There is a difference between a challenge that is of use for this world, and a challenge just because.
I don't see technological, logical, or knowledge progress in the attempt to write complete OS in assembly (anymore). I've done it myself, in high school, just for fun, a 16bit. That is also when MenuetOS came out. Now I spend my time more wisely. I've actually went on doing things that benefit the society the technology and the users.
Not that menuetOS is bad, but I suggest they reorient them selves so that there is that usable part. And I can see space for it, in embedding computing f.i. Far from having no respect for their work, which I have my hands in from day one.
So, essentially your point is that because you have already done something others should be spending their time more productive ?
To some the challenge really is all there is. I'm very happy to see some counterculture to the bloatware that is the norm.
This is an amazingly compact and neat hack, it incorporates a very fast and lightweight GUI that can be used for general purpose computers just as easily as for embedded systems.
Hmm. I don't think I am making my self very clear. I think it is a great challenge, and I know what it takes to do so.
However, as Novash says - a reason: "that was faster", "couldn't find a good one in this language", "friendly enough", that seems to be missing. It was there long time ago when they started (for those of you who remember), but today everything shifted. I don't go building theories anymore on the statement that the world is flat?
So stop attacking me because I gave an opposing opinion and suggestion for improvement. It is great what they do, but I am sure like any other programmer, they too would like their code and idea used, not forgotten.
This was not about productivity or stupidity of projects, so reread my comments before you burst. I also do stuff all the time just to see if it can be done. Don't all of us? But again, "if it can be done" solves a problem. Redoing same things just because, now that's something worth discussing.
I coded a program to parse a text file into a OpenCalc Spreadsheet just because someone asked me if it could be done.
I coded a program to solve Sudoku because a friend made one and challenged me to make one that was faster (his was).
I am still coding a whole MUD Engine in C# simply because I couldn't find a good one in this language and nor a friendly enough one in any other language I know. It is moving slowly since I want it to be generic enough so others can use it.
I still, every now and then, solve problems on Valladolid.
I can see your point that they could spend their time more wisely, but I beg to differ. A lot of people love to code and coding becomes the purpose on itself. The knowledge they are gaining WILL prove to be invaluable to them and to others and the fact that they are doing something because they want, not because they must will drive them much farther than if it was a commercial project. It will give them both the reasons and the will to hone it to perfection. I suggest you to read "Jonathan Livingston Seagull", if you haven't.
It does not mean that every challenge that you take on must be of some use to other people. You're forgetting the fun aspect of doing such things. The same would be said to those who create their own graphics engines, compilers, and heck, even Lolcode. Sure, they don't become the next "big" thing in our industry, but the sense of accomplishment of pulling off a project of that magnitude is valuable enough in of itself.
