Post a Comment
The Haiku project chose the MIT license, because the GPL is too restrictive for them. NonCommercial-NoDerivs is probably not tollerable. If that Shinta guy does not loose the license for GenesTation (GPL at „worst", MIT at best), I don't think that this can be the „IDE for Haiku's Future".
No matter which license something has been placed under, someone will always complain, even if under no terms whatsoever being claimed by the original author.
Nothing to see/read here, move along
If they want to develop an IDE, encourage them!
More choice is better, as not everyone thinks/works the same way.
(Yes, I need to spend more time myself on that topic)
"...even if under no terms whatsoever being claimed by the original author. "
Contrary to what it seems, this would be pretty close to a worst-case scenario
http://en.wikipedia.org/wiki/Berne_Convention_for_the_Protection_of...
BTW, Creative Commons Attribution-NonCommercial-NoDerivs is definitely a non-opensource license (by the OSI definition)
The headline and the summary sounds like Genestation is a BeIDE-replacement written for the Haiku project.
The Haiku project is about replacing closed source Be code with open source code.
Genestation is nothing of that. Genestation is not targetted at Haiku, it's targetted at Zeta and Genestation is not open source. So with this premises: how can Genestation become the „IDE for Haiku's future"?
If Thom hadn't posted that misleading summary and just wrote something like „Genestation is an IDE for the illegal Zeta OS. Genestation is closed source and for non-commercial use only. A port of Genestation to Haiku is considered for the future." and no confusion about Genestation would arise.
Edited 2007-09-09 11:15
If Thom hadn't posted that misleading summary and just wrote something like �Genestation is an IDE for the illegal Zeta OS. Genestation is closed source and for non-commercial use only. A port of Genestation to Haiku is considered for the future." and no confusion about Genestation would arise.
1) I didn't write the summary.
2) Zeta is not illegal.
Haiku 1.0 is just planned, so what's your point? You seem to have a real axe to grind against GenesTation, mabe you should tell us why? OK it's closed source, but so is lots of code that people use to make OSS software. It may not be appropriate to be the main IDE for Haiku, because it can't be bundled, but that doesn't stop it being useful to people who want to use it.
If SHINTA wants to make it GPL, let him. Be happy that Haiku will have an actively-developed open source IDE. If he makes it GPL, it's not a big deal. It just won't make it into the source tree. An IDE is a good 3rd party opportunity, so Haiku has nothing but to gain from this.
Well, there is GPL'ed files in the Haiku sources, at least according to mphipps, and according to him any file under a non-commercial license can never become a part of Haiku.
So yes, this is a great third party tool for students, but open source it is not.
Again, there are so many open source IDE's so if this is important, it's reasonably easy to port one to Haiku. Personally I don't consider it important. It can wait 'till after Haiku goes Beta 
> Be happy that Haiku will have an actively-developed
> open source IDE.
GenesTation is not open source. However, it is free (as in beer).
This is a third party initiative and it's not intended to become part of the Haiku code base; so license compatibility is not an issue.
Regardless of the license, this can bring more options to Haiku in the future, so it is a positive development.
Damn! It's such a long name for a license ;-) Anyway, things are getting over-complicated. Back in the '80/'90, things were done the right way:
- Want to make money? Pricetag
- Want people to use it but want to make money too? Shareware
- Want people to use it? Freeware
- Want people to continue your work? Public domain
Sure, the GPL started something really interesting and I truly believe it's a good thing. But too many licenses appeared after that...
"IDE's are lame anyway, If you can't use vi - You shouldn't be programming."
I don't use VI. In fact, I've never used VI...yet somehow I've been a professional developer for going on 7 years now. Interesting don't ya think? ;-)
(For any folks born w/o a funny bone, yes I realize that BSDFan was being sarcastic)
1. This developer may be used for whatever the hell the community or just one person wants them to be used for.
2. This developer has no rights to choose the licensing terms of any software the community or just one person in paragraph #1 of this license.
3. This developer has no right to object to being told what to do as a developer, when to do it as a developer, and how to do it as a developer.
4. This developer has no right to a personal life while assigned to developing any work for the community or person mentioned in paragraph #1 of this license.
5. This developer never has the right to leave the development of the assigned works as assigned by the community or single person mentioned in paragraph #1 of this license: the developer may only terminate efforts on the assigned works as explicitly written by the community or person in paragraph #1 of this license.
6. This developer has absolutely no rights to stand up for what they believe to be right and express themselves in any manner that violates the views of the community or the person mentioned in paragraph #1 of this license.
7. If anything should be questioned as to what the developer can and cannot do under this license, the letter and spirit of the license is best represented by paragraph #1 of this license, and anything that would extend rights towards the developer under the "Open Developer's License" is interpreted with that being the guiding principle.
Well, that about does it for this "Open Developer's License" and makes it quite clear where whiners stand: clearly they're the masters, and the developers are the slaves, or at least that's what those that can't design and code themselves a solution (for whatever reasons, be it time or ability otherwise) would like to think.
LOL
I know the feeling. Those rules sux. However, nobody has put forth any kind of claim even remotely connected to your homorous post.
The fact that some pointed out that the license was Haiku-incompatible doesn't mean that they want to control the work of the developer. Nobody has claimed that. OTOH virtually nobody are particularly interested in this product because of the license.
You do have a point. Non-coders tend to be aggressive if they don't get what they want. However, we haven't seen any of that behaviour in this thread, or at OSN in general (with the exception of the occasional troll in KDE/Gnome/Vista threads).
Now, stand down and relax. Your reaction is out of line in this context 
I think the CDT Project will be siutable for Eclipse & C++ development on Haiku: http://wiki.eclipse.org/index.php/CDT










you said that now *how* many times? 