Spyke

Replies

Comment on

How do you defy an immersive sim?

i think the main two things that make an immersive sim are open-endedness and mechanical depth. zelda is linear in that there's only one valid outcome, and TES is shallow in that skills are just "press button to action".

some outliers i'd class as imsims are, like... Divinity: Original Sin 1/2 and Hitman.

Comment on

How do you defy an immersive sim?

Reply in thread

an imsim isn't just an immersive game, it's a genre of rpg. examples include deus ex, dishonored, cruelty squad, system shock, thief, and others of that ilk. characteristics include mechanical depth, freedom of approach, open-endedness, and worlds that move with or without the player.

memes

Comment on

I'm a monster

Reply in thread

100g maps directly to percentages. 3.5g sugar per serving, 1 serving is ⅓ cup -> ??% sugar per unit weight. 9g sugar per 100g -> 9% per unit weight. makes it possible to actually calculate nutrient intake in your head.

Comment on

*Drips mic*

reminder that stonetoss is an actual fucking nazi and should not be allowed in polite society.

this is his normal shit at play, using people with coloured hair for opinions he disagrees with. this is a fucking "bootstraps" comment in 4-panel form.

Comment on

*Drips mic*

Reply in thread

all his shit works the same way, it's colorful and simple and memetic and can be read one of two ways and it's only when you see like 10 of them in a row that you realise his intended way of reading them.

fuck_ai

Comment on

What does it mean for a programming language to be AI slop?

with acceptance of vibecoded contributions, the trustworthiness of the tool - and things built with it - goes down. it pushes the burden of verification downstream, unless the maintainers can show that they have full understanding of and legal rights to, the contributions.

ken thompson (of unix and c) demonstrated in the 80's how he could add code to a compiler binary that in turn added code to everything built with it, including itself, without any visible traces in source code. researchers at the university of minnesota created deliberate exploits in the linux kernel for years without consent to test out the reliability of the reviewers, and the entire university was banned from contributing as a result.

when running tools with ai contributions, you risk doing both of these things on accident because when prs become hundreds of files big nobody can verify everything, and we've already seen ai inject seemingly nonsense code into projects which can be used as a backdoor.