I thought GCC dropped support for compiling to the abacus?

I concur. It is also relatively unmolested in terms of fucking up KDE programs.

I remember when Mandrake was a young distro – a redhat derivative – and they (gasp) chose to compile for i586 instead of i386. People were like VROooooOM! And a bunch of other people were like: why would you target CPU instructions that not everyone has?!

tl;dw?

Probably someone’s pet project

I’m sorry you had a bad experience. I’ve used it as my daily driver with minimal effort post installation on multiple occasions, usually on work laptops where time spent tinkering is time wasted. I’ve found it to be a good choice in that context. I now own my own business, and OpenSuse has allowed me to repurpose older laptops as workstations for my employees with minimal effort.

The only actual pain point I’ve seen is setting up a wifi enabled printer … required that I change my firewall zone so the printer could be discovered. And that only required a few minutes to figure out. The fact that the firewall is set to a more secure default is probably a feature, not a bug.

OpenSuse Leap or even Tumbleweed. After getting the media codecs up and running, and remembering to set you firewall zone to “home”, you’re pretty golden.

What’s the weirdest one you’ve tried? Most challenging? Have you found any really cool defining features in any distro?

For example GoboLinux and NixOS eschew the Linux file hierarchy standard (FHS), and that becomes their defining feature. But many other distros have some other defining feature. Slackware uses tarballs as package management and oldschool init. LFS has you build from nothing. Etc.

meow

It’s really rare for a project to completely rewrite to a new toolkit. VLC in circa 2007 did it (moved to Qt - even stole their volume control widget directly from Amarok at the time). GCompris ended up as a KDE project despite originating in Gnome (along with toolkit change, but it weirdly kept the name). LXDE->LXQT also. But I don’t actually have that many examples.

But you mean you wrote it in python with tkinter as a toolkit, rather than writing it in Tcl (which is its own language, like python).

Serious question: I’ve never met a programmer who has ever actually written anything in Tcl in the real world. If you’ve working in Tcl, tell me about it! What did you use it for and when? Was it awesome/terrible/etc.?

Forward slash doesn’t throw a mental syntax error? ;)

Well, you kind of can actually. It just replaces KWin

This sounds like the sort of infrastructure project the Linux Foundation should be supporting.

Sure, it’s just another tarball to compile and install, right? What do you mean lots of dependencies? Oh, well, I guess there is Krita :)

If we’re in string freeze, it’s probably within a few weeks. They’re in bug squashing and translations mode now. I’d take that bet.

As a former slackware aficionado, I’d have to say that the general mood of the users and development team was super chill. Hell, the name slackware comes from “slack”, the goal of the Church of the SubGenius. The whole thing is a meme that’s been going steady for decades.

I had the privilege of meeting Patrick and much of the core Slackware group at the KDE 4.0 release party. They are all awesome.

I can expect that users that tolerate the Slackware style are also those that are pretty laid back to begin with. Probably they were happier people already, and using slackware just vibes with them.

Linux on all their electric cars, and they’re watching porn while driving ;)

In KDE, there used to be man: as a protocol that you could use from Konqueror or anything else for that matter. Does it still exist?

I’m at work and cannot check.