[deleted]
Accidentally making a language, for an engine, for a game
21–30 of 232 posts
Re: Accidentally making a language, for an engine, for a game
#22I don’t get why are programmers so obsessed with the tools they use for the job? More than any profession
You should see the arguments gardeners can get into over lawnmowers
Re: Accidentally making a language, for an engine, for a game
#23I don’t get why are programmers so obsessed with the tools they use for the job? More than any profession
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
#24I don’t get why are programmers so obsessed with the tools they use for the job? More than any profession
Why are musicians so obsessed with their instruments? Just use the right tool for the right job, don't call yourself a "pianist" or a "drummer", call yourself a musician.
Re: Accidentally making a language, for an engine, for a game
#25It'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…
Take a look at Godot. At least then it will be "our own game engine" rather than "my own game engine".
Re: Accidentally making a language, for an engine, for a game
#26I don’t get why are programmers so obsessed with the tools they use for the job? More than any profession
Obsession with the tools is part of every interest/job/hobby!
There's always someone who thinks: "I could make this better". Some of them even try to. Emphasis on try :)
Re: Accidentally making a language, for an engine, for a game
#27I don’t get why are programmers so obsessed with the tools they use for the job? More than any profession
Why are musicians so obsessed with their instruments? Just use the right tool for the right job, don't call yourself a "pianist" or a "drummer", call yourself a musician .
Yeah semi-pro musicians are probably the worst. It's really easy to get obsessed with both accumulating shiny new (or vintage) toys, and tweaking your favorite instruments so they're set up exactly how you want.
Re: Accidentally making a language, for an engine, for a game
#28In the limit, every configuration file becomes turing complete.
Re: Accidentally making a language, for an engine, for a game
#29It'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…
Take a look at Godot. At least then it will be "our own game engine" rather than "my own game engine".
Speaking of making a language for an engine for a game...
Re: Accidentally making a language, for an engine, for a game
#30The way structured concurrency is implemented in Vale is exactly what I've been missing in every language I've been working, including Rust which gets pretty close. Amazing job!