Live data from Hacker News

Simpsons Hit and Run source code (2003)

github.com

131–140 of 177 posts

Re: Simpsons Hit and Run source code (2003)

#131
post #25

Earlier quoted context omitted.

Was pleasantly surprised by the comments. But while the codebase is grokkable (every line is simple), it's brittle [1]. Not saying it's a big deal: brittle codebases are fine when the codebase is only going to be touched by a small amount of people. Less so when the code is going to be used and modified for decades by thousands of people (in OS, compilers, browsers...). [1] Unchecked assumptions everywhere, #ifdef wi…

singeltons are rather common in game code, it's not that bad. What's wrong with ifdefs for platform specific code though? Alternative is to have different compile-time paths.

In my experience (with gamedev) it often leads to your game silently breaking on platform you're not building it for. Proper CI will catch this, but it still makes the feedback loop longer.

Re: Simpsons Hit and Run source code (2003)

#132

Earlier quoted context omitted.

I really dislike framing people from different eras as homophobes. Back when this was written this was seen as just a joke, no harm intended, no homophobia involved whatsoever.

We actually live in an era where homophobia is becoming even more socially acceptable then the 2000s, so this is a weird hill for you to die on.

[flagged]

Re: Simpsons Hit and Run source code (2003)

#134

https://github.com/search?q=repo%3ASvxy%2FThe-Simpsons-Hit-a... Only 50 instances of the word "fuck" in the entire repo.

Real brotherhood forming during this game development: https://github.com/Svxy/The-Simpsons-Hit-and-Run/blob/eb4b34...

Re: Simpsons Hit and Run source code (2003)

#135
post #59

Earlier quoted context omitted.

I don't understand that, why spend so much time making something only to never release it?

You state you will never release it avoid take down, and then when it’s done you “accidentally” get “hacked” and let the Streisand effect handle the rest. It’s either that or developing a remake in complete secrecy and drop it on the internet as a fait accompli. For examples of what happens if you don’t employ underhanded tactics, take a look at AM2R or the Chrono Trigger remake.

That I can understand

Re: Simpsons Hit and Run source code (2003)

#136
post #17

This is a blast from a previous lifetime! I worked at Relic Entertainment during that time. Both Relic and Radical's offices were in Yaletown in Vancouver at that time, IIRC. Radical ended up moving to Main & Terminal. I worked on Company of Heroes and Dawn of War during this era. The code looks very familiar. It's the same style of C++. The code looks very similar to Homeworld. https://github.com/HomeworldSDL/Homewo…

Thanks for sharing that info on Neall... It had been a few years but he was great to work with on ps3 rollout and other tech fun back in the day. Sorry to hear it :(

Re: Simpsons Hit and Run source code (2003)

#137
post #72

Earlier quoted context omitted.

I mean KDE did take over the desktop, with most of our apps living in the browser and most of the browsers being based on their code.

I understand that you're being facetious, but the reality is much darker than this historical trivia might suggest - the web platform is today largely controlled by one mega corp.

I’m being genuine.

Re: Simpsons Hit and Run source code (2003)

#138
post #79

Earlier quoted context omitted.

Yeah, I truly lament the ruination of the Company of Heroes series. The newest installment, CoH3, is so atrociously soulless, greedy and straight-up broken that it's basically almost mocking the playerbase. Similar things are happening with the Men of War franchise (a similar but more realistic game).... enshittification is happening everywhere, and nothing is becoming better.

The problem with making a great game is that people will play it forever. CoH was amazing. CoH2 was eh. And CoH3 is atrocious. I hate SaaS with a passion, but it provides a financial incentive to continue improving an already great product.

What makes you think that the changes that are made in SaaS are always an improvement?

Sometimes that models permanently destroys something without providing users a recourse for going back. See: Warcraft II, or World of Warcraft

Re: Simpsons Hit and Run source code (2003)

#139
post #46

The release note has some nasty casual homophobia. Eurgh. https://github.com/Svxy/The-Simpsons-Hit-and-Run/releases/ta...

There was a period in the 90s and 00s when gay meant lame. I’m sure many used it hatefully, but schoolboys were just using play yard lingo. When gay began to mean GAY, people stopped using it to mean “lame”. This poster is probably 30-50 years old and likely meant no harm. There’s an internet meme “fake and gay” which has nothing to do with homophobia but instead refers to the 90s usage.

People stopped using it because of enormous mounting social pressure and increasing awareness of its homophobic roots, not as some innate linguistic slide. The "fake and gay" meme comes from 4chan where it has persisted since "gay" was still a pervasive pejorative term, not as a winking post-modern reference to it. Your optimism about the banality of this history is whimsical and it'd be nice to live in that world, but the actual harm of that usage cannot be divorced from the term regardless of your individual intent.

Re: Simpsons Hit and Run source code (2003)

#140
post #46

The release note has some nasty casual homophobia. Eurgh. https://github.com/Svxy/The-Simpsons-Hit-and-Run/releases/ta...

There was a period in the 90s and 00s when gay meant lame. I’m sure many used it hatefully, but schoolboys were just using play yard lingo. When gay began to mean GAY, people stopped using it to mean “lame”. This poster is probably 30-50 years old and likely meant no harm. There’s an internet meme “fake and gay” which has nothing to do with homophobia but instead refers to the 90s usage.

[dead]
Post reply on HN