GCC 3.3.1 Switch Coming Soon On NetBSD
Dan writes "Matthew Green says he is ready to switch sparc, sparc64, i386 & alpha ports to using GCC3.3.1 by default on NetBSD. He's uploaded 4 snapshots (one per port ;-), all cross compiled from i386-netbsd. However, there appears to be work involved with fixing approximately 193 broken packages, as reported by NetBSD's Jan Schaumann."
1. You can not play games on it.
2. It cannot be used by my grandma.
3. It lacks a GUI of any note.
4. There is no support available for it.
5. It is an assortment of fragmented OSes.
6. It cannot be run on the x86 platform.
7. You have to compile everything and know C.
8. Support for the latest hardware is always poor.
9. It is incompatiable with GNU/Linux.
10.It is dying.
All major marketing 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 hobbyist dilettante dabblers. If truth, for all practical purposes *BSD is already dead. It is a dead man walking.
BSD you grow in the ghetto, living second rate
And your eyes will sing a song of deep hate.
The places you play and where you stay
Looks like one great big alley way.
You'll admire all the numberbook takers,
Thugs, BSD pimps and pushers, and the big money makers.
By Chinese Karma Whore, Version 1.0
Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.
Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.
These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.
As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.
Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.
The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.
_d8b____________________d8b_______d8,
_?88____________________88P______`8P
__88b__________________d88
__888888b__.d888b,_d888888________88b_.d888b,
__88P_`?8b_?8b,___d8P'_?88________88P_?8b,
_d88,__d88___`?8b_88b__,88b______d88____`?8b
d88'`?88P'`?888P'_`?88P'`88b____d88'_`?888P'
______d8b________________________d8b
______88P________________________88P
_____d88________________________d88
_d888888___d8888b_d888b8b___d888888
d8P'_?88__d8b_,dPd8P'_?88__d8P'_?88
88b__,88b_88b____88b__,88b_88b__,88b
`?88P'`88b`?888P'`?88P'`88b`?88P'`88b
Shut up. Or supply something original or funny.
*BSD Suxors
In a startling turn of events today, a previously little-known fact
came into the public eye: "*BSD Sux0rs".
This came as a complete surprise to the BUWLA, or BSD Users With
Large Assholes, as they previously thought that *BSD 0wned.
"You see, even though I have never contributed code to any BSD
project, I thought it was my duty to be a big asshole to others
which don't use the OS I do, because it just 0wnz.", said one
FreeBSD user. "Now that I know it sux0rs, though, I have to go
find something else to be an asshole about."
One notorious OpenBSD fanatic known as WideOpen, told reporters,
"I have to kill myself. This isn't how it was supposed to happen.
My BSD has always been the best, and shouting that opinion in other
people's faces at every chance I got has been my only hobby. It
was all I ever did. It was what got me out of bed in the morning.
Now I have to die. I will jam my bedpost up my ass until I hit my
brain. It is the only way to go: BSD style."
In the volatile world of operating systems anything can happen.
"At least we don't sux0r as much as Windows users", BigAzz, a
relatively well-known NetBSD user said. "Screaming things in people's
faces is my calling. Now I need to scream that BSD sux0rs. What
a sad world. At least I won't kill myself like those uber-asshole
OpenBSD guys. They are just way over the top. Or were, at least."
Nobody knows for sure what the future holds for the state of operating
systems, but with Netcraft confirming the sux0r status, *BSD users
all over the world will have to stick something else up their asses
from now on or risk looking even more gay than they used to.
I hope never to see
a tree as dead as BSD