thinking of She,.. (my 300zx)

https://cryptid.cafe/notice/Aqtd2UeuKb05roiVsG

this meme has rewired my brain and i always think "explodives" now instead of, yknow, the correct word

To err is human
To scream is vulpine

for any robotgirls that need to hear this

Valve have just updated the Source 1 SDK on GitHub to the latest code based on Team Fortress 2, effectively making TF2 code source available.

SDK was previously updated in 2014.

@Shivaekul @kasdeya i think even microsoft’s proposed convention isn’t that good. would Filesystem ID become FSID? this seems like a 4 letter acronym instead of two 2-letter abbreviations

not to mention the (small, but still present) cognitive load of needing to remember to change the convention depending on the length of the abbreviation

@Shivaekul @kasdeya what you brought up is actually what got me curious about this in the first place!

overwhelmingly the most common way to abbreviate identity/identification/identifier seems to be with “ID” (with both letters being capitalized) since, i think, the alternative would be “Id.” or “id.” when written in plain english. the latter is maybe more syntactically correct but it seems like the tendency is to use the former.

i thought it was interesting that in the case of “player ID,” using PlayerID seems to be the most intuitive and clear except when compared to a case like “XML HTTP Request” where XMLHTTPRequest reads like a random string until the last word. Javascript uses XMLHttpRequest which is maybe the worst of both worlds. if i remember correctly, microsoft has a naming convention that is approximately: “Only capitalize each letter if the abbreviation/acronym length is 2 or less.” … but they are also the ones that implemented XMLHttpRequest

@kasdeya hehe that's actually the exact reason i made a second poll! aesthetically, i like the capital letters for abbreviations and acronyms but i totally agree with you: clarity is way more important

@rowan as weird as PlayerId and XmlHttpRequest look, I still think they’re overall better because they remove ambiguity which is much more important (IMO) than aesthetics

my first impulse in the first poll was PlayerId but I didn’t remember why lol (just a vague sense that it was less ambiguous) but this second poll reminded me of exactly where that ambiguity comes from

when using upper camel case, how should "player ID" ideally appear without considering pre-existing project or team naming conventions?

@kirakira big same, it was very very good for baby tran rown

@vivi a ok! 💜 thank you :3 i'm big dumb and just wanted to make sure i understood before giving my very well informed opinion

@vivi a ok that makes sense! thank you for explaining

so the three-stage System is responsible for

1. before: initialization/checking its run conditions
2. onEach: Do A thing
3. after: cleanup / “finally” (in the sense of try / catch / finally) type things?

i think i like “Behavior” or “Runner” for that, but i also know Nothing

CRT photography is an art form
(There are tougher ones, but getting a good photo of a CRT screen is still tough)

girl on girl virtualisation

@vivi

i dont know much about kotlin so i'm Extremely out of my depth here but in AGK, do systems carry additional capabilities outside "take a list of entities and Do A Thing with them?"

@vivi a type so well integrated that the engine just assumes every type is a system

it is decided so: the Systems in my ECS shall be named "". I am confident that the JVM will be absolutely fine with this name and will not cause any issues

@ShadowJonathan a!! thank you!! 💕