

The discussion should be simple: “You are not having Greenland. If you try to take it, the snow will be red with American blood, and the next guy who tries to shoot you at one of your rallies won’t miss”


The discussion should be simple: “You are not having Greenland. If you try to take it, the snow will be red with American blood, and the next guy who tries to shoot you at one of your rallies won’t miss”
For me it was Ignition, a top-down racing game where you could play as a police car, a school bus, an ambulance, a yellow car or a blue beetle car.
There was also another racing game I don’t remember the name of and likely never will, because it was a game that came on a blue floppy disk and actually was a 3D racing game, and all I remember is that it was a demo for a game that had you doing street races and it wasn’t open-world, it was with proper tracks and it was a level at sunset in a city, with no traffic. As far as I can tell, it shouldn’t really have been possible to have a fully 3D game on a floppy disk, but I guess since the game was just a demo, it could be squeezed down.


The only times I’ve seen devs do inline comments in their code is when it’s been done by AI, and I can tell it’s AI because the comments are all useless and describing what’s happening, not why.
Technically Vader never once destroyed a planet. Tarkin gave the order to destroy Alderaan, no planet was destroyed until Force Awakens, by which point Vader was already dead.
I wish I could say the same. I didn’t get into programming for the money, I got into it because it was the only thing I was any good at and generally wouldn’t discriminate against me because of my disability.
Anyone who complains about code not compiling on the first try likely hasn’t been coding for very long. Getting your code to do what you tell it is easy, getting it to do what you want is hard.