This is how the year of Linux desktop finally happens!

It's just planet Nibiru.

Poor english skills?

Didn't you mean to say poor Chinese skills? Those US workers, all cocky and don't even speak Chinese...

All true. But to be fair, what really ticks some people (bit me included) is how the systemd folks decided to piggypack all the other things, what they later have started to call "coreOS" with the original "systemd". Sure, they are all somehow related to the process of bringing the system up and maintaining daemons and almost all can be left out if decided. Given it's essentially a Redhad backed project, it will come with it all and I suspect Debian leaves most of it out.

Which all good the either way. The Linux ecosystem have survived from worse misteps if mistep this be.

Hum. That's true.

I wonder if it could be circumvented by setting something like Gnome terminal or krusader as the login shell instead of desktop environment's session manager. Maybe then a new program would be opened in its own window and not inside that hideous box. Or, it won't open at all. I think Xrdp doesn't do rootles.

How have you configured Xpra, do you run it all in the server or tunnel Xpra session over the tunnel? I tried to do it all in the server end when it was all new and flimsy (because the receiving end was a windows machine with Xwin server), but didn't get it running.

Wow, what a good round-up and start collecting karma. You should sign up and I'd mod this message up if I had points.

And it used to do a lot more, like load executables, and be a print server.

On the other hand, it does not do much of what its original strong points were: graphic primitives, no one uses those any more, only raw bitmaps prepared by various external libraries; fonts, people use Pango, device drivers, they are now in the kernel; remoting, now done by RDP and VNC and the list goes on, hence why Wayland is now actually viable.

You mean it needs to be separately enabled and or installed?

You know, for the past 20 years, all major X-distributions have come networking disabled by default. Yeah, its there, you may be able to (I've always been) enable it, but for sure it's not ideal. Lack of any model of sessions or the huge round trip delay of modern applications makes using it over the public internet pretty miserable. Plus one needs to set up an SSH tunnel for it separately, because X doesn't do real security either. ...Or they could just use Xvnc, like folks have been doing about equally long.

Also, DRI2 and various other common extensions don't work over network.

Also, Knuth hasn't yet finished "The Art of Computer Programming".

(Publish the fifth issue and update 1-3.) At this phase, he'll need to break the oldest human alive record several times over...
It's just too much work. If it gets finished, it won't be by him.

But still no "advanced macros, non-blocking IO or much of synopsis 9 and 11"...

Thank you, I didn't know this.

I was wondering, how anyone would inhale water.

Then I remembered a friend who has gotten into these vapes/e-cigs or whatever they are called. The thing is, he mixed his own juice, because ordering raw nicotine fluid is apparently a lot cheaper than premix. ...Now just wait when his head starts to swell.

IEC 61131 is the automation guys bread and butter, but apart from it, every machine smarter than a induction motor seems speaks it own variant of ugly QBASIC.

Learn to grok those, get good, have a proof of it and there are plenty of jobs.

I mean every guy can do simple "put an input in in these circumstances" like things in them, but dare to use the buggy and feature-depleted networking/gui/string manipulation utilities the programmers put in probably thinking no-one is going to use them anyway, you need some good wits, because the thing is literally a black box, sometimes you load the thing in with FTP or serial and the blinking lights at IO board is all you get to show that the thing is doing what you inted to. No debugger, though there will be bugs - hardware bugs! And bad, insufficient, badly translated documentation, no user community to get help from; maybe a manufacturer hotline which will tell "gee, I dunno" if you are lucky and privileged.

PowerShell is not like the shell languages. It tries, but fails subtly the moment one tries to use something not .NET based, or anything not specially wrapped into a cmdlet. Pretty much fails the original promise of shell languages, the ability to pipe together programs that don't necessarily know anything about ech others beforehand. I don't like the attitude of everyting's .NET, raw data is irrelevant. Say, try to manipulate SQL dump with binary data in it in the normal PowerShell way, it gets corrupted due carriage returns helpfully being added in. There are workaround though, just have to be super careful to not use THE PIPELINE for it. Anyway, that's what bite me recently. Sorry for having to take my eruption, o random stranger.

As a person who uses C-preprocessor extensively, I need my capslock key.

Jokes aside, I often program these industrial robots where basically every variable is a macro-define on bare memory address. The macro system doesn't know about tokens, but thankfully thinks case matters, so I use all caps on my variables to reduce name clashes.