870 karma · joined July 14, 2022
Instead you pick literally the worst (of the popular) languages that is painfully inefficient.
But you can buy legit oem licenses that cost something like 40$. You simply won't be able to move it to new pc, but usually it doesn't matter much.
People avoid them cause "surely if they are thus cheap they must be scam", but it's not. They simply have restriction of permanently binding to single hardware. But again, usually it's worth it anyway
And since most people are used to windowsUI, going out of their way to switch to Linux while still keeping windows installed just doesn't make much sense. Also, with wsl I can switch back and forth seamlessly, while dual boot is inherently clumsy when trying to cross the barrier.
It's not really much different then 'w10 updates forever', just marketing with new version.
Which is basically how every tech ecosystem works.
The problem is that linux is supposed to not be just_another_centrally_controlled_ecosystem, so when systemd abuses their popularity by enforcing whole ecosystem (rather then cut itself into separate pieces), that is worrying
I don't like a framework that promotes using components that are arbitrary dependent on it.
To use udev, I need systemd-init, and to use systemd-init I need systemd boot.
I really don't believe it MUST be this way, and those requirements aren't at least partially arbitral.
Why systemd refuses to run in chroot?
And now I don't like systemd anymore.
Even in hindsight it's hard to judge whether building your own engine was good or bad decision, and we are nowhere near "the hindsight" level of knowledge.
Because not every program that doesn't compile is necessarily invalid.
And no matter how many upsides ECS can have, being forced to use it everywhere, rather when You want to, is the painfully part.
Not to mention smaller projects like 'Braid- anniversary edition'.
...but ofc most app makers are lazy and just throw up error whenever they don't get what their wont, forcing users to give up.
I guess google could introduce a dummy system for every single service and feed that to the apps when the permission is not granted, but I imagine that would be a lot of work. Maybe some day...
Looking at what big companies are doing is also weak argument, especially since Google literally developed their own language which slots in the same space as Java. Maybe not exactly the same, but pretty close.
Again, if you need compatibility with existing code - that it's a decent argument. But in terms of language itself? No good reason
And even if they went for "all out war" I still don't think it would be that one-sided.
And yes, in the end everyone end up using GMS (besides those who are banned, ie. Huawei). But still, it's better to have a separation that is imperfect, vs not having one at all
If you compare ecosystems then maybe, but it terms of language features I don't know why would any1 ever pick java from scratch in this day and age.
Sure, if you really care you probably will go for something lower level, but if you don't want to abandon all the nice things that high lvl language offer, C# still exposes some tools to get your hand dirty every now and then. (Unsafe, stack allocation etc.)
Kotlin meanwhile goes even further then java and completely removes the distinction between stack and heap, slamming every single type into an object. Painful.