Slashdot Mirror


Wind River CEO Unexpectedly Resigns

The Finn writes "According to Electronics Weekly Wind River CEO Tom St. Dennis resigned today and left Wind River. For those who forgot, Wind River assumed stewardship of FreeBSD as part of the BSDi acquisition in May 2001, and subsequently Cut it loose in January 2002, and it still sells BSD /OS 5.0. I'll avoid the speculation of BSD dying, but Wind River may not be looking so good."

71 comments

  1. License contradiction by rapiere · · Score: 5, Insightful

    Quite sad to see Wind River in trouble ("The companyâ(TM)s revenue declined 20 percent last quarter" - Electronic News) as it decreases FreeBSD deployement among enterprises.

    I don't know much about other firms using BSD (like Wasabi Systems) however it seems it's more difficult for them to sell BSD systems compared with Linux distributors.

    Quite contradictoraly, BSD license is more "liberal" than Linux from the enterprise point of view which can use the code with minimal restrictions (FreeBSD License) Wind River and Wasabi Systems gives a generous access to their proprietary source to some bsd developpers)

    As Linux gains momentum, I hope IT managers will see those nice BSD lurking around, using them, and helping maintaining them (like hiring developpers to work on these systems).

    1. Re:License contradiction by rapiere · · Score: 3, Informative

      You should of course read "However Wind River and Wasabi Systems gives a generous access to their proprietary source to some bsd developpers".

      If some admin could modify my post, I grant him my benediction.

    2. Re:License contradiction by Anonymous Coward · · Score: 0

      Ever heard of yahoo? The Weather Channel?

  2. Well... by Anonymous Coward · · Score: 1, Interesting

    I was forcefull migrated off BSD/OS to FreeBSD a week ago. Perhaps things at Windriver aren't so great and the word is out?

    1. Re:Well... by rapiere · · Score: 1

      by who, why ?

    2. Re:Well... by Anonymous Coward · · Score: 0

      Hasn't BSD/OS been dying for a long time, in favor of the free ones? Wasn't there some effort, even, to merge parts of BSD/OS into FreeBSD?

    3. Re:Well... by tkrotchko · · Score: 1

      My experience with BSD/OS has been extraordinarily good.

      I set up a pair of mail servers based on BSD/OS back in '98 on a pair of PII-300's for a major corporation.

      Mail volume increased by at least an order of magnitude, and still the machines never crashed.

      They were only replaced a few months ago, when the volume of spam simply overwhelmed the perl scripts I wrote to filter mail.

      I hope BSDI finds a niche.

      --
      You were mistaken. Which is odd, since memory shouldn't be a problem for you
  3. Slashdot double standards! by larry+bagina · · Score: 5, Insightful

    So it's "news for nerds, stuff that matters" when the Wind River CEO resigns unexpectedly (I use FreeBSD and I don't have any idea who they are), but it's not "news for nerds, stuff that matters" when VA Linux CEO Larry Augustin resigned unexpectedly?

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

    1. Re:Slashdot double standards! by eht · · Score: 4, Insightful

      /. is owned by VA Linux.

      Make you own conspiracy theorist backed conclusions.

    2. Re:Slashdot double standards! by evilviper · · Score: 1

      Conspiracy theorist backed conclusions? Now you're talking!!!

      He resigned because CmdrTaco threatened him... Homer Simpson style...

      "Nice place you got here. Oh, look, a hairnet. It would be a shame if it was hurled to the ground."

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    3. Re:Slashdot double standards! by Anonymous Coward · · Score: 0

      If you have never heard of Wind River you must not have been using FreeBSD for very long ...

  4. WindRiver are not related to the FreeBSD project. by Anonymous Coward · · Score: 5, Informative

    WindRiver never, ever had any involvment with the FreeBSD project. What they bought was the FreeBSD merchanidise business that originally had been started by Walnut Creek and was subsequently owned by BSDi. WindRiver subsquently sold the FreeBSD merchanidise part of the aquisition to FreeBSD Mall who are still selling FreeBSD merchandise. What happens to WindRiver is of no relevance to FreeBSD in the slightest, and they had nothing to do with the project itself at any time, they just bought out one of the many FreeBSD merchandise comapanies that exist.

  5. He was pretty good... by baywulf · · Score: 4, Interesting

    When I worked at Applied Materials many years back, he ran the division I was working in. Although I never directly interacted with him, I found his management style well balanced and his speeches inspiring. Looking back, I would have no qualms about working under him again.

  6. Wind River dying? GOOD! by wowbagger · · Score: 4, Informative

    Sorry, but I have the misfortune of using Wind Rivers' VxWorks real time OS. I've have very little luck getting support from them (usually I have figured out the problem myself long before they can respond). Their hardware support is poor, their disk I/O layer is abysmal, their compilers out of date, and they are way too expensive for what you get. They don't have USB drivers (unless you want to be a printer, not a controller), they don't have SMB drivers, they killed their embedded X server (guess what I needed!), their board support packages don't (imaging a BSP for a Strongarm that does not even enable the cache!)

    If I had it all to do over again, I would have used an embedded Linux rather than VxWorks. Granted, I work on some pretty large and complex systems that are just too much for VxWorks.

    If you are doing a smaller system, use something like eCOS or RTXC. If you are doing a larger system or a system that must be networked, use QNX , BSD or Linux.

    1. Re:Wind River dying? GOOD! by Anonymous Coward · · Score: 2, Informative

      Why would you be doing some of the things you say you want to do with a real-time OS? An RTOS is not the same thing as an OS. The whole point is the real-time capabilities. If you can use Linux to solve your problems, you don't need an RTOS. Are you just trying to find an OS to run your big complex system or what?

      That said, you left out some OS suggestions: if you need a truly tiny-footprint RTOS, you can't get much smaller than Express Logic's ThreadX. And if you need a guaranteed-rock-solid high-reliability RTOS, look at Green Hills Software's INTEGRITY. Neither of those, however, have SMB support, embedded X servers, etc. But customers at Ford, Lockheed, etc. don't usually care about running an embedded X server on the chip running their vehicles...

    2. Re:Wind River dying? GOOD! by The+Vulture · · Score: 3, Interesting

      Good to know that I'm not the only person who had problems with WindRiver support from time to time.

      One thing to keep in mind though (and many of my colleagues share this view) is that the actual RTOS is very good, but the other things aren't. Unfortunately (for the company I worked for), WindRiver bundled things in such a way that it was seen to be more convenient to use their built-in IP stack (for example) than buying a third-party one. Some developers spent months trying to debug WindRiver's routing stack, versus buying a working solution, since it "just made sense to be a complete WindRiver shop". Let's just say that management's decisions have almost driven the company out of business (parts of it are being acquired, what's left is expected to be around for no more than two months).

      Yes, their BSP support is somewhat lacking, but, at least for us, they were one of the few companies that could get us a BSP that supported the Broadcom 3350 CPU (MIPS3K based).

      When I talked to a QNX tech at the Embedded Systems Conference, he explained their support for the Broadcom 1250 (the core we were using at the time), it made WindRiver's RTOS seem absolutely laughable.

      -- Joe

    3. Re:Wind River dying? GOOD! by cpeterso · · Score: 1


      I have always wondered why Wind River keeps supporting BSD/OS and dismissing Linux. Linux is hot. The embedded market is hot. Why doesn't Wind River provide a road map from old RTOSs to their new Embedded Linux? Instead they are letting little companies like Monta Vista stake Embedded Linux as their speciality. Wind River has more embedded customers and brand name recognition than Monta Vista. Because of the GPL, Wind River could even make use of most of Monta Vista's Linux contributions.

    4. Re:Wind River dying? GOOD! by wowbagger · · Score: 1

      To be accurate, WRS Never "supported" BSD - their OS is completely different.

      They bought Walnut Creek, a distributor of, among other things, BSD.

      As to why not support Linux - simple. The WRS mindset is "Screw them for the money, screw them for more money, then screw them for money again." Supplying a product that others can get in on would be a violation of that model.

      Keep this in mind: WRS aims to be the Microsoft of the embedded realm.

    5. Re:Wind River dying? GOOD! by Anonymous Coward · · Score: 0

      If they really wanted a good OS for embedded systems, I guess they would be more interested in the more portable NetBSD. But wait!...Wasabi systems "owns" NetBSD, right?

    6. Re:Wind River dying? GOOD! by DES · · Score: 3, Informative
      To be accurate, WRS Never "supported" BSD - their OS is completely different. They bought Walnut Creek, a distributor of, among other things, BSD.

      Actually, they bought BSDI, maker of BSD/OS, then sold off all the bits BSDI had acquired from Walnut Creek. And they did have a number of FreeBSD developers on their payroll for a while.

    7. Re:Wind River dying? GOOD! by chthon · · Score: 1

      Wind River has more embedded customers...

      I thought that this fact had more to with a series of acquisitions in the past than with providing a good product.

    8. Re:Wind River dying? GOOD! by gooser23 · · Score: 3, Interesting

      I was introduced to VxWorks when my previous employer asked me to port some drivers (ISA, PC-104 and PCI) for it. My overall impression was that it provided some nice libraries (multi-processes, semaphores, sockets, pipes, networking, as well as low-level IO) and was a piece of cake to get set up. It was Tornado, the IDE for VxWorks, that sucked. At best I was able to ignore it... at worst I actually had to use it.

      I really don't know what the dev team was thinking when the released it. Its a total visual studio 6 rip off, but most of the useful features don't work, and the others are buggy or illogical at best. The debugger could never remember what radix to display data in, anytime a file was saved with the editor you lost your undo buffer, and every now and then it woud do strange things to the build rules (the makefiles were generated every time you built a module) that would generally screw everything up and leave you with an error message like 'not found' or 'error'.

      So, I gave up using it and did my work in MSVC: it was far quicker to write custom build rules for VC than to fight with Tornado. When I left that job I spent an entire day writing a report on the bugs and strange things that Tornado would do.

      The one thing that Tornado did do right was its remote connection. I was able to boot VxWorks off of a floppy on a test machine, and control it via Tornado's debugging terminal on my dev computer. It took some getting used to (the frame pointer wasn't always in thre right spot, and nested function calls could confuse things), but it worked well enough to finish the project on time.

      --
      "Dying tickles!" -- Ralph Wiggum
    9. Re:Wind River dying? GOOD! by The+Vulture · · Score: 2, Informative

      This isn't surprising (the part about FreeBSD developers on the payroll).

      While the core OS itself was written from scratch, a lot of the periphery code (i.e. network stack, device drivers, etc.) come from one of the BSD's (I can't tell which one though, since I haven't bothered to read all of the code). And, judging by some of the dates in the changelog, they haven't been updated in a *long* time.

      -- Joe

  7. Doctor confirms, CEO Tom St. Dennis is dying. by Elwood+P+Dowd · · Score: 1

    Someone needs to post about how Tom St. Dennis only has 40,000 red blood cells, down from 100,000 last year. Someone? Help?

    --

    There are no trails. There are no trees out here.
    1. Re:Doctor confirms, CEO Tom St. Dennis is dying. by sulli · · Score: 1

      Is that like the river of blood that is like the red ink flowing from Wind River and the other *BSD developers?

      --

      sulli
      RTFJ.
  8. WindRiver by Anonymous Coward · · Score: 0

    WindRiver is the MS of the embedded world. They make there money selling there OS to people trying to make whatever boxes.
    They are arrogant, hard to deal, support is awful and they number enbedded system OS.
    I have dealt with them and don't them.
    Of course their tornado app does make it easier to develop on.

  9. VxWorks by jd · · Score: 5, Insightful
    Their RTOS - VxWorks - is, or rather was, very powerful. I've used VxWorks for fairly significant projects twice - once in '91 and once last year.


    The OS in 1991 was pretty decent. Things were up-to-date, and it was the best thing VME had going for it. (VME is a great standard. Pity about the companies implementing it.)


    Last year, though... That was another matter. VxWorks was unreliable and unstable. (I don't care what my boss at the time claimed - I was needing to reboot the VME crate repeatedly, and that's not acceptable. That's worse than my coding!)


    IMHO, VxWorks has had a good run. It's been around a long time, it has had some wonderful moments, but somewhere along the line it took a wrong turn. It's time Wind River accepted this.


    Wind River also does need to cash in a reality check or two, when it comes to pricing and support. We are NOT living in the boom times, we are NOT living in the early 1990's, when competition simply didn't exist and companies could charge what they liked and get away with it.


    Even Microsoft is beginning to feel the pinch, and that's impressive, given that it has enough spare cash to function at 100% capacity for the next three to four years without selling a single thing. That's just the loose change!


    *BSD isn't dying, it isn't even remotely close to it. Although the kernel does need some serious work, as technology is moving ahead faster than the coders.


    That's true for Linux, too. Progress in the field is outpacing the kernel coders by miles. That's not good, because it means certain hostile companies can out-flank these efforts, by simply skipping a generation or two of technology and going to the latest. We've seen that more than once.


    What's dying is the rate of development, as a function of the rate of technological change. That's not unusual when projects get very large. The larger a project, the more effort it takes to add even small components. Too much interaction to check for and debug.


    Wind River will likely vanish. By pricing itself out of the market, creating hostile public opinion, and by not building up the programming staff required to keep the momentum going, it will kill itself.


    FreeBSD'll move elsewhere, bruised but otherwise unharmed. It'll be set back a little, though, as it'll take time for the politics to work out.


    The underlying issues, though, are universal to all software writers:

    • If you aren't moving forwards, you're moving backwards.
    • If you are moving forwards, it'll take increasingly more effort to do so.
    • Moore's Law applies to silicon. Murphy's Law applies to software.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:VxWorks by Ded+Bob · · Score: 1

      FreeBSD'll move elsewhere, bruised but otherwise unharmed.

      Move from where? They have no association that I know of with Wind River. See link at top about it.

    2. Re:VxWorks by Anonymous Coward · · Score: 0

      FreeBSD'll move elsewhere, bruised but otherwise unharmed.

      FUD alert. This has nothing to do with FreeBSD. They're not going anywhere.

    3. Re:VxWorks by Anonymous Coward · · Score: 0
      It is official; Netcraft now 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 mere 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 a 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 can save it at this point in time. For all practical purposes, *BSD is dead.

      Fact: *BSD is dying

  10. Re:WindRiver are not related to the FreeBSD projec by Anonymous Coward · · Score: 1, Informative

    They still sell BSD/OS, a commercial version of FreeBSD, which they got from BSDi.

    It is probrably 1% of their business, so - as you said - troubles at Wind River, if any, do not reflect on FreeBSD.

  11. Re:WindRiver are not related to the FreeBSD projec by mph · · Score: 4, Informative
    BSD/OS, a commercial version of FreeBSD
    BSD/OS is not a version of FreeBSD. Both of them are BSD-derived operating systems. They have a common ancestor, but neither was derived from the other.

    The BSD Family Tree

  12. Kindly repost in fud.slashdot.com by Anonymous Coward · · Score: 0

    Well, now you can see what you get the other 25% of the time from Slashdot. 75% are just reposts of daemonnews.org or various bsd forums.

  13. does not look good... by BigBadDude · · Score: 2, Funny

    -Linux will soon be owned by either IBM or SCO...
    -Windows was never alive
    -BSD is dying...

    guess we have to go back to AmigaOS again

    1. Re:does not look good... by Anonymous Coward · · Score: 1, Insightful

      You're a hoot! Really though, speaking as a FreeBSD/*BSD zealot, GPL-hater, and a Linux-doubter, the AmigaDOS of old is dead, dead, dead--but that doesn't mean some old fans of the OS couldn't bring it back to life in a new, slightly different form in the same way Mr. Torvalds did with U**x. BSD/XFree86/Darwin teams all offer a lot of code that ought to be reused in other places as well as in *BSD/OSX/X11. I'm finding myself becoming more and more hostile to the notion of the "One true OS" or the "One true Desktop" or the "One true Windowing System" or the "One true web browser" or "One true scripting language". The only good alternative to all of that is the ability to share good code with as few hoops to jump through as possible so that fewer people have to reinvent the wheel in the open source world and good software gets cheaper.

  14. Re:WindRiver are not related to the FreeBSD projec by DES · · Score: 5, Informative
    WindRiver never, ever had any involvment with the FreeBSD project.

    BSDI had several full-time FreeBSD developers on their payroll when WindRiver acquired them.

  15. Re:Wind River and BSD problems by jonbelson · · Score: 2, Funny

    When you cut and paste an old Mac flame, try to remember to change details like the model (8600/300) if you really want to wind people up. :-D

    --Jon

  16. WindRiver != {Free,Net,Open}BSD by MythicalMan · · Score: 3, Informative

    Yet another "BSD is dying" FUD at /.

    Confusing WindRiver with the FreeBSD Project is a silly mistake.

    --
    --- Signature? You must be kidding!
  17. When you're hot, you're hot by Anonymous Coward · · Score: 0
    When you're not, you're not ...
  18. St. Dennis ousted by board by The+Finn · · Score: 3, Informative

    Now electronic news is reporting that St. Dennis was ousted by the board.

    --
    NetBSD: the cathedral vs the bizzare.
  19. I know the Editors enjoy a good troll.. by Anonymous Coward · · Score: 0

    Quote ..."I'll avoid the speculation of BSD dying, but Wind River may not be looking so good."

    I see. So *BSD is dying is now longer just a complete myth now but has moved to the status of speculation.

    Cool. Trolling seems to work ;)

    1. Re:I know the Editors enjoy a good troll.. by Anonymous Coward · · Score: 0
      It is official; Netcraft now 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 a 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 can save it at this point in time. For all practical purposes, *BSD is dead.

      Fact: *BSD is dying

  20. Elegy For *BSD by Anonymous Coward · · Score: 0

    Elegy for *BSD


    I am a *BSD user
    and I try hard to be brave
    That is a tall order
    *BSD's foot is in the grave.

    I tap at my toy keyboard
    and whistle a happy tune
    but keeping happy's so hard,
    *BSD died so soon.

    Each day I wake and softly sob
    Nightfall finds me crying
    Not only am I a zit faced slob
    but *BSD is dying.

  21. WindRiver == *BSD by Anonymous Coward · · Score: 0
    It is official; Netcraft now 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 a 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 can save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dying

  22. Does anybody know about "Zinc"? by motown · · Score: 1

    Not entirely off-topic, I admit, but Wind River has offered a desktop-version of their GUI toolkit called "Zinc" for free use (with certain ristrictions). So I'm curious: has anybody here had any experience with Zinc? Is it any good?

    http://www.windriver.com/products/zinc_for_deskt op /index.html

    --
    "Oooh, does that mean we get to kick some puffy white mad zionist butt?"
    1. Re:Does anybody know about "Zinc"? by motown · · Score: 1

      Oops, I meant "not entirely on-topic", of course. ;) And "restrictions" with an 'e', while I'm at it. :P

      --
      "Oooh, does that mean we get to kick some puffy white mad zionist butt?"
  23. "Zinc"? the former cross-platform window api? by teambpsi · · Score: 1

    Is that where that behemoth ended up? At windriver?

    I used Zinc in the early 90's to do some very light-weight cross platform toys, but that was about it -- it was a jack of all trades, master of none when it came down to it -- like most of the class of tools under the umbrella of CASE

    In fact today, using AWT in Java reminds me of that experience

    --

    Old age and treachery almost always overcome youth and skill.
  24. *BSD is GROWING by Anonymous Coward · · Score: 0

    It is official; Netcraft now confirms: *BSD is growing

    One more crippling bombshell hit the already beleaguered Windows community when IDC confirmed that *BSD market share has risen yet again, now up to more than 30 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has gained more market share , this news serves to reinforce what we've known all along. *BSD is sending other OSes into complete disarray, as fittingly exemplified by topping the charts in the recent Sys Admin comprehensive networking test.

    You don't need to be a Daemon to predict *BSD's future. The hand writing is on the wall: *BSD faces a long and prosperous future. In fact there won't be any future at all for Windows Server because *BSD is growing. Things are looking very good for *BSD. As many of us are already aware, *BSD continues to gain market share. Red ink flows from Redmond like a river of blood.

    FreeBSD is the most loved of them all, having gained 93% more core developers. The sudden and pleasant release of the long developed 5.0 only serves to underscore the point more clearly. There can no longer be any doubt: FreeBSD is growing.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 70000 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 70000/5 = 14000 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 7000 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (70000+14000+7000)*4 = 364000 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the release of OSX, cool new technologies and so on, FreeBSD is expanding into more desktops than ever. FreeBSD has become more than the sum of its parts.

    All major surveys show that *BSD has steadily gained in market share. *BSD is very powerful and its long term survival prospects are very bright. If Windows is to survive at all it will be among OS dilettante dabblers. *BSD continues to improve. The progress achieved is nothing short of a miracle. For all practical purposes, *BSD is alive and kicking.

    Fact: *BSD will kick your ass

    Just pissing off the trolls. Move along.

  25. The Finn is a troll by Anonymous Coward · · Score: 0

    The Finn,

    You couldn't resist the "BSD is dying" troll inside yourself, could you?

    Kindly never post on a msg board again.

    BSD is stronger than every, please get this through your damn head.

    OpenBSD
    FreeBSD
    NetBSD
    Mac OS X - more UNIX desktops than Linux will ever be on.

    All actively being developed, strong community, where most new technology is developed, Linux community just bolts it onto their distros.

    So what if some company that sells FreeBSD CD's CEO quit, it means nothing to any of the develoment of BSD.

    You have no say.

  26. Up Wind River without a paddle by gnalre · · Score: 1

    We use vxworks here and from our perspective it has a number of problems.

    Firstly they have been trying to push a subscription scheme from there old licensing model. For existing projects this works out as very expensive(10,000 per seat per year).

    Support can be poor and updates unreliable. We recently had some poor drivers which took ages to debug and a poor network stack. Until recently source code was a very expensive optional extra, so leaving you very stuck waiting for vxworks to get there act together. And remember we are paying for all this in our support contract.

    Also on the horizon is embedded linux. The pricing structure is such that if go with vxWorks for low end products any profit margin is taking by license costs, therefore RT linux has been killing them in this area.

    On the plus side, if you have a non standard board or processor getting a working OS on it is a breeze with vxWorks.

    But I think embedded linux is starting to make there high costs look increasingly out of phase with the real world. I can see a lot of changes occurring in the next 6 months.

    --
    Choose your allies carefully, it is highly unlikely you will be held accountable for the actions of your enemies
  27. Wind River confirms: *BSD is dying by Anonymous Coward · · Score: 0
    It is official; Netcraft now 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 a 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 could only 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

  28. Re:Larry Augustin, open sores shyster, dead at 39 by Faggot · · Score: 1

    i'm so happy to see that someone's archived this!

    --

    But what do I know. I'm just looking for anonymous gay sex.

  29. Hard times for *BSD by Anonymous Coward · · Score: 0
    So why? Why did *BSD fail? Once you get past the fact that *BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. *BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know *BSD keeps losing market share but why? Is it the problematic personalities of many of the key players? Or is it larger than their troubled personalities?

    The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.