11 ms·
Sadly, I must say goodbye to Leaf, my programming language
- ghostbrainalpha 8y agoThat's too bad. I never actually tried Leaf but I loved following the journey.
- lifeisstillgood 8y agoThis is sad, and I feel for you. Your experiences I think mirror in the macro what many of us have in the micro - a side project becomes a love affair becomes something that has to be left aside as the rest of life takes over. I hope it is merely a hiatus - and I hope too find your next great passion. Keep writing about it - we will follow ...
- Thaxll 8y agoNever heard about that language.
- zengid 8y agoEven this doesn't help http://leaflang.org/faq.html http://leaflang.org/faq.html
- sdegutis 8y ago> "And would I want to work on yet another language, knowing I’ve already solved the interesting problems?" Sometimes this happens to me too, where I want to scratch an itch, and I try to do it by writing real software and using it. In general I have found that to be a bad idea. For those I prefer writing throw-away software, and only writing real software when it's "boring" but useful work.
- mortoray 8y agoWhen I started Leaf it was to scratch an itch. It was really only when the motivation dropped that I tried to find ways to use it, to renew my interest in pursuing it.
- caiocaiocaio 8y agoLeaf is a good name for a language.
- ModernMech 8y agoapparently someone else thinks so too: https://github.com/leaf-lang/leaf https://github.com/leaf-lang/leaf
- seanmcdirmid 8y agoWithout reading the parens, I first thought this was a story about how owning electric car wasn’t working out.
- deleted 8y ago[deleted]
- oldandtired 8y agoWhat 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 projects are actually worth it then they need to be completed. Otherwise they are just a fad and not really worth the effort that might be put into them. If something is worth starting then it is worth finishing.
- Waterluvian 8y agoI struggled with side projects that I never completed until I decided that I would never do a side project that can't be done in one or two afternoons. There are people out there that can chip away at a project over months or years and I think I just took a while to learn that I'm not one of them.
- oldandtired 8y agoMost of us have side projects that we can be troubled by. We also don't put them out for everyone to see, nor do we say publicly that we are giving up because the hard work is now upon us. I have lots of side projects that I may live to see finished. However, any that I say I am working on get assigned time to move them forward - they may take years to complete, but they will be worked on over time. From my perspective, he would have been better off saying that due to time constraints further work will be done when he is able to allocate time and leave it at that. There are plenty of projects that only get updated irregularly over years and can have years between updates. That's fine. However, if you stop a public project because you just don't want to handle the hard work now involved, that becomes something different. You are making a public statement about your character which you probably weren't intending.
- goatslacker 8y agoYes and no. Sometimes it's not about the destination but about experiencing the journey. From the post it seems like the author extracted the value they wanted to extract over the years. Knowing when to give up is difficult, especially when you've sunk a lot of cost into the project and feel like you have to finish it. The thing is, you don't have to and it's perfectly acceptable to put it on hold indefinitely. In the end you'll still have all those experiences with you and that's what you paid for with your time.
- mikekchar 8y agoI 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
- foota 8y agoI 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.
- pixelbash 8y agoRe the second point did you manage to get around this? Played with it a bit and it felt almost like flash back in the day where you could eschew the timeline and do everything programmatically. In the end ran into a problem where I wanted to move the universe around the player and couldn’t get the particle engine to cope..
- tlarkworthy 8y agoYou can do anything programmatically in unity. I think professionals tend towards this. You use the world editor only for artistic expression, the spatial layout and tuning etc. where previewing layout really saves time. For very specific effects like universe turning, you have to do a lot of code work in a niche area, but it's still quicker than building a particle engine from scratch. Sometimes you can cheat the effect in shaders or camera tranform manipulation. Or skip the effect altogether if the volume of custom code is not worth it and you are prioritizing shipping. Ask yourself, does it make or break your game?
- foota 8y agoI 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.
- kjeetgill 8y agoI 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.
- deleted 8y ago[deleted]
- roblabla 8y agoOnly because rust has an unstable ABI. I feel like it'd be nice to have rust provide an explicit "rust-stable" ABI for those kind of things.
- foota 8y agoI can't find much documentation on it, but it sounds like there's support for the Itanium c++ ABI
- kjeetgill 8y agoReally curious, is there much of a usecase for a stable rust ABI? There is no ecosystem of "rusty shared objects" to support and cargo tends to build things fine without it. As an outside observer it looks like an unnecessary complication.
- roblabla 8y agoPlugin systems and distributing dynamic libraries are the two big use-cases. For the second use-case, distributions can handle that somewhat okay by simply enforcing that all packages are compiled with the same rustc version. That works okay, but it means that, as an external user, you can't really depend on those libraries for your own executables, as you'll need to recompile when the distribution updates.
- VerbEncroacher 8y agoFeels like ripping out an internal organ, eh? This is advised against strongly.
- CocoaGeek 8y agoAnything that is too niche is bound to be a "barren run", at least for a while ...
- hyperpallium 8y agoI want to do D, and it'll be easier to do A, B, C first. A turned out harder than expected; B had challenges, some seemly insurmountable, some merely incredibly tedious. C looks even worse. I'm exhausted, lost interest in D. But I "should" continue. I give up... a failure. All because A, B, C make D "easy".
- abhgh 8y agoInterestingly, the author of D is on this comments page ... he did do D :-)
- abraae 8y agoAs the old saying goes, "When you're up to your ass in alligators, it's easy to forget you came to drain the swamp". (This is not a political comment! The saying long predates the current swamp drainers)
- Someone 8y ago”I give up... a failure” You could also call it a partial success. Your A and B may help others write their C and D. Also, hobbyists should have the motto “the journey is the reward”. If you had fun or learned doing A and B, it’s not a failure, even if all the learning was “if you want a D, it’s not worth it spending time writing a slightly better A and B”.
- mortoray 8y agoPerhaps that did not come across in the article well. When I set out to do Leaf that was the goal of the work. It's wasn't a diversion to some other goals. Over time my priorities changed, and I was trying to force myself to follow Leaf to follow them. Had I wanted to make a game from the start I would most certainly not have made a language first! That would be crazy. And that's my comments about sunk costs -- just because I have Leaf, it'd still be crazy to do this other projects in it.
- cjohansson 8y agoIt's a depressing feeling but the key point is that it's not motivating you any longer and motivation was the driving force of the project. When I face situations like that I usually raise the requirement bar up until it feels hard and fun again. So I suggest that instead of just doing what needs to be done with your project, invent a novel solution to the problem that is useful enough but most importantly - motivating you to do it
- z3t4 8y agoGiving up on something is probably harder then finishing it.
- ChrisFoster 8y agoSome people seem to be objecting to this as a fluff piece, but it speaks to me on a deep level. I develop free software because I like to learn and create; because good tools make work a joy; because I like to make useful things. And I've parted ways with several projects, some of them mine and some of them from others. It's painful each time I leave a useful project unmaintained. And yet, I don't find long term project maintenance sustainable as a hobby when my personal use declines. I suppose the best outcome is handing useful things off to a new caring maintainer. How do other people deal with this?
- brobdingnagians 8y agoI think handing it off to a maintainer when your own usage declines is a very good idea. One of the problems with maintaining something that you don't use a lot is that you get out of touch with how it is being used and the direction of the community. If you are at the head of the community, it is helpful to be an active participant; so appointing another maintainer who has an active usage, passion, and is "in-touch" with what is going on could be very fruitful. Eat your own dog-food
- chaoticmass 8y agoI worked for years on a game engine so I could develop a game I had an idea for. In doing this, I learned C, Lua, 3d graphics, threading in Linux, and a lot more. I never finished my game, only getting as far as some demos, but I'm still greatful for the learning experience.
- z92 8y agoFor my language, instead of targeting LLVM, I targeted C. That made me take off fast, because everything in C is available from day 1. What I did is build an extra layer over C to make it behave more like a scripting language. Used it for my website.
- mortoray 8y agoI chose LLVM from the start since I knew some of the challenges that interested me couldn't be done at the C level -- or rather it'd be more complicated at that level than at the LLVM level.
- rwallace 8y agoWhich challenges? As far as I can see, LLVM is essentially C in SSA syntax; what semantic differences have you come across?
- auggierose 8y agoThis is funny, I was just looking (like 2 minutes ago) at an article about GC vs. ref counting from the mortoray blog!
- auggierose 8y agoIt is possible though to build your own stack from the ground up (hard part is to be smart about what exactly "the ground" is). Look at Knuth and TeX. And today we have even better tools to write programs, and much better turn around times in terms of compiling etc. Obviously, there is some added complexity for there are API's like Apple Metal you will need to learn, but I think that more than evens out in total. I think it is important to have a big goal though (like TeX) to keep you motivated and moving forward.
- axilmar 8y agoC is a perfect language for writing games into; C++ has some extra sauce that makes some things easier, faster to write and more correct. There is no actual need for a new language for writing games; that's why so many, including the author, give up. C/C++ has the 90% of what is needed to write any application, and the rest 10% is simply elusive and might not even exist.
- Philipp__ 8y agoProblem with C/C++ is maintaining and writing code. I am sure you are well aware of Jonathan Blow's efforts in writing Jai programming language. If not take a look at his Youtube channel. Pretty eye opening. (I am no game dev btw)
- axilmar 8y agoI am a beyond-veteran C/C++ programmer, I already have studied Jai, viewed all of Blow's videos etc. I will not recommend Jai for any development, it doesn't offer anything substantially better than the current C/C++ combo to justify the switch.
- danbolt 8y agoI work as a programmer in the games industry, as well as make games by myself on my spare time. Like how the author describes, I really had to divorce myself from the thought of being a software designer or computer scientist to even start to make the sort of games I wanted to make. Even then I'm hardly a competent game developer, but I'm at least somewhat proud of my work so far.