Silly girl, there's a reason why Berlin will never succeed.
It's the same reason why other Open Source projects like the HURD, GGI, and Freedows are going nowhere fast: Too much design, not enough code.
Too often, non-programmers (or worse random C newbies) will propose some absurdly difficult endevour ("Just imagine: an Open Source version of Microsoft Office 2000! On my PalmPilot!"). Usually, this will be followed by the registration of a.org domain name, a SourceForge page, and a "0.01" announcement on Freshmeat. Occasionally, one of these ideas will be taken too seriously. Web pages will be written and re-written. Mailing lists will be created. White papers will be written. Developer hierarchies will emerge. Often, one sub-groups ego will be bruised, and they will splinter off to form some equally vaporous project.
But what never happens is code being written. APIs might be formalized, but that is worthless without working code. The most succesful projects (such as GNU, the Linux kernel, the BSDs, KDE, and GNOME) were founded on the "shut up and code" model. The authors spent time hacking rather than writing press releases or yet another web site revision, or the checking the latest PDF copy of the Offical Project X Standard for Widget Frobbing into a CVS mirror. And who gives us results?
Berlin is a pipe dream. A nice dream, perhaps, but so are many others.
Slashdot Mirror
Silly girl, there's a reason why Berlin will never succeed.
.org domain name, a SourceForge page, and a "0.01" announcement on Freshmeat. Occasionally, one of these ideas will be taken too seriously. Web pages will be written and re-written. Mailing lists will be created. White papers will be written. Developer hierarchies will emerge. Often, one sub-groups ego will be bruised, and they will splinter off to form some equally vaporous project.
It's the same reason why other Open Source projects like the HURD, GGI, and Freedows are going nowhere fast: Too much design, not enough code.
Too often, non-programmers (or worse random C newbies) will propose some absurdly difficult endevour ("Just imagine: an Open Source version of Microsoft Office 2000! On my PalmPilot!"). Usually, this will be followed by the registration of a
But what never happens is code being written. APIs might be formalized, but that is worthless without working code. The most succesful projects (such as GNU, the Linux kernel, the BSDs, KDE, and GNOME) were founded on the "shut up and code" model. The authors spent time hacking rather than writing press releases or yet another web site revision, or the checking the latest PDF copy of the Offical Project X Standard for Widget Frobbing into a CVS mirror. And who gives us results?
Berlin is a pipe dream. A nice dream, perhaps, but so are many others.
i have one hell of a user number...