Leaf is a good name for a language.
apparently someone else thinks so too: https://github.com/leaf-lang/leaf
Sadly, I must say goodbye to Leaf, my programming language
11–20 of 132 posts
Re: Sadly, I must say goodbye to Leaf, my programming language
#12I had a similar thought process (but luckily without spending time implementing something). I want to write a game. I thought, "None of the current languages works quite the way I want. I know! I'll write a language specifically for my game and just keep implementing the bits I need".
Then I thought, "Wait. If I do that, I'll spend 90% of my time writing a language and 10% of my time writing a game".
So I was saved. Except I still haven't even started writing the game, so I suppose it's completely moot :-D
Re: Sadly, I must say goodbye to Leaf, my programming language
#13I wonder if Rust could become used as a standard library for other languages in the future. It seems well fitted for this role due to it's safety, relatively easy ffi, and speed next to languages with similarly large standard libraries.
Re: Sadly, I must say goodbye to Leaf, my programming language
#14Leaf is a good name for a language.
Without reading the parens, I first thought this was a story about how owning electric car wasn’t working out.
Re: Sadly, I must say goodbye to Leaf, my programming language
#15I had a similar thought process (but luckily without spending time implementing something). I want to write a game. I thought, "None of the current languages works quite the way I want. I know! I'll write a language specifically for my game and just keep implementing the bits I need". Then I thought, "Wait. If I do that, I'll spend 90% of my time writing a language and 10% of my time writing a game". So I was saved.…
I hit a similar roadblock for a long time, always spending time writing low level graphics utilities (which I do rather enjoy) but never getting around to writing a game.
If you find yourself in a similar situation and want to get around it I would suggest trying unity, which I was hesitant to do since:
1. It felt like giving up and cheating, and
2. I don't like how unity interfaces with the developer, since I mostly wanted to implement games without using the world editor that seems to be the focus of unity.
But I've enjoyed using it so far and would suggest giving it a shot.
Re: Sadly, I must say goodbye to Leaf, my programming language
#16What he is experiencing is the reality of most people's lives. The boredom and drudgery of doing the hard yards every day. Most people do not have the luxury of doing what is interesting to them. It is a case of just having to knuckle down and complete what has been started. From my personal perspective, it's nice to have side projects that are interesting and learning exercises. The reality is that if these side pro…
This post seems to be just a collection of generalities judging the way that someone else has chosen to spend his time. You seem both to be saying that he shouldn't have started and that, since he started, he shouldn't stop. Well, presumably the author once got some value out of the effort, so that it was worth starting; and found that he was now no longer getting enough value out of it, so that it was worth stopping. Do you really think that it's valid (or even important) for you to judge either of those decisions by someone else?
Re: Sadly, I must say goodbye to Leaf, my programming language
#17I wonder if Rust could become used as a standard library for other languages in the future. It seems well fitted for this role due to it's safety, relatively easy ffi, and speed next to languages with similarly large standard libraries.
I believe rust can compile down to a shared object and thus trivially used via any CFFI. Sure you lose the expressivness of the rust language APIs but that's a nightmare for interop anyways.
Re: Sadly, I must say goodbye to Leaf, my programming language
#18Feels like ripping out an internal organ, eh? This is advised against strongly.
Re: Sadly, I must say goodbye to Leaf, my programming language
#19I had a similar thought process (but luckily without spending time implementing something). I want to write a game. I thought, "None of the current languages works quite the way I want. I know! I'll write a language specifically for my game and just keep implementing the bits I need". Then I thought, "Wait. If I do that, I'll spend 90% of my time writing a language and 10% of my time writing a game". So I was saved.…
Language Syndrome sounds like Engine Syndrome in hard mode. You want to write a game, so you start working on a game engine, only to realise that a game engine is a never-ending project and you'll never have spare energy to actually write the game. I fell prey to this a couple of times back in the day.
Re: Sadly, I must say goodbye to Leaf, my programming language
#20I had a similar thought process (but luckily without spending time implementing something). I want to write a game. I thought, "None of the current languages works quite the way I want. I know! I'll write a language specifically for my game and just keep implementing the bits I need". Then I thought, "Wait. If I do that, I'll spend 90% of my time writing a language and 10% of my time writing a game". So I was saved.…
One of my motivations for writing a compiler was to get my game Empire to run faster.
Wound up with a career writing compilers, not games.