81–90 of 142 posts
> Systemd, gnome 3, I think that it is Red hat that ruined the desktop experience in the last decade by imposing terrible choices on everyone else...
90% CLI oriented but with common sensical GUI plugins and settings.
The best of both words, and a "DE" with unmatched speeds.
Earlier quoted context omitted.
I'm not sure how they've kept up, as I haven't used Qt in some time, but back in the 4.x days the documentation was absolutely stellar. Extremely thorough and almost every non-trivial feature came with code samples. I couldn't for the life of me understand why anyone was using GTK at the time.
My point is not about lack of usability or documentation. Rather that the nature of HTML+CSS+JS lets you do things you can't do as easily in either GTK or QT. In the latter, yes you can easily achieve a certain kind of UI, but not deviate from it, and even formatting/displaying a significant amount of information that doesn't fit into one of the classic widgets can be a bit of a pain.
Earlier quoted context omitted.
Just imagine you need a container for the calculator.....
OpenBSD went that route, and when they introduced pledge(2) and later unveil(2), they've applied these to every single program in the base system (over the course of a single release cycle!). There's absolutely zero reason for bc(1) to accept network connections, or for grep(1) to execve(2) into arbitrary programs. But both of these programs need to process and interpret arbitrary input, which makes them potential ta…
Earlier quoted context omitted.
Just imagine getting pwned by malware bundled in a calculator...
What is the connection here? Why would you install the calculator not coming from your distribution?
Without flatpak I'd need to use some rolling release distribution, where not just a few applications get updated quickly, but also the rest of the system, which I'm not interested in.
Earlier quoted context omitted.
I don't think that's really the reason for Electron's popularity. While GTK and Qt are cross-platform, my (limited, to be fair) experience with building for multiple platforms was that it was a huge pain in the ass, and Windows and macOS platform integration often felt clunky and out of place. The big draw for Electron is that we have way way way more web developers out there these days than native-code desktop UI de…
a big part of why browser engines are so unwieldy is the implied compatibility with every website ever, right? but the "way way more web developers" you mention are not, at least in the context of electron apps, interested in that feature except tangentially.. so while everyone knows a full web-ready browser engine is impractical to design from scratch, maybe a simplified engine that supports a conservative subset of…
Maybe something a bit opinionated, like a React Native-only runtime, could fit the bill here.
Or in a sense, is this what Flutter is?
I use Fluxbox (slightly tweaked Zukitre theme), lxappearance, Tango2 icons and Rox filer with a bunch of plugins among Rox-Lib under ~/lib. 90% CLI oriented but with common sensical GUI plugins and settings. The best of both words, and a "DE" with unmatched speeds.
I think there's a future for STLWRT. All was right with the world when Linux looked like this: https://www.linglom.com/images/Linux/ChangeIPAddress/1.png I still run RHEL5 and use it everyday. I don't even consider it that old.
Earlier quoted context omitted.
I don't think that's really the reason for Electron's popularity. While GTK and Qt are cross-platform, my (limited, to be fair) experience with building for multiple platforms was that it was a huge pain in the ass, and Windows and macOS platform integration often felt clunky and out of place. The big draw for Electron is that we have way way way more web developers out there these days than native-code desktop UI de…
a big part of why browser engines are so unwieldy is the implied compatibility with every website ever, right? but the "way way more web developers" you mention are not, at least in the context of electron apps, interested in that feature except tangentially.. so while everyone knows a full web-ready browser engine is impractical to design from scratch, maybe a simplified engine that supports a conservative subset of…
The issue here is re-use - Sciter is small and very fast, but won’t run an arbitrary existing web app that targets Chrome. Maybe you could argue for a middler-ground, add more HTML features to Sciter until it can run “most” things… but you’ll end up back to having the whole banana.