At this point, web design 'ecosystems' are essentially money whirlpools. They're complex, so they require programmers skilled in using them, who in turn make more sites which need more programmers, and so on, and the network effect takes over and cements this feedback loop in the structure of the jobs market.
And the frameworks are churned continuously and are also bug-ridden nightmares, so that continuous development and support is needed to keep websites functioning and secure.
Any reduction in framework complexity threatens the whole edifice.
I have on several occasions offered to pay for food at a nearby sandwich shop or fast food place for beggars who were asking for money for food. None of them accepted the offer.
Claude is insanely good at grunt-work maintenance coding, which is a fairly formulaic exercise that mostly requires RTFM and simple code changes that look a lot likw the surrounding code. Designing new things from scratch based on human specs is something which Claude still struggles with.
The problem is that it often doesn't get it right the first time. You have to sort of have a conversation and it eventually gets there but if you have no idea what the destination should be like, you can't guide it there.
AV2's mission is to nip VVC in the bud. They seem to be more or less at parity, and given that, why would anyone want to use a royalty-based codec when they could could use an essentially equivalent free one? There's no massive hurry to implement either - we have existing codecs that are largely good enough for now - this is technology which take 5 to 10 years to fully deploy, as has been seen with other codecs.
And the frameworks are churned continuously and are also bug-ridden nightmares, so that continuous development and support is needed to keep websites functioning and secure.
Any reduction in framework complexity threatens the whole edifice.
reply