> Ironically, even though Stonehenge has an earthwork circle around it (the earliest phase of the monument), it isn’t officially a ‘proper’ henge, as the main ditch is external to the main bank. It has to make do with being a ‘proto-henge’.

https://www.english-heritage.org.uk/visit/inspire-me/what-is...

Javascript is actually fully backwards-compatible, to not break the Web. Any javascript from 10 years ago works in the browser. This is good but also a bit of a burden, since the language can only expand but not shrink. React is a library, and like all libraries it has breaking versions. Not understanding the basic difference between the two kinda undermines the credibility of the article.

Also, in a similar way, core, ANSI SQL is largely backwards compatible, but all the SQL dialects linked to various DBMS implementation are generally incompatible. Obviously that's not mentioned in the article.

> Not a tutorial. Not an ORM. Actual SQL: joins, subqueries, window functions, query plans.

Not text written by a human. Not a style that an real writer would ever use. Actual AI slop: Short sentences. Incorrect facts. Not X, Y.

Now I want to know in which culture this is used as a common insult.

Clients - I don't see anyone delighted that apps are better, or cheaper, or more secure. If anything, I see more enshittification, more half-baked ideas and more fear that security is worse now that we let AIs write almost all code.

Employers - They didn't really sell more or expanded their customer base. They would have, if they had the exclusive advantage, but now everyone has AI. They can cram more features in their software quicker, but so can their competitors, and AI is not magically opening any untapped market. If anything, everyone is now doing the same thing - trying to get their software on the AI train, with mediocre results so far.

You - did you benefit really? The job market is shit due to the death of ZIRP, the nature of the job itself is changing and there's a lot of uncertainty around. If anything, employees are now laid off more, not less, and salary and bonuses are not increased in any measurable way.

It looks like to me that we have to dance this particular dance because if we don't do we're left behind. That's fine, it happens every now and then. It might even be that in the future we will have tangible advantages from LLMs - better automated health care, better learning opportunities come to mind. That has to be demonstrated. But now, in year 2026, what's one advantage of AI? Having less and pricier RAM? Being able (and expected) to write more code in less time?

I don't understand this. It increased productivity of every developer in the western world, so it didn't really give you an advantage. Your output is more valuable, but your colleagues' output is more valuable too, and your competitors' output too, and so on. So you're doing more things at the same salary and it's not like your company or your employer is making more money than usual or awarding you more eoy bonus. If your "life-change" is "I'm writing more code" without any other advantage (and with the possible disadvantage of your role changing, or being at risk), why is it desirable?

1) Materializing documents. Assuming you don't have "live" yjs documents and you only merge diffs with diffUpdate, when one or more user are connected, it's always worth to have the blob in RAM to quickly merge diffs in it and save it periodically; when the usages of a document go away, you save it for the last time and you "ice" it in long term storage, offloading from RAM. I typically use a LRU cache for that. The problem is when too many users are working on too many docs and they all have to fit in RAM. How do you solve that?

2) GC. Again, assuming you don't have live documents but you only merge diffs, those blobs need to be garbage collected to compact them after a while iirc (if the doc is live it's done automatically). This normally is a periodic process that eventually GCs all documents in turn, one after the other. If you handle that, how do you manage to not make your server essentially unpredictable when it comes to compacting big blobs? GC'ing takes a toll on your CPU, and not GC-ing takes a toll on your RAM and secondary storage.

Sure, Claude Web App is an adequate replacement to full-fledged Claude Code, and then there is also something that I didn't bother to try but maybe you can try it after you bought a new laptop. What the hell.