I agree with you here. As soon as you change something, that should be respected but as long as you use the default theme/wallpaper/… that could just as well mean that you prefer tracking the default or don’t care at all.
Now bringing back the explicitly disabled search bar really is atrocious
Yeah, if all those complainers want something more modular, they’re free to push for protocols that allow to leverage existing components while also allowing for them to come from multiple vendors.
Objectively, Apple is focusing on leveraging high DPI over subpixel tricks.
It makes sense that people who value sharpness on low DPI screens prefer subpixel rendering over grayscale.
Qt is a thing. Idk why all these environments are messing around with a GTK that’s being sabotaged/neglected by GNOME while Qt just keeps working.
Thank you!
Do you have a link without paywall?
The both-sidesing was already telling. Sometimes the only “controversial or alternative viewpoints” are just idiotic conspiracy drivel and should be presented as such (or not at all)
A developer who hasn’t caught a virus since his teenage years.
Yeah, a measurement cup is half a pint. They are defined volumes
Why would we?
Rust is faster than C. Iterators and mutable noalias can be optimized better. There’s still FORTRAN code in use because it’s noalias and therefore faster
You got it right, the person you replied to made a joke.
In a good way. Using a non-verified bytes type for strings was such a giant source of bugs. Text is complicated and pretending it isn’t won’t get you far.
That was my immediate reaction here: one of the reasons the xz backdoor was possible is that nobody is going to question the idea of shipping a tarball to spare users from having to touch Autotools.
Of course I wouldn’t think of manually hacking together Makefiles since I come from languages that have either the One True Build Tool or a standard for packaging and defining build backends.
I think the author’s aversion to build tools trying (and apparently failing) to make everyone’s life easier is more a statement about how much C/C++ have suffered from not having a standard for packages.
I don’t think those are better or worse. My point isn’t about some ancient far too limiting standard, but about how easy it is to wreck everything by not knowing some obscure syntactical rule. My issue is about implicit conversion between strings and arrays, about silently swallowing errors and so on. And the only shell languages that I know aren’t idiotic are nushell and Powershell.
That KDE theme that nuked some user’s home directory? Used a bash script. That time the bumblebee graphics card switching utility deleted /var? Bash script. Any time some build system broke because of a space in a path: bash/ZSH/… script.
Why would anyone make an init system based on shell scripts these days?
POSIX shells are horrible unmaintainable bug factories.
shellcheck is not enough to make them safe programming languages. They are acceptable only in an interactive context.
Having anything encourage people to write POSIXy shell scripts is a design flaw.
Services are bash scripts?
Oh no. That’s horrifying. I’ll never go back to the bad old days where my system constantly has dozens of untestable buggy bash scripts running.
I currently have zero bash scripts running on my system until I open steam, and there’s no world where I’d go back.
Nuance? On my internet?