Not really worth a message, but I just released a new version of calendoku which fixes several issues with timezone handling introduced in v5. Still, date/time handling in PHP is a mess.
Wow, I finally got some feedback, so people are actually using calendoku!
I didn't write about the former ones, but there are two new releases: One was rather a bug fix one week ago, the other (recent) one is another release (v5). This release adds support for timezones for the dates.
Sometimes I really wonder why people are doing some things. I'm usually pretty happy with anybody who is doing anything, as long as they don't start insulting other people (and even with that, I have a very high tolerance). And I don't complain about software written by other people.
I have already written about my endorsement of a markdown standardization, and I always held back with my complaints about the author not willing to further develop his buggy software, but also blocking standardization efforts. Standard^W Common Markdown was an effort to circumvent this and extent the language which is already heavy in use. But now there are even complaints about this (WHY?), forcing the project to rename itself.
There is a huge industry behind it which wants to use Markdown, there are lots of people using it for their own projects, and a lot of Open Source coders spending hours of having to deal with this shit. Congratulations, now the situation becomes even worse, with the author making clear that, whyever, he will not tolerate any standardization except for his own software.
It's not only what he is doing in this case. It is that he states clear that he will not tolerate anybody trying to use the name for something looking even closely official. Anybody who uses the name Markdown cannot be sure whether he will someday receive a complaint by John Gruber. Who knows, maybe he will get into legal issues as well? It's the same as with patents, except that in this case, there is no company with a rational interest behind it.
I don't have a voice in this whole issue, except for my own plugin which is far from being Markdown, I never contributed anything. But I really hope they just fork it, find a new name, and develop it with their own name. Github, Stackexchange and Reddit should have enough influence to be able to actually make a useful formatting language which extends Markdown in a sensible way.
After lamenting for years and finally, after a few days of coding, it is finally done: I released the first beta of calendoku is released. It is still very rough, but I am currently rebuilding the calendar of this page with it. So for now, it works as far as I tested.
Naturally, I'm interested in Markdown. Now, I read on heise: Markdown shall be standardized. I never expected this to actually happen, but I'm clearly happy about it. Maybe now there is a reference which can be used for Markdowku to implement Markdown properly.
For a long time, I planned to make a longer article about why Markdown is shitty. I mean, writing it is actually nice, but everything behind it is horrible – the techniques, the “standard” (a buggy Perl script), the community (i.e., it didn't move forward for a long time), the missing features (code blocks, tables), etc. I never did it because I didn't want to shame such a nice project (and I didn't find the time for writing the articles), but hopefully, this won't be necessary anymore now.
Once the standard is finished I will make Markdowku respect it.