Stimmt. Passt wohl auch gut als Startrampe für diesen AFD-Pfeil.
What about square screens?
inb4 chaotic neckpain
Or a signal that you’d rather not support the worst way to introduce type systems to frontend dev. While I’m not sure that applies to DHH, I am sure there are other devs that understand compromising all your goals to codepend on Node or even JS itself isn’t that much of a win and rather see support for better options.
Thanks!
I need it to steal content from programminglanguages.
Relatable. If it wasn’t for good memories of its demo, I wouldn’t have picked it up back then.
Oni: not possible to rebind keys.
As for honorable mentions, Urban Chaos/Attack of the saucerman: I can’t imagine a successful remake.
Damit zu tun habend: Weiß hier wer, ob diese komische Pfannenhelden-Pfanne etwas taugt? Die Reviews sehen weitestgehend gekauft aus… Oder doch lieber klassischer Hersteller?
Seems to be specific to germany, though.
Yes. They are largely “ordinary” patterns explained in the context of game (engine) classes.
I learned about gameprogrammingpatterns which led me to Nystroms other stuff as well. Which taught me programming techniques I used in a professional setting a couple of years later.
Also learnt where to buy non-labelled tshirts.
Wie sieht es mit Hunderwasserhäusern bzgl Isolation aus?
assuming you’re meaning that the interpreter is called ad-hoc basically and isn’t the entirety of the system.
That was my assumption. Basically, that interpreter would have to run small snippets here and there typically on an irregular base. Thanks for reminding, I should probably clarify that as well.
If your interpreter can execute the systems in parallel,
Well, the way I thought of it was that the interpreter gets called in the systems in the first place, so that might become a problem.
Maybe I’m misunderstanding what the system is, is click_handler in the post a system, and if so, do systems only declare a single component of an entity as their input?
The way I figured would make sense was that, in the engine/game itself, the BoundaryComponent would have an additional field for registered scripts or that there would be an additional component just for registered scripts, to keep components lean. Not sure if that actually worked out in reality.
Then there would be a system for clicking on boundaries that would call such a script, if available. It’s probably a poor example, but since that system doesn’t touch much else, only the boundary component gets passed into the script. That’s not supposed to be a rule, though. I probably should clarify that on the post later on…
Makes sense, I guess. I really can’t comment on the wider implications with an ECS, though.
Possibly the same situation for Attack of the Saucerman. Dayum.
Oh well, realistically, an upscale and a few improvements wouldn’t have cut it anyway.