Slashdot Mirror
Bordeaux 1.6 For FreeBSD and PC-BSD Released
Tom Wickline writes "Steven Edwards of the Bordeaux Technology Group released Bordeaux 1.6 for FreeBSD and PC-BSD today. Bordeaux 1.6 comes with added support for Google's Chrome Web Browser, Google Earth, and Google Picasa. In addition, Cellar support has improved; you can now delete and install into an existing Cellar. There have also been many small bug fixes and tweaks on the backend to improve the speed and reliability of all the supported applications."
BSD is dead.
WTF is this doing on the frontpage? This looks like some proprietary wine ripoff. Don't buy from these, buy from Codeweavers instead!
(I had guessed that this was posted by kdawson before i looked...)
You know, Microsoft's street address also says a lot about their mentality.
Some explanation in the summary of what Bordeaux is would be nice.
You could give some indication of what this program is for and why this is interesting.
Unless we are talking about an extremely popular app (Linux, Firefox), the first or second line of the summary should tell what the hell the app is!!
I am amazed that the slashdot editors still don't get this after so many years.
A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
I am surprised at how Tom succeeds in writing a blurb that is extremely difficult to understand (unless you already know what's being discussed, which I don't); primarily because, at this level of lack of understanding, I had expected a much higher three letter abbreviation-to-actual word ration. Bravo! ;-)
Oh, and happy new year, everyone.
"Good news, everyone!"
A random app released for PC-BSD? Woohoo!
I want to delete my account but Slashdot doesn't allow it.
It is now official. Netcraft confirms: *BSD is dying
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be the Amazing Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
Google Earth has been written in Qt with a native Linux version for quite some time now. Wouldn't it be easier to use the Linux version? I thought FreeBSD had extensive compatibility layers for running Linux executable built-in, and a Linux Qt application would look and feel more native.
# cat
Damn, my RAM is full of llamas.
" Unless we are talking about an extremely popular app (Linux, Firefox), the first or second line of the summary should tell what the hell the app is!"
Eh, I dunno. I don't know the names of most of the Linux oriented stuff, but as a BSD guy if it says "Bordeaux" and "BSD" in the same line, I know what it is.
If you make it easier for non-BSD people to understand this stuff maybe the same courtesy could be paid for this so call popular linux app thing as well. Fair is fair?
I don't even care if it's an ad. I actually want to read it (unlike the, say, Microsoft banner ads)
Need Mercedes parts ?
WTF is this app? The summary sounds like you can use it to map out locations and the inventory of wine cellars around the world. I suppose it would come in handy for the post-apocalyptic booze hound.
Since it relies on WINE, I guess those of us who run a pure 64-bit environment are still screwed. If I wanted to pay money and be tied to i386, I'd drop my money on Win4BSD -- assuming it works as well as it did on Linux (Win4Lin) when I tried it a few years back.
It's a bit of a bummer, as FreeBSD's PC emulation options are limited. AFAIK, Qemu is the only viable option right now, but it has known issues with crashing under FreeBSD/amd64 with certain (most) Windows versions. Hopefully VirtualBox will be made to run under FreeBSD in the near future.
Method of processing duck feet
Seems every time a company chooses to support FreeBSD, Linux fanboys come to /. to diss it. Linux fanboys are usually freeloaders, academics, or religious zealots of the Church of Stallman.
It's very good that there are companies developing for FreeBSD.
We need to have a software ecosystem from small software houses and I feel this will never happen with linux due to the GPL.
Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
The End of FreeBSD
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real
It is a kernel. Just FYI. This would have to be the first time any Slashdot* reader has needed Linux (or BSD) to be defined
* When I said I used Linux, I once got the response "So, do you really have sex on it?". This was not on Slashdot though
I don't mind the proprietary Wine vendors. However I am mystified by how they often claim Wine is difficult to install and configure. Any Free/Open Source OS likely already has excellent tools to help users download and install Wine (I know mine does). If that's the only problem these vendors solve then are they just making money off spreading FUD or is there some other force driving their (presumed) profits?