There should be a competition of yak shaving. I've writing a Rust based canvas engine, with content via my own IDE, the runtime is fed data via WebSocket using my own API protocol, web proxy routing through a streaming and distributed load balancer using a new protocol, landing on my back-end platform running my own language, writing deltas to my own data store. https://www.adama-platform.com/ Why? For board game glo…
Accidentally making a language, for an engine, for a game
31–40 of 232 posts
Re: Accidentally making a language, for an engine, for a game
#32There should be a competition of yak shaving. I've writing a Rust based canvas engine, with content via my own IDE, the runtime is fed data via WebSocket using my own API protocol, web proxy routing through a streaming and distributed load balancer using a new protocol, landing on my back-end platform running my own language, writing deltas to my own data store. https://www.adama-platform.com/ Why? For board game glo…
It's not quite yak shaving, but it certainly is... something: > I mean, we are running Access in Wine in X11 on Linux in an isolated user account on our server slice that revision controls your Access database in git, and we're displaying it using VNC in your web browser in flash. People can't possibly want that. But they need it. https://apenwarr.ca/log/20120326 (Not mine, but seems relevant)
Re: Accidentally making a language, for an engine, for a game
#33Earlier quoted context omitted.
You should check out the comment section of a woodcrafting (or the like) Youtube channel. I think 'tool obsession' is probably a personality trait and one you're more likely to see in your day to day in programmers than in other crafters due to proximity to the internet. Oh, sewing rooms are another good hit for that as well.
In Table Tennis we call it "being an EJ" or "EJ-ing" where EJ stands for Equipment Junkie.
Re: Accidentally making a language, for an engine, for a game
#34It's interesting that this phenomenon is much more prevalent in game development, as opposed to (for example) web development: some people build their own web development frameworks, but it seems like every game dev tries to make an engine at some point. My theory why: good web frameworks consider developer experience to be of paramount importance, and invest heavily into examples, documentation, and API improvements…
My reason for making my own was partly that it felt like less work to write what I needed than to learn the intricacies of an existing engine. Also, back then the big engines didn't have as generous licenses as now.
As for Unity and Unreal: I found them both very easy to get into and get productive with.
Re: Accidentally making a language, for an engine, for a game
#35Scala for a game engine seems like an odd choice. What was the initial decision to choose it? Also, how’s the compile time? If it’s too long won’t it drive you crazy?
Sounds like it was for the compiler, not the engine itself. IMO Scala is the best general-purpose language going, but it's particularly good for data transformation, so it's a good fit for compilers.
Re: Accidentally making a language, for an engine, for a game
#36It's interesting that this phenomenon is much more prevalent in game development, as opposed to (for example) web development: some people build their own web development frameworks, but it seems like every game dev tries to make an engine at some point. My theory why: good web frameworks consider developer experience to be of paramount importance, and invest heavily into examples, documentation, and API improvements…
Re: Accidentally making a language, for an engine, for a game
#37It's interesting that this phenomenon is much more prevalent in game development, as opposed to (for example) web development: some people build their own web development frameworks, but it seems like every game dev tries to make an engine at some point. My theory why: good web frameworks consider developer experience to be of paramount importance, and invest heavily into examples, documentation, and API improvements…
In the same way, every React app eventually starts to look and act like the Reddit redesign, but many web developers consider that more of a benefit than a drawback.
Re: Accidentally making a language, for an engine, for a game
#38Re: Accidentally making a language, for an engine, for a game
#39Re: Accidentally making a language, for an engine, for a game
#40There should be a competition of yak shaving. I've writing a Rust based canvas engine, with content via my own IDE, the runtime is fed data via WebSocket using my own API protocol, web proxy routing through a streaming and distributed load balancer using a new protocol, landing on my back-end platform running my own language, writing deltas to my own data store. https://www.adama-platform.com/ Why? For board game glo…
It's not quite yak shaving, but it certainly is... something: > I mean, we are running Access in Wine in X11 on Linux in an isolated user account on our server slice that revision controls your Access database in git, and we're displaying it using VNC in your web browser in flash. People can't possibly want that. But they need it. https://apenwarr.ca/log/20120326 (Not mine, but seems relevant)