Function arguments are unfilled holes. So are interface declarations.
Both are (fairly) programming language agnostic, but in the context of an editor, would become specific. The editor would have to know _how_ to represent them in the code’s language.
What about the animals that have been domesticated to be pets? It's arguable that their native habitat is the home at this point. Although, I do hope we stop capturing the animals which aren't domesticated (most "exotic" pets).
This is exactly the point I saw in a recent x post, that building anti-bot detection was incredibly difficult because some people exhibit bot like behavior.
Blizzard employee once told me anti-botting in WoW was extremely challenging due to the number of real people that acted identically to bots.
Every assumption was invalidated:
- unbelievable # of consecutive hours played
- consistently repetitive patterns of movement and clicks
- farming patterns that aren’t considered fun (“why would anyone do that”)
- solo, no external engagement
- goes on for months
I think what happened was that it became his full time job, and he started to need to be able to make money from it. At least, that's what I remember; I haven't seen much about it as of late.
I'm still just not really comfortable with the ethics of withdrawing source code that you previously published. There are tons and tons of things he could've simply kept to himself on top of his first release, but he chose to take back the entire release instead.
Like, he seemingly fully intended it for the public because it's cool and interesting and he wanted to show how it worked, but then he simply changed his mind and completely removed all of it? Makes me doubt he has the public interest in mind at all, because he could've still developed the Steam version and kept that version closed source, but he just decided to take back all his goodwill instead
> Makes me doubt he has the public interest in mind at all
But why?
He's doing what he loves. He's able to support himself doing that. What he chooses to do with the internal product of his labors is his choice. Committing to open source software is a big lift for a lot of people. Maybe he didn't want that.
Once again, I have issue only with his taking it back after already open-sourcing it. It felt disingenuous. That's all. I would have no issue with simply never open-sourcing, but he open-sourced it and then took it back.
He could've never open-sourced it in the first place. He could've archived it and kept the rest of the development private. He could've done anything other than what he did. It's one thing to take back something that you never intended to release, but he fully intended to release it and even made a video about how it's fully open and available, but then he just went actually nevermind.
It's just so, infuriating that he would take it away like this after he told everyone he was giving it out. To me, that act of taking it away takes precedence over whatever I'd think if he'd kept it closed all along.
Edit: I just looked it up and apparently he did keep an archive online. I swear he'd taken it down before and there was a whole thing about this, but maybe he put it back up later? It's here: https://github.com/ange-yaghi/engine-sim
I was upset when I heard it'd been taken DOWN after it already went up. Not based on literally any expectation of any future support or literally anything. Literally at that point it had already been published and then reportedly unpublished. It's back up now and learning of that resolved my frustration, but man you are making a lot of incorrect assumptions about me, even after I clarified myself multiple times on this exact point.