cpw

And this is the fifth line of four..

I'll bet the Intel management engine is just as "vulnerable". The only context this is likely a concern is large scale corpo deployments, without verified supply chains to the source. Love how the security researcher handwaves that there's "plenty of existing exploits" that can be used to install the exploit into the SMM, without giving any suggestions of how.

Bought a mach e instead of a model 3 or y because Elon is a dick. Glad to stick it to the wanker. The mach e is awesome btw 👍

Your second point is key. In an ideal world, open source could rival and even beat the best paid offerings (see: blender). But in most cases it just doesn't. There's not a dedicated team working on the open source products, working with HCI experts and designers on every detail of the product. It doesn't preclude the open source being better (see, again: blender), but it does push a LOT of workload onto a bunch of hobbyist developers working in their spare time. The resultant burnout is typically why you see these projects sputtering along for years and years. I don't know how to solve those problems either, but they're your real "roadblocks".

I agree with your fundamental point, learning new shit is definitely fun for me. But there's lots of different people and some just don't. I can definitely sympathize with someone who's income depends on one of these workflows, and why they can't disrupt that for "fun learning sake". There's only so many hours in a day and some people have different priorities.

This guide is misleading. Sure, the product functionalities overlap, but if you have a mature workflow, you will not be able to switch without investing a LOT of effort in relearning your workflow on the new product stack. This is one of my MAIN reasons I hate the "I tried to switch to Linux and failed" genre of content. You're not going to find identical like-for-like replacements in Linux world that won't require significant effort to relearn. It's something us Linux users through and through need to bear in mind.

Also, we need to be cognisant that "just switching to Linux" narratives, fueled off infographics like this, will lead to frustration and dismissal.

No, I don't know how to change this - and morphing e.g. gimp to be a clone of Photoshop isn't the answer either.

Fair enough. But the fact I can't even use it to connect to my homelab proxmox cluster kinda has to be a dealbreaker for me. Even a trial period to allow me to try and experience everything would be sufficient in my opinion. On the fuzzy thing, I'm using gnome desktop, with latest gnome shell in debian sid, on an Nvidia 20280 using the proprietary driver (latest in debian experimental). It's connected to three 2k/1440p monitors running at 144/60/60hz. If that helps at all. The tooltips are most notably fuzzy. It looks like it's being antialiased multiple times or something?

Locking basic homelab functions behind a $50/year license means it is purged. Sad, because it had potential, though it suffers from a weird text scaling issue that means everything is just very slightly blurry.

Check your power. I've had about 50 led bulbs for about 7 or more years. Only the ones in the bathroom failed because they were cheap and not rated for use in a wet and humid environment. Their replacements are coming up on 4 years old now and no signs of trouble. None of the bulbs were particularly expensive when I bought them.

I'd talk to the Linux guy about how fun it used to be to install debian 1.1 back in 1995. And how I've still got the same /home from that install

30s are rookie numbers. I'm 52 and still game regularly. I started out playing pong clones in about 1975 hooked up to my tv. I played a lot of zx spectrum games in the 80s, failed my degree in the early 90s because I spent far far far too long playing civ1 on my Amiga. Etc etc.

Debian guy could have just downloaded the nonfree installer that includes some common wifi and other hardware firmwares. There are some pragmatists at Debian.