cakeistheanswer

I mean it predates a lot of the pervy anime, but Usenet looked the same at the start with lots of Unix/computer boards and an alt.

Computer enthusiasts gonna enthusiastically talk about computers. People who pick up and move to a new platform are likely to be united around being technically competent enough to get there first, and everything else second.

Definitely worth running through vim tutor at least once.

It's beyond typing speed, things like piping out strings to utilities is using one program to write another, you aren't just getting faster because of access, it's a paradigm shift.

Edit just for fun: im a non Dev dummy who happened to grow up in a Unix household. Even having dropped vim for helix and bounced around the MS admin/Apple IT space for 30+ years. When I switched to Linux I could still remember binds I'd set up and last used at 9.

Kinda like riding a bike.

Efficiency.

There's 0 chance if you have to pick up your mouse that you can keep up with a Unix gray beard.

That's just editing, if they're from the emacs era there might be nothing you can do with text faster across their whole system.

I like vscode as a entry point, but if you care to get faster learning just vim motions and sys utils alone is going to cut time from the process.

This is incredibly true. The hardware manufacture process is a slow turning and cost centric wheel, but it's always forward looking. If it doesn't exist today you are building around compromises made outside the scope of your concerns.

Anyone whose had to work on DEC or Sun hardware can describe in excruciating detail about how minor implementation differences in hardware cascade down the chain. (Missing) Rubber washers determined a SAN max writes once, lest the platters vibrating cause the chassis to walk across the floor.

'Universal' support is always a myth, and carving up what segment to target is shooting one moving target while standing on another one unless you have exclusive control of implementation of the whole chain (apple).

For the most part what kind of company you are is what kind of product you're selling or making money off of.

So you could contend that Tesla is a battery company or a car company feasibly. Nobody ahead of the AI bubble would have mentioned Tesla and artificial intelligence in the same category.

Besides, if it's what he makes money selling Tesla is a tax credit company.

I think it's grossly undersold personally. What valve has managed is getting the single target platform open source could never agree on.

It's a small miracle, and it bleeds over into stuff like device driver support in a way I don't think most people who didn't deal with Linux in the 2.x era immediately appreciate.

If Linux on the desktop has a surge, they did a lot of the legwork.

From a macro economic perspective, (and im not advocating for a conspiracy, just aggregate business interest) they're dropping energy usage so they can pay less on their electricity bills.

So actually a double fu. get less so they can pay less rent, to provide lesser service.

Because rent seeking is the only tech bubble left.

I didn't mean to imply they'd roll in buggy packages, by virtue of release; just that Fedora's function is typically regression testing for the money making product.

The testing is for the much more marketable enterprise window.

Generally Fedora's purpose is to make sure nothing gets into redhat (RHEL) Linux. So if there are breaking changes to things, you'll be getting them.

Historically if people had wanted to learn I'd push them towards Ubuntu because its Debian based, meaning familiar enough to most of what runs the modern internet that I could eventually (I'm not a Linux admin) fix.

These days if you just want to use it I'd pick Linux mint, just since they seem to be orienting towards that way. Arch or SUSE based something if you want to learn more about how the packages you install work together. But the choice in distro honestly feels more like an installer and package manager choice than anything. a distro is just a choice of which thousand things to hide in a trenchcoat.

I just ideologically don't like IBM and would rather hand in my bug reports to the volunteer ecosystem.

Even if you're right, those organizations still have to be dragged kicking and screaming to do the right thing.

It's not a quick solution, but the answer is more education about the space, so that there are more voices.

I ended up on a first gen dell developer xps and didn't win the Intel nic lottery. Dell's Ubuntu repo bricked my laptop a dozen times til I moved to arch, which actually had the decency to include the broadcom driver.

The hardware is alright, but the total lack of effort in maintaining has been from the jump.

+1 here for the arch recommendation as an ex ms sys op. Browsing their repos was outstanding for retooling, most of the config problems you hit are a great way into the ecosystem.