How would a new format be backwards-compatible? At least JPEG-XL can losslessly compress standard jpg for a bit of space savings, and servers can choose to deliver the decompressed jpg to clients that don't support JPEG-XL.
Also from Wikipedia:
Computationally efficient encoding and decoding without requiring specialized hardware: JPEG XL is about as fast to encode and decode as old JPEG using libjpeg-turbo
Being a JPEG superset, JXL provides efficient lossless recompression options for images in the traditional/legacy JPEG format that can represent JPEG data in a more space-efficient way (~20% size reduction due to the better entropy coder) and can easily be reversed, e.g. on the fly. Wrapped inside a JPEG XL file/stream, it can be combined with additional elements, e.g. an alpha channel.
I didn't mean that bash has no local variables, but rather that if you want to use a function as such without capturing stdout, you need variables that are scoped across your functions, which is usually global or at least effectively global.
Bash has its upsides too, like the fact that it has arrays / lists and dictionaries / hashmaps. In my opinion, it gets iffy though when you need to do stuff with IFS; at that point one might be better off just using specialized tools.
Not saying working bash isn't good enough, but it can break in very surprising ways is my experience.
Not sure I'd call what bash has functions. They're closer to subroutines in Basic than functions in other languages, as in you can't return a value from them (they can only return their exit code, and you can capture their stdout and stderr). But even then, they are full subshells. It's one of the reasons I don't really like Bash, you're forced into globally or at least broadly-scoped variables. Oh, and I have no clue right now how to find where in your pipe you got a non-null exit code.
It's not a big problem for simple scripting, but it makes things cumbersome once you try to do more.
In all seriousness though, the core of the technical stack has become very robust in my opinion (DNS being the exception). From a hobbyist's perspective, things work much better than when the Web was still young. I can run multiple sites (some of them being what are today called apps) on a domain with subdomains, everything fast, HTTP3-capable, secured via valid free TLS certs, reverse proxied, all of that running on a system deployed in minutes...
If you focus on the part of the Internet that you have control over, it's a lot better than back in the simple days.
It's only natural that the buyer who orders the most volume gets the best price. So they certainly won't charge Google and all more than others.
Just wait it out and stock up on components when they're cheap and even subsidized by manufacturers. It's times like now that enable this in the first place.
Bonfire itself is a framework that implemented ActivityPub, on it you can build applications that make use of it without developing from the ground up. Bonfire Social is a social network similar to Mastodon. Collaboration is is about project management etc and allows one to host their own, but integrate with others, e.g. to synchronize milestones via federation. What they have in common is that both build on Bonfire and as such use the same protocol for federation. But they're tools for very different jobs.
The current hype and the massive investments are about generative AI, not the actually-useful-for-humanity applications.
Image recognition, medical research etc. are not drives the current market. It's about offering a service that the broad masses use continuously. Otherwise these investments don't make sense.
I think this is a huge release of just because of accessibility, that's always been a pain point (read: basically impossible) with LaTeX, I heard ConTeXt is better there but I never got into it. typst on the other hand is very approachable and makes a lot of sense.
While I don't need accessibility very much nowadays, it's basically a requirement for usage in the public sector here as PDF/UA. Which I guess is the main motivation.
Looking forward to trying it out when it hits my repositories, which should be soonish.
Another option is docbook, but I never particularly enjoyed working with that...
We had vibe coded desktop operating systems, what about vibe coded phone operating systems?