Hades II: love how everything ties up in 1.0.

Dwarf Fortress: my Fortress is coming together nicely. Food and drinks are plentiful, morale is good. Gotta strengthen my defenses though.

I love these grotesque historical events. The Cadaver Synod is pretty good too: pope hates predecessor so much he has him exhumed, trials the corpse and declares him retroactively not pope. Great Halloween fun!

We need version control for the version control.

deleted by creator

Start small. Like, really small. Don’t listen to the elitism about programming languages. Make stuff, fuss about the details later. Godot’s cool. Love2D’s cool. Nobody gives a fuck if you used a scripting language or an enterprise grade engine or if you wrote it in assembly like some cybermonk. Balatro was nominated for goty and was written in a “simplistic” scripting language (Lua with Love2D).

Stop Killing Games is about online components, relevant or not to the core gameplay, requiring the presence of a company server and acting as a remote kill switch. It’s not about putting the burden of preservation on the studios, but of reasonable “preservability”.

The argument that actually preserving video games is easy because we have preserved other forms of media does not hold. Digital data is problematic to preserve because most physical supports have ridiculously low shelf life compared to, say, paper. Storing it on computers which age even faster isn’t any better. Furthermore we have lost to time countless works from other media, some critical. Fortunately this all has little to do with what Stop Killing Games is about.

It clawed too 💅

I recalled differently so I looked it up. Here’s a video of a random person claiming their points. No code-in-box, just the console phoning Nintendo with cartridge inserted.

Nothing is stored to tie carts to hardware or accounts.

Do you remember the discontinued gold points program? For any brand new physical cartridge you could claim equivalent to 1% the game’s price. Obviously the points could only be claimed once, by a single account. This seems to point pretty strongly to carts being uniquely identifiable and to Nintendo’s ability of keeping track of usage.

Yakuza: Like a Dragon does this and I’m grateful.

When the game is such a precious labour of love, so obviously cared for, and constantly improved, that there’s no way the dev has any time left for gaming.

Both translation and subtitles have highly efficient tooling when in the hands of a professional. Translators nowadays use a mix and will build up a dynamic database as they go through a corpus that needs coherence. What’s bad in this instance is not the usage of some AI, but of a badly adapted AI and ultimately of mediocre results which gives an amateurish impression.

sunk cost fallacy let’s gooo

So that we can discuss the issue without triggering abuse survivors would be a reason.

having to wait for javascript to load, decompress, parse, JIT, transmogrify, rejimble and perform two rinse cycles

This is whole sentence is facetious nonsense. Just-in-time compilation is not in websites, it’s in browsers, and it was a massive performance gain for the web. Sending files gzipped over the wire has been going on forever and the decompressing on receival is nothing compared to the gains on load time. I’m going to ignore the made up words. If you don’t know you don’t know. Please don’t confidently make shit up.

EDIT: I’m with about the nags though. Fuck them nags.

Some non peer reviewed paper with a tiny sample size is hardly enough to go “The Science has spoken”. On the other hand, one can make an appeal to the intuitive idea that lack of practice implies lack of skill.

This immediately points to the pernicious effects of touting LLMs as a machine to do all the thinking for you. Heck, the enthusiasts are even using LLMs to do their social interactions for them.

This is a warning to people as much as workplaces: is this task you’re offloading to LLMs really a skill you want to see atrophied?

Oh I love it when the language has advanced type inference! I have fond memories of tinkering with Haxe.

I know far too little about compilers & interpreters to have anything to say about performance so I’ll leave that subject to wiser programmers.

What I can say about the usage itself of dynamically vs statically typed languages is that I struggle with assessments that attempt to quantify the differences between the two paradigms. I’ve come to consider programming has a craft, and as such the qualitative properties of the tools, and especially the languages, matter significantly.

I’ve been switching back and forth between dynamic and static languages lately. Although dynamic languages do feel more straight to the point, static languages are easier to navigate through. All that typing information can be harnessed by intellisense and empower the non-linear reading needed to understand a program. That’s valuable for the whole life cycle of the software, not just the time to reach initial release. It’s kind of a rigid vs fluid dichotomy.

So you take a small round slice from a fresh baguette and toast it. While still hot you put some brie or camembert on the toast. The point is for the cheese to get a little sweaty byt not runny. Finally cut a date open, pit it, spread it on top of the cheese. Heaven.