Sue-dough & s-s-h here. Can’t speak to zsh yet, haven’t actually talked about it w/ others yet. How about /etc/? Sometimes I call it “e-t-c” but others I say “etsee”

Most of the time, the product itself comes out of engineering just fine and then it gets torn up and/or ruined by the business side of the company. That said, sometimes people do make mistakes - in my mind, it’s more of how they’re handled by the company (oftentimes poorly). One of the products my team worked on a few years ago was one that required us to spin up our own ASIC. We spun one up (in the neighborhood of ~20-30 million dollars USD), and a few months later, found a critical flaw in it. So we spun up a second ASIC, again spending $20-30M, and when we were nearly going to release the product, we discovered a bad flaw in the new ASIC. The products worked for the most part, but of course not always, as the bug would sometimes get hit. My company did the right thing and never released the product, though.

If Google had a baby she would drop it on its head spike it at the ground

Carefully-calculated trace lengths and signal pathing have left the chat

As someone that works writing firmware for SAS devices… it’s happened all too many times

Ah, duh! Totally forgot about that part of the article, lol

The z80 actually just went EOL last week! After nearly 50 years.

Shut

Yes! The other comments are incorrect. This is a condition known as reversion. These trees are actually a mutation of a typical conifer, known aptly as a “dwarf conifer”. Mutations are oftentimes unstable, and can revert back to their original form - that’s what has happened to this tree. One of the branches (or multiple, potentially) have reverted and it’s actually growing a normal-size conifer on those branches now. Kinda neat! But can also be very bad for the tree.

More info can be found here: https://bygl.osu.edu/node/1602

Similar things can happen with variegation in leaves (reversion, that is).

I’ve got 3D pipes running on my spare Win10 machine :) fills me with nostalgia every time I see it, even still

I started with C++ too, and then ended up finding a job writing firmware pretty much all in C. There really hasn’t been anything we’ve run into that’s made us consider switching to C++; being able to (and needing to) have complete control over your memory means you can do some pretty fancy stuff with the tiny amounts of memory on our ASICs.

We’ve been eyeballing switching to rust a little bit, but really only for other applications; the root of our main code base is over 25 years old at this point and a rewrite would take a Herculean effort.

Meh? I write pretty much exclusively in C and honestly I still like C++ better, and wouldn’t mind switching to Rust either

We need more OPs like this, kudos

the fitness gram pacer test is a multistage…

I’ll let you guess if that was my most or my least favorite

But we need to know what it taught him about B2B sales!

I’ve tried out FreeCAD and it’s decent - but it’s really tough to get a hang of. Ondsel has a bit of a better interface imo and is based directly off of FreeCAD. Maybe give either of those a shot?

True, he is sitting at a terminal - but it appears to be connected to an IBM 5150 or similar. So maybe not so dumb!

Looking at the rest of things more carefully - very likely a 5150, if not definitely. Iconic and hugely popular PC for its era, so it would make sense for sure.

…absolutely, positively, super false. I work in a sector where we’re constantly dealing with huge capacity enterprise SSDs - 15 and 30 terabytes at times. Always using RAID. It’s not even a question. Not only can you have controller malfunctions, but even though you’ve got what’s known as “over provisioning” on the SSDs, you still need to watch out for total disk failures!

Retro problem? All of our monitors at work use VGA… not to mention pretty much all servers

ELI5 what does this mean for the average Linux user? I run a few Ubuntu 22.04 systems (yeah yeah, I know, canonical schmanonical) - but they aren’t bleeding edge, so they shouldn’t exhibit this vulnerability, right?