121–130 of 142 posts
Earlier quoted context omitted.
That's not what i asked, why do you trust a no name dev more then the distro your kernel is coming from? And do you really think flatpack prevents you from running packed malware?
Why do you assume the flatpak comes from a no name dev? My calculator flatpak comes from the same people who wrote it, and I obviously trust them, otherwise I wouldn't be using their application. So why should I trust them less than my distribution?
Earlier quoted context omitted.
Doesn't SUSE have KDE by default? I use it on FreeBSD myself. It's an amazing desktop. I don't like gnome at all. It uses too much screen space (huge touch style window decorations) and doesn't have enough customisation for me. But KDE is perfect.
OpenSUSE doesn’t have a default. SUSE uses and supports GNOME.
> Default Desktop
> Plasma Desktop from KDE is the default workspace on openSUSE.
Earlier quoted context omitted.
Apple doesn't change. Chrome doesn't change. They both look exactly the same as when they were introduced. What makes platforms strong is stability and consistency. Linux desktop projects are more likely to get funded the more disruptive they are and the more likely it is they'll alienate supporters and cause drama. Like gnome's big shift circa 2014 to tablet first interfaces. If we consider that Linux desktop users…
> Like gnome's big shift circa 2014 to tablet first interfaces. It took a long time to work itself out, but today Linux+GNOME is the only mainstream system that's usable for real productive work on a pure tablet or palmtop device. Far more so in fact than even Apple's iPad. And it got done without having to write and test separate apps, everything has a responsive interface that works throughout the range, from a sma…
Earlier quoted context omitted.
Why do you assume the flatpak comes from a no name dev? My calculator flatpak comes from the same people who wrote it, and I obviously trust them, otherwise I wouldn't be using their application. So why should I trust them less than my distribution?
Ever used npm?
Earlier quoted context omitted.
Eh, no. QT5 is THE serious cross-platform toolkit. Everything else it's a turd deserved to be shunned. Microsoft Teams it's seen as a disaster even from die-hard MS users.
It doesn't have to be though, it's not because it's HTML+CSS+JS that it's bad, it's bad because it was poorly written. You can write poor code in any language/toolkit. You can make beautiful and fast apps with HTML+CSS+JS.
Heck, you can make fast code in Python by embedding a DSL and writing a native-code compiler for it. Turing completeness means that everything is possible, which means that "possible" isn't interesting - practical is.
Judging by how few fast webtech applications there are, it seems like making them is not very practical.
Yes. GNOME is better than ever, GTK4+Libadwaita is simply doing one: Looking perfect. The HIG are excellent, without GNOME I would be maybe 40% as productive as with it.
It may look good --- beauty is in the eye of the beholder --- but it's ergonomics are bad. All those hamburger menus, all those disabled configuration parameters, the non-modular architecture, the poor state and quality of Gnome Shell extensions. I really try to like the modern Gnome, but they make it very hard. If your goal is not staring at some graphic design, but having tools that help and do not stand in the way…
Earlier quoted context omitted.
It doesn't have to be though, it's not because it's HTML+CSS+JS that it's bad, it's bad because it was poorly written. You can write poor code in any language/toolkit. You can make beautiful and fast apps with HTML+CSS+JS.
You can also make safe and reliable applications in C++, or fast applications in Python, or readable code in 1990's Perl - it's just very difficult, because those languages lend themselves very poorly to those things, and that's why good developers avoid using those languages when those traits are needed. Heck, you can make fast code in Python by embedding a DSL and writing a native-code compiler for it. Turing compl…
Perl is not Forth. I know y'all know Perl because of Gold code contexts and oneliners, but look at some games written in Perl and tell me Perl is not readable.
Better, get the free books from Orelly:
https://docstore.mik.ua/orelly/index.htm
The 4th version is updated enough.
Earlier quoted context omitted.
> If that bothers you, it is far more productive to actually contribute your time to fixing the issue than simply describing it while waxing lyrical about how all these modern devs have simply 'lost the way'. I agree with that sentiment in principle. In fact, I advocate the same myself. However, playing the devils advocate, all an individual non-core developer can do is try to smooth out the rough edges. If the compl…
Thanks for responding. I can see your angle but I don't think I agree. I'll try to respond in good faith but let me know if I've made a misapprehension. In regards to the topic of user base alienation: I do think it is an important metric to keep track of, but whether it should be prioritised is contextual. In the case of GNOME, they have frequently made a point that accessibility is a large focus for them. Accessibi…
When the one and only step is "hard fork the project", that's not really an easy one.
Earlier quoted context omitted.
You can also make safe and reliable applications in C++, or fast applications in Python, or readable code in 1990's Perl - it's just very difficult, because those languages lend themselves very poorly to those things, and that's why good developers avoid using those languages when those traits are needed. Heck, you can make fast code in Python by embedding a DSL and writing a native-code compiler for it. Turing compl…
>readable code in 1990's Perl - it's just very difficult, because those languages lend themselves very poorly to those things Perl is not Forth. I know y'all know Perl because of Gold code contexts and oneliners, but look at some games written in Perl and tell me Perl is not readable. Better, get the free books from Orelly: https://docstore.mik.ua/orelly/index.htm The 4th version is updated enough.
Earlier quoted context omitted.
Thanks for responding. I can see your angle but I don't think I agree. I'll try to respond in good faith but let me know if I've made a misapprehension. In regards to the topic of user base alienation: I do think it is an important metric to keep track of, but whether it should be prioritised is contextual. In the case of GNOME, they have frequently made a point that accessibility is a large focus for them. Accessibi…
> Or, in a sentence: you can improve these projects in the way you see fit if you take the steps required. Well yes, but actually, no. If upstream denies or ignores your pull requests, you're dead in the water. Just try and make a pull request to bring back a feature that Gnome or GTK dumped a few years prior.
The 'meta-argument' I was making is that delivery requires coordination, and the more you deliver the more work it is.
That's all well and good, but on a singular level I agree that simply throwing a patch request without doing the due diligence won't get you far.