The problem is the same as with "compact" phones - there are only few models so the choice is very limited and they are usually "so-so" (or have other issues).
The problem is, as always, with marketing - it's easier to sell "this is newer/better because <x> parameter is higher" [1] so we have gigantic phones with more megapixel cameras and higher waterproof rating though I'd argue that more people would be affected by dying battery than by lack of waterproofing… (no data to back it though). Anecdotally I were changing all my previous phones because the batter was dying and never in 20 years had issue with phone being sumberged...
Those are just dumb trends :/ I would love for a phone that has lumia design - it was polycarbon/rubbery, had easy access to battery and yet was super sturdy and I didn't feel the need to buy yet another cover because, to bump the margins, whole effin world is going "premium".
Same with cars so you have less and less choice for a normal sized city-car and everything has to be "crossover" or "SUV"... ffs...
It only shows that you have no clue how EU and it's institutions works, how they are chosen (and elected) and why it was done this way :D yes, it's a huge compromise to satisfy both direct democracy via PE and member state governments. What's more, the actual composition of the government in most of the countries is not elected either (you as a populace don't vote who would be your prime minister, nor it's cabinet... or who will new president nominate)
> Oracle broke compatibility between Java 8 and Java 9+,
No it didn't. Introduction of modules (Java Platform Module System (JPMS)) would be mostly transparent to majority of users.
> so many of the libraries that have a dependency on older functionality are not getting maintained.
Any example? (I already herad the same argument on bluesky and asked for example and suprisingly didn't get it either)
The biggest issue around that time was switching from javax to jakarta namespace but that's somewhat on the side of the Java versioning.
> Java 8 is turning into a dangerous space because even though the JDK is getting patched quarterly, much of the components that work with it are not.
Again - examples?
If the library is not update then it could happen in any ecosystem - python, c# and whatnot.
> It is only going to get worse. SpringBoot, for example, requires either a commercial contract for Java 8/11 support or Java 17+ for the community supported stuff.
Of for f sake - if you are still stuck on Java 8 (released a decated ago) and didn't update then it's only your fault. Supporting ancient platform cost money so you either put that money to be up to date or you pay companies to maintain compatibility you ancient stock. MS is doing the same with old OSs and virtually any other company requires to pay/pay more to support old stuff... (because it costs money)
I'm coming in as someone who helped get thousands of Java 8 based SpringBoot 2.x apps to Java 17/21 and SpringBoot 3.x, so a non-trivial portion of my last year. The javax -> jakarta namespace was a part of the issue. Turns out, we had a lot of things using jaxb as either a direct or transient dependency. About 10% of the apps were some form of old school Java EE which faced the same issue. None of the porting is hard once you've sat down and done it once - but we had team after team who were doing it the first time. We also got to find out who was using deprecated packages, as release by release from 9+, they started to be deleted. Way too many libs were using Sun's base64 encoder.
The point here is that Java is getting updated and the core JDK is just fine. We are seeing components drop support for Java 1-8, requiring 9+. And yes, that could happen in any ecosystem. It is happening in Java ecosystem today. If you crawl GitHub and look at what is vibrant and what is becoming abandoned, you will see the unmaintained legacy stuff stuck on Java 8. CVEs are a terrible way to say security risk - but it does show trends.
Since about 80% of our Java apps are SpringBoot based, when SpringBoot 2.7.18 being the last 2.x community release that reached EOL in November of last year. That version released with Spring Framework 5.3.31 - Spring Framework is currently 5.3.41 or so for those getting commercial patching. This is the last version that supported Java 8 through 11. Similar issue with MapR. This traps people on specific Java versions, which then traps them to an aging ecosystem of components.
The parent asked - why not target Java 8? That is why. If the parent asked, should I be compatible with Java 21-8, I'd say fine. It is a company's fault if they found themselves on an EOL product. Please, for the love of god... don't enable teams to remain there by making ANYTHING that requires Java 8.
None of this is hard until you have so many that it is.
While javax->jakarta was huge PITA (less motivated by technialities but more by politics though) let me introduce you to https://docs.openrewrite.org/ which should make such upgrades easier :)
Why? It's a library so the more platform it supports the better. There is nothing inherently wrong with that and if the author wants to put up with the lack of modern features and syntactic sugar then why not?
1) cookie banners are because tech giants are giants c-nts that will do anything to drive their point (and they are breaking the law because "reject" is usually hidden); though the UE should push to have it as a browser setting and voila - not nagging
2) there was a push for Google, as a monopolist, to offer option to use different map services but becase it's typical for the bully to abuse it's possition they removed the setting. And it seems to work as it causes the frustration in the end users.
It's kinda sad that people are still drinking google cool-aid
This is a ridiculous take. Of course Google should be allowed to link to Google Maps from their homepage and search. I have never seen this level of adoration for ridiculous overregulation.
This is the reason the EU has stagnated and will continue to stagnate indefinitely. There is simply no culture of getting shit done, it's all about hand wringing.
Americans have learned a lot more from having a flourishing tech industry than the EU has, which has stagnated for 20+ years and has missed out on the mobile revolution and will miss the AI revolution.
Our model works to create actual progress. Your model results in nothing but a rent-seeking regulatory industrial complex. The EU can only miss so many industrial revolutions before it fades into total irrelevancy over time. There is a reason your share of global GDP is declining rapidly vs the US.
The problem is, as always, with marketing - it's easier to sell "this is newer/better because <x> parameter is higher" [1] so we have gigantic phones with more megapixel cameras and higher waterproof rating though I'd argue that more people would be affected by dying battery than by lack of waterproofing… (no data to back it though). Anecdotally I were changing all my previous phones because the batter was dying and never in 20 years had issue with phone being sumberged...
Those are just dumb trends :/ I would love for a phone that has lumia design - it was polycarbon/rubbery, had easy access to battery and yet was super sturdy and I didn't feel the need to buy yet another cover because, to bump the margins, whole effin world is going "premium".
Same with cars so you have less and less choice for a normal sized city-car and everything has to be "crossover" or "SUV"... ffs...