rxjs/reactive like, stores subscriptions, ah that's nice.
But i was disappointed about svelte v5, because it changed paradigm. runes force you to change your mind and it is no more rxjs, it is class-based enterprise angular-js. New version added a lot of new things, but they are not described well.
I also hate some things like your class fields that have state are undefined by design and you need to do cast or null-check every time. Also your getter can't return derived, it should be class field, meh.
Ah, also I HATE how they force SvelteKit. Guys, hello, I need just plain svelte, why do your starter template creates for me non-ssr sveltekit project? Do you really think that I'll choose this new sapper?
====
But, svelte is the only non-runtime framework that is trending and has big community. Hope Rich will do better new versions :)
There are pros and cons everywhere, so far I see more cons.
If you want - you can buy modular phones, pay for that, don't force other people
And I'll go and pay a couple dozen bucks for this work, like all normal people. But eco-activists are starting to say that eWaste is caused by non-replaceable batteries, not by the obsolescence of devices. No one will change the battery in an outdated device, even if it is replaceable.
Hey remember when the Motorola Razr wouldn't charge on a regular USB port unless you had a specific driver (or had to use the actual charger?). Amazing innovation
No one regulated the number of mobile operating systems, and there were really many of them, even before the era of smartphones. Now there are 2 main ones and a couple of outsiders, all the rest died in the competitive struggle
The delay was largely due to intense lobbying from manufacturers, especially Apple, which profited significantly from licensing their proprietary Lightning port.
Next up on the EU's list for 2026: Easily Changeable Batteries (you know, what every cell phone 20 years ago had before Apple).
I think you’re missing the real cause of this shift: These free APIs existed during the investment-fueled growth phase, then disappeared when they started switching into the real business mode.
We had an unusually long period of time where companies could play the startup game of spending money and headcount on things that didn’t generate much or any revenue. Free APIs were an artifact of that. The disappearance of the Twitter and Reddit APIs coincides with them shifting toward profitability.
You don’t have to “vote for” anything for this to happen. When it stops being easy to run companies at a loss year over year, the parts of the company that aren’t generating more revenue than they cost either get price increases or dropped entirely.
I’ve been at a startup-like company going through this change. It was sad, though not at all surprising, when management started taking inventory of everything people were working on and cross referencing it with how much that was generating in revenue. There were a few moments of internal revelation when someone realized that entire teams of expensive engineers had been working on features and products that either very few people used or that were very complex but generated no revenue. It doesn’t make business sense.
The abuse landscape has also changed dramatically. In the early days, free APIs were rarely used features by a few power users. Now, any free API is guaranteed to be abused by some growth hacking startup who wants to vacuum up all of your data and use it for SEO spam, AI training, or other purposes.
By the way, some restrictive laws in Russia, for example, blocking websites law, began with the need to protect children from "illegal content".
Australians, don't give up