Good points.

My friend uses the same headset on Linux, that I use on Windows.

When he "mutes" his headset, it is not actually muted on Linux. It is not really fixable. Obviously, on Windows it just works.

Literally the same story happened on Linux in the span of decades countless times. On Windows? Cannot remember this happening more than once.

How to install the app on Linux.

You search for it. Highly likely it is not available or barely functional.

IF it works, it's only packaged for Ubuntu, Debian and Arch. If you use Nix or something even more niche, good luck with proprietary software or sometimes even openly available open source software.

Using Windows since Windows XP was sired. Using Linux for longer than that, mostly Linux servers, but have tons of years of Linux Desktop experience under my belt, with probably half of all Linux distributions on DistroWatch.com.

Conclusion: Linux server rocks. Windows Desktop sux in many ways, but it just works and I personally have no issues with it. Linux Desktop is the worst hell possible. Barely ever works. It is literal hell and I hate it.

Whenever I try to get into Linux Desktop, I have to meditate and drink a de-stressing tea beforehand, or else I cannot guarantee the laptop's or PC's screen's safety, when dealing with Linux Desktop.

For anyone attempting to comment: note, that there is a huge difference between headless server Linux usage and Linux Desktop/GUI usage. I'm only talking about Linux GUI. Linux headless is fine and works great!

Rufus is king. Of course, only available on Windows...

XD I mean, there are also discreet GPUs from the 90's, yet pretty much all integrated GPUs are far more performant than that.

Your discreet GPU is over 12 years old and even back then it was an entry level card. So, actually, it is very weak and, for many use cases, weaker than many current integrated ones. Not to mention possible lack of current driver support, etc...

You could also look up the other parts, I won't do that for you. But the same counts for the "i7". If the i7 is nearly as old, it's weaker than some i3s from today and definitely weaker than lots of i5s, nowadays.

Again....... Same goes for the RAM, etc... If your RAM is really slow, then the size of the RAM will only be useful for certain use cases.

Again and again.... You have to research for every part, to really know, what they are capable of. Just saying "i7" and "discreet" does not make the PC any better, whatsoever.

In short: you can use the computer for a lot of stuff, but only very limited. If you want to do something very specific, really well, then you need to find the right niché, where it might work well. Otherwise, as I initially foreshadowed, there is actually not much you can do with those specifications. ¯_(ツ)_/¯

Can't do much with these specs. You could make it headless and lose the desktop environment to make it much more useful.

Yes, I switched to an older version and there was the warning. However, there was no warning on 0.101.0 whatsoever, so upgrading just one patch version broke my master module.

Sometimes, I skip some versions, so I am certain, that I jumped from < 0.100.0 straight to 0.101.0 and here we are, without any deprecation warning.

Fully agree on this. I do not say, it's bad. I love innovation and this is what I love about Nushell. Just saying, that using it at work might not always be the best idea. ;)

Yesterday, I upgraded from 0.101.0 to 0.102.0 and date to-table was replaced equally (actually better) with into record, however it was not documented well in the error. Had to research for 5 to 10 minutes, which does not sound much, but if you get this like every second version, the amount of time adds up quickly.

Nice, noted. Do you have any other projects on your mind?

SimpleX sux in so many ways...

Thanks for your suggestion. Do you have a list of Github URLs of the ones most important to you?

Nu is great. Using it since many years. Clearly superior shell. Only problem is, that it constantly faces breaking changes and you therefore need to frequently update your modules.

Back then, a pain in the ass. Nowadays, I just let an AI handle that. I used this crap for years and years and still cannot remember, which symbols you need in which order. And why should I remember? I'm not the computer. The computer should know, not me.

It's not about the syntax itself, it's about which syntax to use. There are different ones and remembering which one is for which language is tough.

Very true. Been programming/scripting in Bash since many many years, I could almost consider myself an "expert", however I still need to look up the same crap over and over again, since remembering weird symbol constellations is the last thing you should do, when you actually just wanna achieve a goal with the script and not learn how to summon the spirit of some C-related language creator.

Thanks for the suggestion. Do you have a list of Github URLs, leading to some of the most important emulators, in your view?