I'm not sure what Sun could realistically have done to come out the other side of the dot-com carnage. Other companies in roughly equivalent situations come to mind. You start looking at doing a hard reboot when the margins for that reboot aren't there and it's difficult to see the light at the end of the tunnel. Maybe an earlier reinvention involving more open source and alignment with where hardware was headed. Don't know.
Sun did waste a lot of money in buying MySQL, $800 million in cash and $200 million in stock. Certainly a distraction, as well.
Sun never offered any way to inexpensively get onto the on-ramp of Sun hardware and software as they thought they could continue selling high-margin hardware forever; they had their $995 V100 which even included their much-loved LOM which was a remote-management device like iLO/DRAC/IPMI , then followed it up with: nothing.
info about the V100: https://dogemicrosystems.ca/pub/Sun/System_Handbook/Sun_sysh...
I surely would have liked to get one of those laptops, though.
- MySQL AB — $1.0B
- SeeBeyond Technology — $387M
Some more companies undisclosed and of course in 2000 Cobalt Networks for $2.0B.
But in general, just hanging around on SPARC far to long. Unfortunately the person put in charger of SPARC told Scott that he thought SPARC could be saved but it would need 4-5 years. And that's when they went into mulit-core, selling everybody on the whole 'threw-put computing' nonsense.
Was that before or after you realised the Linux kernel devs were better at squeezing performance efficiencies out of x86 than you guys were?
That's the sort of behaviour I'd sack the guy for if he worked for me.
The first thing is a regrettable quip of mine on Usenet (RIP) from October 29, 1996 -- just over 29 years ago (!!) as of this writing. As I have made clear several (many?) times over the years, I do very much regret it: I was young and it was stupid.[0]
But that's also not what this is REALLY about, because that decades-old quip on Usenet had itself been forgotten for over a decade when it was dug up in 2013 by people who newly discovered that they hated my guts. And they discovered they hated my guts because they vehemently disagreed with my handling of the the Noordhuis pronoun incident.[1] And on this, I have no regrets -- and will have no regrets.
Hopefully that clears up where the (seemingly limitless) venom is coming from -- with my apologies for dragging confused bystanders into decades-old internet beef!
[0] https://news.ycombinator.com/item?id=9041086
[1] https://bcantrill.dtrace.org/2013/11/30/the-power-of-a-prono...
I would not work for you because you exhibit all the qualities of a bully. You've been exhibiting this behaviour for decades now. Every time I see you say that you needed to "teach the hardware guys a lesson", or you write a blog post that you would sack a non-employee, or you resort to invective when you could calmly address the issue without going full nuclear, then it confirms my opinion of you.
I'm not following you around HN, incidentally. You just happen to comment on posts that I'm also interested in. I know, however, that if I ever did work for you or worked in the same organisation as you, I'd likely become your target.
Solaris 10/11, with all its technologies (zfs, zones, crossbow, dtrace, etc), was the pinnacle of UNIX that came out just when the world changed. At a company I worked at circa 2008-12 (that was a solaris shop) we essentially created a proto-docker with containers and ZFS that allowed rapid deployments and (re)building of our systems. It was a game changer for on-prem.
I do ask myself after reading the HN comment you linked, how often is the limiting factor of systems software the hardware? Potentially a case of this with consumer hardware is ACPI issues, like [1] and [2]. You could design the best software, but if your underlying firmware or hardware is faulty, then you would have to design your software around the faults instead of improving the lower layers or accept bugs.
Oxide describes on their website issues with "vendors pointing fingers with no real accountability, even when teams need it most," and I have seen this point discussed online in regards to Oxide's work on designing their own hardware and firmware. Incidentally, I applied to Oxide recently; I think they're cool for the reasons I thought Sun was cool.
[1] https://triangulatedexistence.mataroa.blog/blog/i-uncovered-...
[0] https://news.ycombinator.com/item?id=2287033
[1] https://bcantrill.dtrace.org/2019/12/02/the-soul-of-a-new-co...