The goal of releasing "the best performing, highly stable SERVER based OS, with outstanding documentation" depends upon having competent developers and contributors.The goal should never be to simply attract users. Otherwise it ends up becoming like every other project; a clone of Ubuntu. What the goal should always be, however, is to release the best performing, highly stable SERVER based OS, with outstanding documentation. That alone will in turn attract the right people.
There are two sides of the coin. Yes, more users in general will hopefully bring with them some decent developers capable of i.e improving the OS.I don't see that attracting users will lead to FreeBSD becoming an Ubuntu clone, except perhaps in good ways, such as keeping pace on hardware support.
… grow the FreeBSD userbase? …
… install …
An installer that's more capable and more user-friendly would broaden the base.
… SERVER … the right people.
dumb questions from newbies,
What? No. I have no clue of C, and I'm perfectly comfortable with what I do. So are lots of users.at least some C programming knowledge is the minimum bar for being comfortable with it
You never had to fix compilation errors? Use tracing tools? Read the source code to check whether a particular piece of code is present in a certain branch? Diagnose a program crash? I don't mean you need to be a professional programmer, what I mean is that you need just enough code literacy to do the basic tracing/debugging/read-the-docs stuff. You'll have to eventually learn this even if you don't intend to, there is no other way.What? No. I have no clue of C, and I'm perfectly comfortable with what I do. So are lots of users.
… I've said it multiple times and I even have it in my signature. FreeBSD is a professional operating system for professionals. … Being popular among the highly proficient is good, and it also brings in enthusiasts who add value and contribute, but it also drags in the amateurs who only want to play their games. …
Well, that kind of assumes there is documentation other than syscall/libc man pages and source code comments (and McKusick's book). More often than not, there isn't any. Virtual memory, discussed in a recent thread, is a good example of something that not really approachable without some programming knowledge (high level picture should be easy enough to explain, but details definitely aren't). Yet you need to be aware of it to correctly interpret SIZE/RES columns in theTotally disagree on the C programming sentiment. To be a regular user of the major Unix OSes (FreeBSD and Linux, at least), you really don't need any programming skills, just a little bit of common sense for reading the manuals.
... at least some C programming knowledge is the minimum bar for being comfortable with it.
To be a regular user of the major Unix OSes (FreeBSD and Linux, at least), you really don't need any programming skills, just a little bit of common sense for reading the manuals.
"FreeBSD is a professional operating system for professionals and computer enthusiasts" as someone once said.