Tech really can't see begging for more money from VC's as nothing short of a revolution, rolls eyes.
I can't believe he invented Markdown, one of the most genuine amazing things to come out of languages and the like, especially after what I just read.
JOHN GRUBER wrote a... thing? About Open AI's begging of more money they absolutely don't need. I stopped reading at this paragraph. Maybe he proves me wrong in the latter parts of the post, but this paragraph sure as shit did nothing to convince me he's worth keeping up with for serious tech journalism.
> Thus, effectively, OpenAI is to this decade’s generative-AI revolution what Netscape was to the 1990s’ internet revolution. The revolution is real, but it’s ultimately going to be a commodity technology layer, not the foundation of a defensible proprietary moat. In 1995 investors mistakenly thought investing in Netscape was a way to bet on the future of the open internet and the World Wide Web in particular. Investing in OpenAI today is a bit like that — generative AI technology has a bright future and is transforming the world, but it’s wishful thinking that the breakthrough client implementation is going to form the basis of a lasting industry titan.
I mean, if you wanna read it, have at it, but I simply have to know, where does his journalism shine?
https://daringfireball.net/2024/12/openai_unimaginable
#AIHype #AI #Technology @techtakes
Any good invention looks obvious in hindsight.
Before Markdown there was setext, Textile, reStructuredText and atx, which were basically the same thing but less trendy. Gruber had the huge advantage of being popular with the Macbook Starbucks coder crowd.
and many you can tell they're dogshit from the moment they're introduced
so, for instance, in the case of markdown specifically: it's actually a shitshow format to implement. the reference implementation driving the "spec" as done by gruber was (iirc) essentially a big stack of regexes with language-specific behaviours assumed in, and lots of by-design implementation presumptions rather than by-specification dictation
want to make an implementation in another language? better hope you know every single corner case and behaviour!
(this is one of the reasons why markdown impls varied for so many years, and why even now "commonmark" is still trying to fix the issue)