Damn you got me. I am not a big fan of KDE (Currently using Niri) but I can try to use KDE+aerothemeplasma with nixos as a dual boot (I already used to have KDE nix as dualboot until I accidentally removed that disk and ended up using the glorious tool testdisk to save that) so I will try it some day thank you!
There is also anduinos which I think doesn't try to replicate windows 7 but it definitely tries to look at windows 10 perhaps 11 iirc
When I said native, I meant native to the language, something written purely in Zig, without depending on external UI toolkits. Basically like how Rust's egui works.
You're taking "new fangled" too literally. Is it new, as in not everyone concerned is aware of it? Yes! I think the author is as enthusiastic about this as you are.
New fangled is unambiguously pejorative, both in the absolute sense and in how it is used in the article. If it looks like shit and smells like shit, don't tell me it's not shit.
>There are a few startups these days peddling a newfangled technology called “incremental view maintenance” or “differential dataflow”. Basically the way it works is you just say “hey, I’d like to keep track of how many tasks each project has” by writing any SQL query you want:
>[query]
>The “magic” is actually really cool. Basically the SQL query is analyzed to produce a DAG of the data flow with different nodes for filters, groups, joins, etc, and then each node “knows” how to map any change in its input to the appropriate change in the output.
So the person who calls the technology "magic" (with emoji sparkles around it!) and "really cool" and generally spent all this time writing an article about this particular annoying problem and all of the other bad solutions about it, and then mention these startups at the end... Is being denigrating and dismissive.
Which one of these companies do you work for that causes you to feel so hurt? Because the author didn't mention them by name?
exactly. Borland era OOP gui code was amazingly well thought out. The flaws in the flutter framework are soooo many, a lot of half baked things are made standard. Try to get 2-way scrollbars working decently (try to nest them, or go watch the video tutorials that supposedly explain how to do this - it was an absolute horror show). There are so many hassle factor things that one googles or searches the github for, find tons of other smart people beg for it with examples and use cases and just watch the team say they won't implement for some or other reason. But even the simplest thing, that when you create a component (say with mutable state) - you don't create one class to get one widget defined, noooo you have to create two, one stateful and one stateless. All of these little weird decisions that were made for bs reasons eventually add up to a ton of incidental complexity. Oh we made part immutable for "performance" reason, but the real reason is that people don't understand when to avoid functional style programming idioms. All the weird ways the layout system can bite you, the way they designed constraints being passed down and sizes passed back up - boy are they forcing you to do a lot of thinking about incidental complexity, and the different containers and how thy interact in ways you would not expect by default. The fact that you cannot on a per container basis disable overflow displays in dev (many people have asked for this). That silly debug ribbon your app gets until you disable it LOL who thought that was a good default. In the end though one can make it do a lot, and it is reasonably performant. But the pitfalls are many, and basic stuff that it doesn't solve well for you.
This does ignore the fact that there's not one UI toolkit that you can target and that will work on all distros, and you certainly can't target Qt, GTK, ETK, etc. all at the same time. I've been making a cross platform GUI library and it's been a pain point on Linux (even though I use Linux!)
Wouldn't that be XUL[1] ? It's been there since 1997 and never took off outside of Mozilla, so it was deprecated and removed in 2017. It wasn't meant for use in the wen directly as replacing an entire ecosystem with a completely different way of doing UIs would be close to impossible, all for small benefits.
Feels a little like a déjà vu from an older browser by a big company that had a monopoly..
IMO, the sad truth is that what will happen is that JXL simply won't be used because it's not worth it to lose customers in exchange for a few kilobytes saved. Google has won, it has a monopoly on search, advertisement and the browser and decides de facto of all standards.
The screenshots could easily fool me into believing it actually is Windows 7 :p