The post isn’t claiming perfection. It’s claiming production ready. Very different things.

The confusion there is the claim that good/perfect means done. It means ready for use and extensible.

Note: I’m not agreeing/disagreeing with the claim. Just clarifying the point

Hey now, they aren’t Nazis. Nazis at least believe in something, even if it’s something terrible.

Also, Pepsi Max is a zero calorie drink, so 1 a day is hardly a lot. Three artificial sweeteners aren’t the best for you, but OP shouldn’t feel like they are ruining their health on that.

To this point, for me, it was all about the bubbles. So replacing with a seltzer water did wonders. Sometimes I still have a craving to pound bubbles real quick.

Not sure if you’re suggesting that it’s a problem of knowing the language or sarcastically saying that Node.js allows for developers to not know what’s happening.

On the case that you’re thinking it’s a knowledge of the language issue, that’s not what I’m getting at. Typically, what I see with full stack developers is an over reliance on frameworks to do the heavy lifting to the detriment is their skill sets. Often not knowing how to optimize DB queries or trouble shoot performance problems. This works fine in purely CRUD use cases, but falls apart when scaling using more complex patterns starts to occur. I’ve spoken with Sr and staff full stack developers that truly believe the only thing you need to do in order to scale a web app is add nodes.

I’ve worked with my fair share that were front end devs that didn’t understand the backend, too

I’ve beaten the game about 6 times now and while I’ve certainly encountered minor glitches that made me laugh, I’ve never had issues that were game breaking at all. And the fire giant included.

I always hear stuff like this but in hundreds of hours of play on both PlayStation 5 and PC. I’ve never experienced any serious bugs. It’s so interesting to me that experiences can vary so much between people.

I only do that when the problem space is interesting.

Most developers are just implementing CRUD using a framework that does most of the work. There isn’t the interest motivation to keep on trying to fix things.

I’m going to be honest. I’d be really annoyed if somebody kept asking me for a ride because they don’t want to be a driver. I also hate driving but it’s necessary where I live for most cases.

Hopefully you’re taking the inconvenience to others into account when asking for a ride to places.

Some things we would want to install aren’t in the official repos. Downloading the deb file is a solution to that for newer users.

By this description, year zero is the time between the 0 and the 1 for the same reason the time between 10 and 11 is the year 10.

It’s not attitude they are giving you. It’s strong recommendation. It’s the strong recommendation of the entire Linux community.

Sudo is different than run as admin and is not intended to be used to do things the way Windows does them.

The biggest thing he got wrong is the assumption that it’s good programmers writing libraries.

Windows reports using binary and continues to use the Greek terms. Windows is still the holder of largest market share for PC operating systems.

This is such a weird take to me. We don’t even colloquially discuss computer storage in terms of 1000.

The Greek terms were used from the beginning of computing and the new terms of kibi and mebi (etc.) were only added in 1998 when Members it the IEC got upset. But despite that, most personal computers still report in the binary way. The decimal is only used on boxes for marketing terms.

Many organizations vendor packages in the repo for a number of different reasons and languages. Not just for node.

Human made changes is likely not what caused this image to occur.

111 files with that kind of change count is most likely a dependency update. But could also be that somebody screwed up a merge step somewhere.

None of those things are required but they sure do help.

Most products have always had bugs in them, though.

Don’t worry. They’ll change it again next week.