If he had said he was stopping due to life commitments or family situations, etc, then these kinds of things take priority, as they should. No problems or issues should arise from that. But he has stated that he is giving up because it now involves doing the hard yards to complete the project - this does not show him in a good light.
In essence, he is saying that once something has become non-interesting in whatever way, then he will give up and move onto something else that will hold his interest. In other words, he is committed to a course of action only when it holds his focus, but that he will happily drop it when it becomes hard work.
I really don't think that he was intentionally going out to say that he is undependable. This is what he has said though.
When I look at it from his point of view, I feel quite sorry for him. The language's forum has 9 posts in the last calendar year. 4 of those are him solving a problem using Leaf. Then, I check out the status page and realize that, for all the work he has done, Leaf is still in a very primitive state.
I'd equate it to being like a startup. At some point, it stops making sense. Then, you can either ride the ship down into the depths, or hop out when the going is as good as it will get.
As for his dependability, I've got to tell you that, from my perspective, anyone who can pull this off is more than impressive enough.
I think he should be awfully impressed with what he did. And, I don't think it's even remotely fair to judge him as being undependable. Based on what I've seen, I think he should have pulled the plug last year, when he first wanted to quit.
I don't feel sorry for him at all. He found something that was of interest to him and he decided to head down a path towards that interest. Good on him. Kudos to him for giving it a go. However, the problem he has made for himself is that he went public far too soon and is now publicly saying he is quitting because there is too much hard work ahead for him.
Startups have a low rate of success and is about testing an idea that has a good likelihood of failure. Different proposition to start with. The more appropriate comparison is making some item that can be useful to you but has a lot of tedious and fiddly work to be done. In his case it was a computer language which always comes with implementation problems to do deal with. One knows this up front, or at least, should know this.
The problem is, he hasn't pulled it off - there is still a long way to go. One of my areas of interest is language design, compiler construction of virtual machine implementation. This subject matter is highly complex, tedious in many ways and requires a great deal of patience and perseverance. For each problem you solve, more arise to be solved.
For an individual, this can be daunting when you finally realise that you have undertaken a massive project. It is especially so, if the language that you have designed doesn't strike a cord in other people. But if you have a goal in mind, then continue on even through the tedium that will come.
Things will always get in the way of you completing side projects, that's life, but you can still keep chipping away as the years go on.
This fellow doesn't get paid for his work on Leaf and he works on it during his already spare time. He would gain more doing creative tasks - he wants to "do graphics, write music, make some games and record some videos."
It has nothing to do with hard work and everything to do with allocating his time in the way he most wants to. He is taking control of his own happiness and that is admirable.
I also don't grasp the logic behind the notion that once a creator shows his work -- or work-in-progress -- to the public that he is somehow bound by duty, honor, respect for his 'followers', or some other compelling consideration, to finish that work.
If Beethoven starts writing a string quartet, and posts the first movement on the internet, but then realizes that the Duke isn't going to commission it and he'd rather be writing a sonata anyway, does it really reflect badly on LvB if he abandons the quartet?
You can show off your work in any way that you want. You are also not bound by duty or anything else to finish that work. However, if you are putting it out there for other to see and or use, at least say that this may or may not be useful in some way. To cover yourself, you could say that it will be a work in progress and that the progress will move in fits and starts as you have time to devote to it. At that point, there will never be a need to say that you are giving up on it.
Bad comparison with Beethoven. But to answer your question, if he had said that this is the first movement and may have a potential to be completed if the Duke commissions it, then it doesn't reflect badly on him when the Duke doesn't commission it.
It is a matter of what expectation you are creating in those who are viewing your work. If you are saying that it is there as an example of something, then so it is. But if you go out and say "here is the bee's knees", and then you decide that it is no longer worth your while because the amount of work is now too much, then you have created the problem for yourself.
There is a project called Axiom, which has inspired me to look at my own code and projects in a different light. But to follow in the footsteps presented by Axiom in my own projects involves a lot of tedious hard work. The benefit that I see is that anyone who comes after me and is interested in what I have done will be able to follow. That "anyone" may only ever be me, so be it.
I'm not sure where you got this whole idea from, but it's not true, neither in the real sense nor in the perceived sense. People benefit from working on projects they do not finish, and plenty of people are impressed with unfinished projects. This person is going to be a much better developer than average from this experience. There is literally no issue here. It's his work and it's his time and what he does with it is none of anyone else's business.
The only issue here is you making an issue out of it according to some strange ethical norms that nobody else shares. This is a massive overthinking/overjudge and the thinking here is rather unhealthy.
Yet I suspect that the intent of what he may have wanted to say is that final sentence above. But that's not what he said.
I'll say it again, there is no problem with unfinished work, if what you were trying to achieve has been completed.
But please, don't then say that you won't complete the work your doing because to do so would require hard work and it's just boring and tedious. This is what reflects negatively on you.
If you have achieved your goal then just say that and show what has been learned from the exercise. If you would like it to be continued but can't do so for whatever reason, which you do not have to state, then offer it to anyone else who might be able to take it on. You never know, you might get some takers. This reflects positively on you.
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.
...to you. You find most parts of your projects boring and tedious.
Many people don't. I definitely don't find any of my work boring, and only very small parts tedious.
In the end you'll still have all those experiences with you and that's what you paid for with your time.
However, when one starts a project and says "look at me and the fabulous stuff I am doing" then it does not show them in a good light when they give up because they are now in the drudge work.
In a public situation, they are essentially saying that they are not worth their hire when the normal drudge work starts. I can understand stepping back from a project for all sorts of reasons, except for the reason that it is hard work to continue because drudgery.
Most of the work that most of us have to do is not exciting, not learning new things, not even interesting. It is just drudgery that needs to be done to get to the eventual goal that we started with. This is life.
The thing is that even drudgery work can be viewed in a very positive light if we continue to see it as essential for the final goal we started with. We will see the need for it and we work willingly towards the completion of it for the purpose of what we will achieve in the end.
The journey is a part of the destination and it is an essential part of the whole process. A journey without a destination and a destination without a journey are both meaningless without the other. Both are the two sides of each other.
> The problem here is that the project was made public for others to use/view.
This literally doesn't matter if we're talking about someone's character, because whether it's public or not is irrelevant regarding the " they give up because they are now in the drudge work" point. Either that point is valid or it's not, but the public knowing about it is beside the point.
And I would say the point is not valid. Someone starting a personal project for a language and then discontinuing it is still much better off than someone not starting a project at all. I don't think most engineers share the perspective that this shows them in a bad light or something, this is honestly the first time I've seen this perspective in years.
> Most of the work that most of us have to do is not exciting, not learning new things, not even interesting. It is just drudgery that needs to be done to get to the eventual goal that we started with. This is life.
There's nothing good about this, nor anything good about reinforcing it. Godspeed to those who can avoid it.
The author of the language does not owe it to anyone to start, continue, or finishing any projects they have in mind, definitely not to anyone sitting around and judging them for daring to do something at all.
It is a matter of what expectation they are creating and what they say they are trying to achieve.
I don't have any problems with someone creating a language to see what they can achieve with it. If they find it not doing what they need, they can move on. However, they can ambush themselves by the creation of a project that they claim is bigger than what they may actually have in mind.
I have lots of partial language designs to test out specific ideas. Many are incomplete because they have shown that the specific idea I was testing is basically flawed. The information is available to those I discuss this with for them to investigate in their own way. They can see the lessons I have learned, especially about the failures I have come across. But they know well that the work done is both incomplete and was created to test out one idea or another and may or may not be of any use to anyone else.
My discussion point is that the author could have handled himself better without reflecting on his character. Essentially, to say it is now too hard to keep going because it is tedious, boring or just too much effort required doesn't reflect well on him. He could have handled that a lot better and still put everything into a close down mode.
> > Most of the work that most of us have to do is not exciting, not learning new things, not even interesting. It is just drudgery that needs to be done to get to the eventual goal that we started with. This is life.
> There's nothing good about this, nor anything good about reinforcing it. Godspeed to those who can avoid it.
My question to you - do you have a plethora of servants to do all your drudgery work? Who cleans your toilet, washes your clothes, cooks your food, sweeps your floors, mows your lawns, changes your children's nappies, and so on and so forth? Who writes your correspondence, enters your passwords, writes your code, drives your car in traffic?
Far too often, people are taught today to skip the tedious, the uninteresting and the hard boring work and someone else has to come along and clean up after them.
I am not judging that he dared to do something, I am highlighting that the way he has stopped his project reflects badly on him. Whether he starts a project or stops that same project is up to him. It is the reasons he states for that start or stop that reflect positively or negatively on him.
Perhaps that's true, but I think it's often quite difficult to know whether a project will be worth finishing before you start working on it.
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.