nanochad

Tools require manpower to maintain, which costs money.

In F2P games you need to spend hundreds of hours to either grind to unlock basic functionality, or even if they don't have grinding, you still need skins or everyone will leave your party because they assume you're a noob. Skins drag down game performance. I've seen literal billion dollar games where it ran perfectly fine until they added waves of skins. Also multiple games where each time someone comes near you with a skin, the game freezes to load the skin (probably a blocking socket call in the middle of the main game client loop, as that's the quality you get in such games). And in most games, emotes and skins allow unintended behavior that gives advantages to their users. This is what happens when you focus all dev work on designing skins and zero thought goes into how they would affect the game.

Now, since you don't want to spend hundreds of hours unlocking the ability to play the game on a level playing field, you will probably want to spend money to unlock these things. This will costs hundreds of dollars, far more than you would pay for an actual real game. Even if you unlock them the free way, there's a high chance your account eventually gets banned. As, once again, the studio has no experience in anything other than skin design, and have no idea how their game actually works and will cave in to every single basic cheating allegation and social crap like "he was in my game therefore he stream sniped me". Again, if you have ever played a game in the last 30 years, you would be well aware that most people in charge do not understand very basics like how you could infer an enemy is near you because you heard him behind the wall, or he triggered something on the map somewhere that tells the other player that trigger was indeed triggered across the map.

> zero impact

Obviously false unless you have never played a game before.

Splitgate is annoying because some skins look red and blue and you can't tell what team they're on. I haven't played enough to find out how long it takes to get used to that. It's also a poor quality game and precisely the type of thing that comes to mind when I hear F2P (I realize Splitgate may have started out as a fun project more than a microtransaction cow from the outset). I quickly returned to Halo. I prefer playing games that actually feel like real products and are created by people who know what they're doing.

We have placed full sanctions on Russia. It's common sense not to rely on them too much.

>If you can meet these expectations in fewer hours than you are supposed to work, then you shouldn't just find more to do. Instead you should do something different.

This one really struck home for me. I will often quickly finish a task like refactoring a class heirarchy, then I will spend another 3 hours looking at it and the surrounding code to check for any unoptimal usages. But it always turns out to be a waste of time, because we have much bigger things on the backlog. Thanks for reminding me.

Routing should be done in software.

For some of us, there is no improving. If someone brings up a topic I know well, such as C, or the POSIX shell, I will start explaining the nuances which everyone gets wrong and after a minute I will be heavily breathing without realizing it. State that milliseconds don't matter, and I will start shaking and explain why Java is the worst thing to happen to computing, and maybe insult you for using it, as if you're the enemy all of a sudden. I also tend to point out spelling and grammar mistakes in people's writing online. I've tried to fix this. I am aware of the problem in me. I have tried explicitly preventing the usual trappings. But at the end of the day I always go back to the same old habits. Even this post took me 10 minutes to edit.

Python is what has been popular for the last 15 years. Scientists are not programing language geeks, they just use whatever is popular, viable, and established.

Immediate mode GUI is a very nifty concept. Kind of like learning about fully persistent data structures for the first time. But I wonder, does it scale?

> You could open up system functions in the editor, modify and compile them while the machine was running.

Why would you want to do that other than hot patching a system that can't go down? Testing new changes requires more time than rebooting. If you just want to test simple changes, most debuggers can do that.

> Everything worked in a single address space, programs could talk to each other in ways operating systems of today couldn’t dream of.

And with a single address space you have win9x security.

> A modern UNIX system isn’t self-contained. I have 4 UNIX systems on my desk (Desktop, laptop, iPhone, iPad) I’m contentiously using the cloud (iCloud for photos, GitHub for text files, Dropbox for everything else) to sync files between these machines. The cloud is just a workaround for UNIX’s self-contained nature

This is just your use habbits. Nothing is stopping you from using NFS or SSHS. Someone who feels the need to use iCloud for whatever trivial convenience it provides is unlikely to benefit from a Lisp machine's ability to edit code on the live system.

> Then we add a gazillion programming languages, VMs, Containers, and a million other things, UNIX is a bloated mess of workaround for its own problems. We need a replacement, something that can be built for the modern world using technologies that are clean, secure, and extendable

The same thing will happen with any OS given enough time. Lisp is also not secure. It's prone to side channel and eval bugs.

> eliminate memory leaks and questions of type safety,

Lisp is not type safe.

But the desktop is just snap and the windows store now.

This could have been avoided by not having your entire business be at the mercy of a single company and whether any of its one million agents makes a mistake.

For cavemen or office workers?

Translation: we should all be forced to go to work because we are dweebs and don't matter over our other social peers.

There are ways to establish communication to humans other than going into work to use their keyboard and monitor.

Sad how classical languages like Pascal family, Lua, and Fortran aren't often used anymore.