Why give the game a number? Just call it after the new protaganist, while creating another game that lays a lot of groundwork for a whole new generation of gaming. (It’s just VR gaming this time.)

HL Alyx was really groundbreaking for its time in the VR world. Few other games combined the user experience, VR immersion, and grapichs into a good game. Just like how HL2 was groundbreaking in the physics department.

Kinda. But once you pay them, you also start to expect things from them. You inadvertenty put pressure on them. This will drive some of the volunteers away.

Boston looks much easier to navigate though. Much clearer road hierarchy, meaning better flowing traffic, and less traffic near houses and shops.

Disclaimer: above statement is based on the image posted here, not on knowledge on the actual situation.

Why take pill, when you can install schnapps?

The large wheel next to the cabin is also messed up. It means the cabin must be smaller than the track width, since the cabin is squized inbetween the wheels. But in reality the cabin is always wider then the wheel base.

I agree that the lines look sharp, but the composition makes no sense. The giant wheel next to the cabin is just weird. Why is the wheel bigger? And why is the cabin not wider than the track width? This looks like a tractor, not a locomotive. The steam is comming from the coal storage, but not from the engine. And why does the coal storage have a chimney anyway? Then there are the weirdly shaped coupling rods. These mistakes make no sense in the context of a steam locomotive, but they look plausable. I’m no AI expert, but it certainly is a weird looking steam locomotive.

…

I’m starting to think this was designed wrong intentionally. What better way to farm engagement then to wrongly draw a train in a meme about autism, on Lemmy?

Best do that with something that hides the taste well. Maybe create a drink so aggressive that it might as well be a cleaning product. Just add some caramel to paint the whole thing black and you’re good to go. People will love you coca product.

I remember using mumble in a time when smartphones weren’t even a thing yet. Love to see the open source tool outlive everything else!

Why the complicated if statements to check the sign? Just let the number overflow. Would be functionaly the same, and result in much prettier code.

But how does the Rust compiler do that? What does it actually check? Could I write a compiler in C that does this check on a piece of Rust code?

C is so simplictic, that if I can write a piece of functionality in C, I must understand its inner workings fully. Not just how to use the feature, but how the feature works under the hood.

It is often pointless to actually implement the feature in C, since the feature already has a good implementation (see the Rust compiler for the memory safety). But understanding these features, and being able to mentally think about what it takes in C to implement them, is still helpfull for gaining an understanding of the feature.

I mean, at the end of the day, if you really understand your language of choice, you know that it is jusf a bunch of fancy libraries and compiler tricks of top of C. So in my mind, I’m a fully evolved programmer in a language, when I could write anything I can write in that language in C instead.

I have this experience with a certain type of pedestrian traffic light “button”.

I quote button, because nothing physically moves when you press it. I’m not sure if it registers pressure or heat, but you don’t even feel anything move when you press it.

Usually when you press the button, a red text lights up on the button, telling you to wait. This text gives you feedback that the button registered your press, and the traffic light will schedule a green light for you.

However, sometimes you didn’t press hard enough, and the text doesn’t light up. Simple solution: press harder.

But there is a scenario where it doesn’t matter how hard you press, the button won’t light up. You keep staring at it, while slamming the damn thing with the fury of a Hulk wealding Mjolnir. Still, nothing lights up. The reason: the light instantly went green, so it never needed to light up the text telling you to wait. And all that time slamming your fist on the button, could have been spend crossing the intersection. Instead you have been standing there, looking like a drunk person having a fistfight with an inanimate object.

Considering std::cout should only directly be used when you are too lazy to place breakpoints, I totally get the decision to auto-flush.

I remember a javascript library where the was a function that returned, according to the documentation, “a color”. Did it return an object with 3 fields? Were those fields RGB or some other color scheme? Is it a string encoding a color? What format is that string? None of these questions could be answered without just running the code, and analyzing the object you got back.

Do you mean that programming languages are hard to read/write, or that the languages themselves are poorly designed?

In the former case, I invite you to read machine code. Not assembly, but straight machine code. Just zeros and ones as far as the editor can see. Any popular language is better than that.

In the latter case, I invite you to look at the design of an arbitrary natural language. Weird grammer rules, regional differences, loan words that don’t fit in, etc. No programmming language is worse than that. Although I would argue that Javascript has all of those problems too in some degree.

Simple solution: only allow lower case characters in file names.

Of myself of the now dead purpetrator?

The worst thing is: you can’t even put an int in a json file. Only doubles. For most people that is fine, since a double can function as a 32 bit int. But not when you are using 64 bit identifiers or timestamps.

But I love coding at work?!

The problem is that every living entity in a 10 kilometer radius around me, seems to be hellbent on getting me to do anything but coding. Refining work estimates, fixing badge access rights, fixing a driver issue, telling people that you cannot do 1000 things at the same time, teaching the new developer how shit (doesn’t) works, mangling Jenkins into a functional state again, explaning that thing I did a year ago but is only now used (it was very high prio a year ago), writing documentation that noboby ever reads, progress meetings, specialty group meetings, knowledge sharing meetings, company wide meetings, etc.

I have a ton of legs. Waayyy more than 2.

What can I say? They were cheap, and I love chicken.