What Sun got wrong | Hacker News Reader

What Sun got wrong

bcantrill.dtrace.org

692 pointschmaynard436 comments

As someone who was buying hardware in the late 1990s, it is hard to overstate the difference in buying experience between Sun or Digital (DEC) and someone like Dell. The former forced you into a live sales meeting, endless quote revisions, it was a nightmare. I remember calculating the server rails and power cords for a new Alpha server were going to cost more than a shipped/delivered Dell server that I could get the next day.

For us dell has become that. Rep changes all the time, what appears to be random pricing and long unclear delivery dates. Instead I can for example go to Thomas Kren and configure my serves online for a fraction of the cost. They have what they list in stock, delivered a few weeks later. Everything is clear and hasle free.

At this point I have the feeling dell just charges you what they think they can get out of you. You push back and the price drops, I don't want to negotiate.

That’s exactly what enterprise sales is. Call for pricing, tell the absolute upper limit you can spend, and pay.

A nicer way to frame it is: “value based pricing”.

hire a salesperson to give them fake sales numbers and low ball them so you pay less?

Is there a guide to negotiating enterprise software purchases somewhere that doesn't suck? I feel like I am always overpaying.

Figure out what you need, get the final quote, and go silent.

Eventually they’ll come back and have some impressive sounding exec reply saying they need 20% less to get it in the budget.

because you always end up paying... from time to time do the exercise of not purchasing but finding out their lower limit

I think this is a case of AI ruining the hardware market. We used to almost exclusively use Dell, but now we've been forced to look elsewhere and go through validating new vendors. The lead-times are ridiculous, and these guys now only pay attention to the really big guys. Not sure I can blame them though, you've gotta do what's best for your business.

Dell was very much moving this way before modern AI explosion. The inconsistency on pricing alone depending on what rep was helping you also became a problem. I could often times call in direct and order via business line cheaper than dealing with my account rep. No reason to jump through so many hoops.

I prefer the "This is the price" model and just make it consistent. I can't wait until AI helps us remove multiple layers of middle men across Sales in general.

Just let me buy it and move on.

> I can't wait until AI helps us remove multiple layers of middle men across Sales in general.

Based on how things are moving, I think it's more likely that AI will _replace_ the layers of middle men (with layers of "middle AI"), then that those layers will be _removed_.

Of course, the process (of squeezing the customer) is the point. The implementation of that process, with either human account reps or sales bots, is irrelevant.

Not to the account reps who's pay put food on their table, vs the bots who don't have children to feed.

> I can't wait until AI helps us remove multiple layers of middle men across Sales in general.

Monkey's paw - now you have to deal with a layer of bots.

And bots don't buy lunch.

that's great as an attitude, the problem with it is that money is made up and so are prices. Business have an inventory and expenses, and hopefully they can sell enough product before their debtors come calling. There's no right price for something. Underpriced, Overpriced, the only qualifier is: is the company still in business? Sony could give Playstation 6's away for free, so long as people bought games for it, but culturally, that would look desperate, so that will have to charge money for it, when they announce it. The only thing something is worth, is what someone else is willing to pay for it.

I think you're misunderstanding.

We need more Tesla style this is the price for all.. less dealership style with prices varying by some ones mood. As a buyer with a relationship, I should not be able to just buy through the website cheaper than your quote (for the exact item line by line). That's the scenario I had multiple times. Hell with the GB10's came out I bought a couple and the price through our Rep was 6k a piece no extras. We paid the list price $4k and were even able to use a discount coupon due to holidays that our rep wouldn't take. That's the BS Dell has been doing.

Periodic component shortages have been a fact of life in the server business forever. Like a key supplier's factory burns down or something.

The key thing is being transparent with customers on price, availability, and delivery schedules. In the short term server vendors can use tricks and personal relationships to extract higher profit margins but eventually the senior executives at major customers figure out what's happening and start looking for other options.

> The lead-times are ridiculous, and these guys now only pay attention to the really big guys. Not sure I can blame them though, you've gotta do what's best for your business.

I don't blame them in the sense that I wish for them to be imprisoned or anything. But I wouldn't do business with them, either. I want business partners whom I can count on, not ones who will stop returning my calls as soon as a more lucrative opportunity arises.

> At this point I have the feeling dell just charges you what they think they can get out of you. You push back and the price drops, I don't want to negotiate.

This is precisely the role of the sales person for something like a service, but for a physical product it is pretty egregious. There is no greater sin than leaving money on the table. There's an old story about someone offering a quote that was apparently pretty low based on reaction, so they quickly add "that was for my assistant" to give way for pushing the number higher.

> so they quickly add "that was for my assistant" to give way for pushing the number higher

I don’t understand what this means? I understand that they bumped the price. But I du not understand what is meant by it being for the assistant? Care to explain?

Not OP but the way I read it...

Electrician: "Okay, so my services start at $100/hr"

Electrician: "... for when my assistant can handle things."

Replace Electrician by whatever skilled professional you prefer.

Pretty much, except the assistant is never going to handle things and the updated fees go up to include you and the assistant. If you only ever send out your assistant, you never make money

I think you miss the point.

You price it at what you think works. There is no push back, so you make room to push the price higher.

You were happy to do it at the original price.

I didn't miss the point, I'm the one that posted the comment. I know precisely how it's used.

If you play poker, it is the equivalent of pushing 'portions' of your bet out at a time. You push the portion, observe their face and body language, and maybe push the rest.

The 'that was for my assistant' is just something they say to explain away the earlier quoted price. They are pretending that what they said wasn't the quote for this conversation, it was for another, different conversation, between the salesman and their assistant. This only works when the assistant is not in the call.

That behavior is not tolerated at any real poker table. It shouldn't be tolerated in salespeople either.

This is called string betting and will get you kicked off a table.

I like this version: The optician quotes the price of new glasses by saying "$100", waits to see if the customer flinches, "... for the lenses", waits again, "... each.".

I wonder how effective it really is, over the long term, to generate short-term profit by consuming trust like this.

I mean this is the point of having salespeople, to maximize the amount of money you get from each customer.

This is why when I go to the price page for a product and seeing "contact our sales team for a quote" I look for an alternative.

Dell does a soft version of this by setting uncompetitive prices on the website and making you call to get the real price, although ironically that usually just means we go with a different company that simply posts a competitive price.

The iron law is that vendors want to become like the old Sun. The only reason they don't is if they are trying to compete their way up the hill. Take away the old Sun and SGI and IBM and now Dell is Sun.

Difference is Sun was providing a "full stack" proprietary product including CPUs running a proprietary ISA, Unix OS, compiler, desktop environment and productivity apps. All that Dell does is assembling standard, commoditized parts and putting a free OS on it. Dell's business is incredibly easy to replicate, while Sun's business is extremely hard to replicate. Of course, Sun's competitive advantage turned into a curse when the components of that vertical integration become uncompetitive both features and price wise vs. the GNU/Linux-on-Intel stack. But regardless, Dell could never replicate the vertical integration Sun had.

Really? When I first met Sun machines they were selling 68k-based Sun machines that were better specced than Apple and Amiga and such but left them dependent on Motorola’s architecture that had indirect address and thus no future.

Sure they had an in house chip development ARM team right at the time when RISC economics looked good but CPU architecture had to work harder and harder to beat the memory wall and SPARC was not competitive by 2005 and “Hail Mary” projects like CoolThreads were difficult and expensive but did not deliver for customers.

Hypothetically customers could benefit from that proprietary stuff but they benefit even more from rapid progress is competitive, commodity markets.

When I was working at the library circa 2005 we were thinking about replacing all the Windows computers that patrons used to access the online catalog (and other services) with a web browser with Sun Rays, we probably would have bought a few hundred of them and we would have bought some SPARC servers to back them up.

We could have gotten Netscape to run under Solaris but after a week of effort I wasn't able to get Mozilla to build, so no modern web browser. So no Sun Rays. No servers. DTrace and ZFS were great innovations but without the magic of "can run the software you need to run" they are just Blub. Had Sun done the work to get Mozilla running on their machines and forgotten about DTrace and ZFS people might still be using Solaris... but instead DTrace and ZFS found an audience by supporting... the commodity OS!

(arguably at that time supporting a web browser was the #1, #2 and all the way through #99 task that the Solaris team should have been working on at that time and everything else from Java to Tcl to ZFS was a dangerous distraction... and that's how companies in a position like Sun die)

"When I was working at the library circa 2005 we were thinking about replacing all the Windows computers that patrons used to access the online catalog (and other services)"

why were you thinking of going Sun, as late as 2005? just easier to lock down, like kiosks?

We already had a big investment with Sun for back end systems like the library catalog. We perceived managing a big fleet of desktops as a hassle, it was worse then it is now.

> circa 2005

> I wasn't able to get Mozilla to build

You must be misremembering something. Netscape/Mozilla/Firefox had always tier one support on Solaris. You had nothing to build, just download and run, with perfect compatibility.

I only ever ran Netscape/Mozilla/Firefox browser (and still today in 2026). My desktops and servers were all Solaris from mid-90s to 2012 or so. Never a hiccup running the Netscape family browsers (and servers too).

There was Netscape support, but then there was that crisis when it seemed that IE would be the only viable web browser, the realization that the Netscape was too FUBAR to build on, and then Mozilla got rebranded as Firefox.

They probably had an official Solaris build of Mozilla later on but if one had been available at that point in time I would have installed it on the SPARC machine I had under my desk. The ship had sailed in terms of the organization's capital planning.

If you were happy running Netscape later than I was you might have felt supported.

This sounds right. There was a "dark ages" in the early 2000's, where Unix/Linux browser support was terrible. You were either stuck with old Netscape 4.x, which crashed every half hour, or you had to work with half baked, almost unusable beta builds of Mozilla (pre-Firefox). Because of this, I actually ran Windows on my desktop for a while!

There was never a time when Netscape Navigator, Mozilla or Firefox were not fully supported on Solaris (earlier, also SunOS).

When Netscape Navigator first came out eary/mid-90s I ran it on SunOS while working at a Sun shop, it always worked perfectly.

By the time the Netscape browser was open sourced in 1998 I was working at Sun and running it on Solaris, always worked perfectly. I attended the open sourcing party Netscape held in San Francisco, still have the autographed CD with the very first open source release source code. Netscape paid for buses from Silicon Valley to SF for people to attend the party. Fun times!!

In 1999 the Sun|Netscape alliance happened, AOL took the consumer software part including the browser and Sun continued the server product development under iPlanet brand. For a while I worked in the Netscape campus that year, and I continued working on iPlanet servers for years after that. Since the browser code had been open sourced, development continued outside AOL becoming Mozilla and later Firefox. Always first class on Solaris.

Firefox branding happened much later (wikipedia says 2004). Still working perfectly on Solaris. Only browser I ever ran, always on Solaris, until the bitter end (oracle lawnmower in 2010).

So yes I can confidently say it always ran perfectly on Solaris (SunOS in early years), having been there through all this and have fond memories of it all.

Dell puts a fair amount of engineering into their servers (as do other main brands like HPE and Lenovo) so it's unfortunate they've lost their roots from the old mail order sales company.

If someone else is paying I'd prefer one of these big OEMs for established firmware lifecycle, spare parts and long gray market availability, shock (shipping) and thermodynamics engineering. If I'm paying, Asus or MiTAC (Tyan) are good enough.

I was fortunate enough to work with a fair bit of sun gear (3/260, 4/670, enterprise 250/450 and even some big iron 6500s) back in the day.

These days, I've got several Dell 5820 style workstations and I'm pretty sure someone who interned at sun in the 1990s is now running dell's workstation division. The medium sized dell deskside towers have nearly identical vibes as those old workstations, and are a pleasure to work with.

> a "full stack" proprietary product including CPUs running a proprietary ISA, Unix OS, compiler, desktop environment and productivity apps.

this is apple today.

True but Apple is a consumer company that makes consumer products. Sun lost all interest in that already by the early 1990s. They were happy to just be standard unix and didn't do anything to be a real consumer company. They talked a lot about competing with Microsoft but didn't actually.

They talked about buying Apple, and they could have, but the CEO basically admitted they had no clue what so ever on what to do with Apple.

They had no vision or concept of what being a consumer company would even be like. Even in the 80s they were focused on engineers and costumers like that, never end costumers.

> Dell's business is incredibly easy to replicate

Your sentence is a tacit admission that you don't have a very deep understanding of logistics and integration and what it has taken for Dell to build the deep supply chain they have. Yes, it's a commodity system; that's the point; but it's still leagues better than a Supermicro, right? Think about the difference there and why people still shell out for a Dell instead of a Supermicro or Exxact or plain whitebox hardware. There's a lot to a solid Dell server that you might not realize, from disk controllers to iDRAC....

>but it's still leagues better than a Supermicro, right?

We didn't think so.

I mean, if you have no knowledgable people, maybe, but for about 10 years we've found it a better use of time & treasure to buy generic servers and consumer laptops, and just have spares. We found Dell's support so costly and so ineffective that just buying extras turned out to be a better move.

I think it's a matter of scale and focus.

Dell is at a sweet spot for many organizations where you can get hardware support from dell, or not.

You can (with dell) just buy used junk and use that, and you can still access their support library for firmware updates.

I did a lot of work with storage with dell stuff and I found it far simpler to "outsource" the storage integration to dell than to do it myself -- they make sure that all "2tb disks" are the same (exact!) size, they all use the same mechanism for firmware updates, etc.

A much larger org could have saved some money doing that integration and testing internally; a much smaller organization could save money just buying stuff from wherever and not worrying.

I personally haven't used dell support in over a decade, but I have found that their "look up the serial number" web site has been invaluable; I've found the fact that they publish firmware for all their stuff and let anyone install it valuable; the huge secondary market for dell is helpful, etc. And, if you care, you can even give them more money to directly support you, instead of just doing it yourself.

HPE, on the other hand, locks their stuff down super hard; I assume there are reasons to go with HPE, but I'd rather get clocked on my superdome with an HPUXy stick than ever touch that stuff again.

>I personally haven't used dell support in over a decade,

We used to buy the top-tier support plans for our laptops and servers, and we found they just consistently could NOT meet their obligations. Laptops stayed broken and nonfunctional for weeks and weeks.

They're awful.

> Difference is Sun was providing a "full stack" proprietary product including CPUs running a proprietary ISA, Unix OS, compiler, desktop environment and productivity apps.

SPARC was not proprietary, buy fully licensable:

* https://sparc.org

Fujitsu sold their own SPARC servers for many years with their own CPUs, and many third-parties put Fujitsu SPARC CPUs into (e.g.) laptops:

* https://jasoneckert.github.io/myblog/sparcbook3000st-the-coo...

Can you get an x86_64 CPU from someone other than Intel or AMD? x86 is much more proprietary than SPARC ever was.

Sun used the non-proprietary Open Firmware (IEEE 1275) for booting (also used by Apple with PowerPC), and SBus (IEEE 1496) for cards before moving to PCI. SCSI and Ethernet/IP were there since forever as well.

The "proprietary" label on Sun, at least when it came to hardware, was always a mystery to me.

It's the platform that's proprietary.

Sun used a lot of open parts, but they had absolute control over the platform. Everything in your solution came from Sun or a Sun partner. Fujitsu doing weird stuff with Japanese mainframes was an interesting fact but irrelevant to 99% of Sun's user base.

Intel/AMD combined with EFI or IBM-compatible BIOS? You can get that from anybody. An HP server is basically interchangeable with a Dell.

Sun was proprietary in the same way Apple is.

> SPARC has been licensed to several manufacturers, including Atmel, Bipolar Integrated Technology, Cypress Semiconductor, Fujitsu, Matsushita and Texas Instruments.

* https://en.wikipedia.org/wiki/SPARC

Fujitsu was selling Solaris-compatible systems (as were many others). Linux and BSDs also ran on them.

There were a number of x86 makers up until the 1990s or so, but who is left of them? Can you still license x86(_x64) to fab your own CPUs? You can with SPARC:

* https://www.gaisler.com/products/gr765

"Many others" is stretching the truth a bit. There were maybe 4 or 5 Sparc clone vendors, ever. The one I remember offhand is Solbourne: https://en.wikipedia.org/wiki/Solbourne_Computer

Sadly, they left the Sparc clone business before they could even support Solaris! They stopped at SunOS 4.1.

It wasn't just the chip, it was the whole ecosystem.

Could an every day consumer buy a Sparc motherboard, chip, and build their own system? No. There may have been one or two vendors that did that late in the 90's, but they didn't stick around.

> Could an every day consumer buy a Sparc motherboard, chip, and build their own system? No.

Yes:

* https://www.gaisler.com/products/gr-sbc-gr740

You kind of proved my point: that's an embedded platform. No consumer is going to be running it. The last link indicates "VxWorks, PikeOS, and RTEMS operating systems available."

It appears there is a Linux kernel port: https://www.gaisler.com/products/linux-for-leon

I'll give you the benefit of the doubt that you can load a Linux distro on there. You have a couple other problems: there's no ethernet or wifi, and you only have 512 megs of RAM.

> You kind of proved my point: that's an embedded platform. No consumer is going to be running it. The last link indicates "VxWorks, PikeOS, and RTEMS operating systems available."

"Consumers" can be running it just as much as "consumers" could be running Raspberry Pis, which could also be considered 'embedded' by some. SPARC is no less (or more) proprietary than ARM: you can license the ISA, fab a CPU, and sell some kind of hardware stack.

Do you think it would be more or less difficult to get a license from Intel/AMD for x86(_X64) than ARM and/or SPARC so you could fab your own chips?

So you don't think the complete lack of connectivity (video, networking, and storage) is going to be a problem for a normal person? There is absolutely no comparison with a Raspberry Pi. It has all those things and great software support. That Sparc platform is for a satellite!

But yes, you are correct, it's much easier to get a SPARC license.

> So you don't think the complete lack of connectivity (video, networking, and storage) is going to be a problem for a normal person?

Not someone looking for rad hardened boards with flight qualified bootloaders...

If you're looking for rad hardened boards, you're not a "consumer" in the general sense of the word.

Yes you could do this, from Sun Microelectronics back in the 1990's. We purchased an Ultra-10 motherboard with 250 MHz Ultrasparc II in 1998/1999, fitted it out with compatible third party SVGA, Ethernet and SCSI adapters and ran Solaris on it. Was our production LDAP, Mail and database server for a small ISP for many years.

I later worked for a systems builder that built and sold Sparc/Ultrasparc systems for government (eg. Hong Kong Mass Transit). We were the only vendor in the Southern Hemisphere doing it. So it wasn't common. But yes you could order parts from Sun Microelectronics and build your own systems, and it became easier use certain standard PC compatible parts once they standardised on PCI. We had shelves full of the older incompatible MBus compatible systems and boards as well.

Sun made a Sparc ATX motherboard that you could put in any PC case.

That is what made Sun, Digital, and SGI loss hurt even more. Dell is nothing in comparison, just a bargain box maker with no ambitions beyond. Losing those other companies hurt because when you control the hardware and the operating system software, you potentially can build anything.

Look no further than Apple computer. I must admit, back in the day I wanted a Next computer or an SGI computer because of the graphics and sound capability, but the only thing I could afford at the time was an Amiga computer later on, I had to settle for a work related Microsoft computer using AutoCAD, Revit, Navis and a few other graphics programs.

They should reexamine that wish.

https://companiesmarketcap.com/sun-microsystems/stock-price-...

Is that what Dell is like?

I went to their server site and clicked “shop now.”

I picked a PowerEdge R360. It has the price right here at $5k and a big green “Add to Cart” button along with an incredibly long list of customization options just like I was buying a laptop or desktop. It doesn’t seem like I have to contact anyone to get an order in.

It says I can get it as soon as October 2.

It can be that easy if you want a small number of servers and are willing to pay the outrageous sticker price. In reality, nobody pays $5k for that R360. You either play their game and deal with their insane sales team to get a big discount or you buy from a partner instead of Dell directly. We did the latter and it was just as easy as ordering from Dell online but also way cheaper.

dell is not sun because they have way too much competition

Dell’s innovation to the computer industry was build to order, selling computers direct, and later online in short streamlining the buying process. IBM, Sun, Digital, and SGI we’re at a whole different level, and they were at that level because of their capabilities.

They could’ve have potentially changed the game (like Apple) and competed against Microsoft and Intel, but they were fixated on selling basically to the corporate level which was in hindsight not a good decision long-term, and eventually it cost them all, their loss was immeasurable because of the hardware and more importantly operating system capabilities they had in house.

> At this point I have the feeling dell just charges you what they think they can get out of you

This is how license compliance shakedowns work. Make sure your DRM is more flexible than theicensing terms, find an overage and see what you can get the customer to agree to.

I have seen senior Oracle sales reps deliberately misreading their license doc to inflate what is owed.

> I have seen senior Oracle sales reps deliberately misreading their license doc to inflate what is owed.

"I guess I can't pay so much because such a huge fraction of the contract volume goes to my lawyer."

DELL was an innovator in this "incomparable pricing" model for normal consumers.

You'd price out a machine and then go look at comparable machines (difficult) from other vendors, then the next day your machine wouldn't be "the" configuration anymore. Instead there'd be half the ram and double the harddrive space for an extra $50, and if you swapped back to what it had been yesterday it'd cost you an extra $200.

IIRC they won business awards for this.

Where's Cartman when you need a vigorous "SHENANNIGANS!!!!"?

Did they learn this from the airlines ?

We sold web traffic analysis software to Dell Europe, around 1998 or so. They never kept their data more than a week. As the traffic and purchase behaviour they were analysing in the store changed so much every week they said (if I remember correctly) it didn’t make any sense to compare the data over time. I took from that that what they sold every week changed all the time. Of course, data storage and processing was then not as cheap as it is today, so maybe there was more to it.

try adding wifi, you don't get DVD. Remove DVD, you don't get wifi. It's ridiculous. Dell is a joke of a company

... this also made me swear off DELL and discourage everyone I knew from buying from them, too.

> For us dell has become that. Rep changes all the time, what appears to be random pricing and long unclear delivery dates.

I think this would be expected from a company that has acquired and absorbed EMC and Perot.

And that is the "thing". Every failed mini company had the same exact issue, seems customers had to beg and/or go through hell to purchase equipment. Never mind that the hardware was more expensive than what you cold buy from companies like Dell.

IBM is not much better than what I hear, but somehow they keep surviving. Probably because of their mainframe business.

And Redhat[0], and professional services a la Accenture[1].

[0] https://en.wikipedia.org/wiki/IBM#2010s%E2%80%93present

[1] https://en.wikipedia.org/wiki/Accenture

Their old services arm was Kyndryl which they spun out as its own thing

> IBM is not much better than what I hear, but somehow they keep surviving. Probably because of their mainframe business.

Imagine every bank you know going through tech modernization and maybe 70% of those are now using Red Hat OpenShift.

They own Red Hat (OpenShift kubernetes, Red Hat Enterprise Linux, Ansible Automation Platform) AND HashiCorp (Terraform, Nomad, Consul, Packer, Vault, etc.) now, on top of their previous mainframe, services gigs, global financing arm, and calling everything they sell "watson".

I seem to remember IBM had a way to buy their stuff online, but not anymore apparently. I'm sure this was back in the System x days.

Sun commercial sales reps, at least in Europe, were astoundingly slimy.

I had a colleague where almost his whole job consisted of beating them in sheer sliminess, and at this he was good. I don't think we ever paid 30% of the prices they'd start at, but the process of achieving this was disgusting, and there was still the sense everyone was being screwed.

So when we could move to Dell we did.

I'm sure I have a memory of someone at Sun UK telling me about how they managed to run up a £30K bar bill at an event....

Yeah that fits. I was in London (though not the City) and it was definitely that sort of scene.

Thinking about it, we moved to Dell as part of the run up to IPO, and I suspect had we not done so Sun would have been much harder to deal with afterwards.

What I recall from that time is Sun were very happy they'd sold a huge pile of servers to be the core of Interlink, and a whole load of people went off to work on that.

Yeah, and it wasn't just the "call for pricing" game, it was having to deal with monthly "touching base" calls which were mostly an opportunity to push corporate hospitality and other not-quite-inducements.

Whereas Dell just gave us a flat 30% discount on list pricing, and were clear in advance about what level of annual spend would trigger an increase to 35%. We'd order online and our sales rep would phone a few hours later to confirm. Other than that, they'd initiate contact maybe once a year when Dell refreshed their server or storage product lines and would offer to either send some bumpf or arrange for some demo kit.

Dealing with them was so much less hassle all round, you never got covered in slime, and you never felt like they were on the verge of offering you bribes.

* [...] some bumpf [...]*

Uh, as in "excessive paperwork", like brochures/leaflets [1] about the new products? Not a native speaker, had a parse error I'm just trying to resolve ...

[1]: https://www.reddit.com/r/EnglishLearning/comments/1hlbxv7/co...

Yep, a mix of glossy brochures and things like white papers from Intel about their latest Xeon 3 architecture or whatever. They tended to lie about on someone's desk for 6 months before being chucked out...

(and I'd had no idea about the "bum fodder" derivation, so thanks!)

Awesome, thanks!

Yeah, and then Dell more-or-less turned into that. Companies get big, customers and sales get more complicated, process gets more calcified.

SUNW would probably still be around if the whole x86 commodity pizza box revolution hadn't happened OR if they had pivoted away from SPARC earlier and went heavily into x86. Example: buying from IBM doesn't sound too different from buying from Sun, but they're still around because mainframes will be around until the Earth implodes (probably).

(I think that their channel/partner programs along with their professional services org are big reasons why Dell is still a key player in the datacenter space. You can buy Dell direct, and the sales process is still "good" as far as enterprise sales goes, but bigger players usually get their Dell kit through distributors/vendors with Dell professional services handling architecture, build-out, enablement, etc. I'm not sure how much energy SUNW invested in this, as they were before my time, but this combo is a major revenue driver for them.)

Also thanks to virtualization being originally invented in mainframes, and the OS design done by IBM (and Unisys as well), they get to run the old workloads on modern hardware, and also support various UNIX flavours.

You can even run most cool Python, Go, Java, Rust, PHP among others, on systems like z/OS.

We have a couple mainframes at work, had an incident last year when someone forgot to apply a new license to one. p1, no payments happening.

I was kinda stunned; there’s a level of balls involved in selling an x millions machine and having it fail closed that I’m sort of impressed by but also utterly appalled they’d treat their big customers like that..

I mean surely to fuck it could have been an automated reminder email to the mothership and not just: sorry folks no banking for you today.

IIRC (never got to physically play with that part) it's configurable - when you install licensing. And you can get quite expedited support/unlocks/etc.

I had a similar experience earlier this year. Cheaper situation than a mainframe, but... why do some companies make it hard for them to take my money? I'm already a customer ffs.

Glad to see you mentioning channel sales.

The rise of the Internet made channel sales handoffs a weak point in the business model. I bet this missed sale went to a reseller who didn't respond and Sun didn't have any controls or visibility on that failure.

Dealing with VARs was always the worst part of dealing with Sun (and certain other companies). Though a great many old-school CTOs I worked under loved the schmoozing, it meant engineering decisions were always fed through the management meat grinder and the risks of "added value" changes to orders were always there.

Yeah it was so much more accessible to play around with configs and pricing and then all you needed was a credit card.

Even now I think enterprise companies should be more open about what's possible and what the price and delivery date would be without having to talk/chat/email anybody. Even for something like a Juniper $100k+ device it would be kind of cool to configure it.

I’ve had that experience with dell consistently over the last 6+ years. While with other vendors I can do everything over email from start to finish, Dell insists on meetings, follow-ups on topics that I said I am not interested in talking about, services that I do not need, meetings with teams I am not interested in meeting, reps that straight up skip meetings, so I have to console a junior rep that got stuck in a meeting that is above their pay grade. Different reps same slimy bs.

I needed to add a bunch of capacity running Sun/Solaris back in the late-90s. Same thing: pointless meetings with sales reps without clarity in pricing. Finally, I found the gear we were looking for on eBay, bought it, drove over and picked it up in my Ford Explorer, and had it up-and-running in one day. To my surprise, people in my company were PO'ed. But I had air cover because the CEO found out and loved it.

> Sun or Digital (DEC) and someone like Dell.

In a time frame like 1999 to 2002, much more broadly than that, just the increasing gap in cost vs what you would get between buying any hardware+OS package from a legacy Unix-like vendor (Sun, DEC, SGI) and doing your own thing on a FreeBSD, OpenBSD or Linux on x86 hardware.

Dell was obviously a top choice, but by 2000 or so, Linux or FreeBSD had become good enough that you could do exactly the same thing for a fraction of the cost and run it on x86 hardware you had purchased from either Dell or one of the top 5 or 6 Dell-competitors.

As compared to, as you say, sitting through sales meetings, price quotes, revisions, a long slow and arduous process to arrive at a figure where you come to a conclusion "yeah you can spend $60,000 on these Sun servers or we can buy $20,000 of x86 servers and get creative with our own software stack to do the same thing in house".

At a certain point 1U and 2U server hardware got fast enough on boring standard x86 single or dual socket motherboards from Taiwan, in the era of like the 1.2 GHz Pentium 3 with 512KB cache, that the performance was pretty damn good and the machine cost a fraction of what the equivalent Sun or SGI rackmount machine would cost. This is in the era before a multi core x86 CPU existed. And you could be sure that its BIOS and motherboard were already OK for use with a current Linux kernel, we're talking about motherboards from Supermicro, Tyan, intel whitebox reference server boards, etc.

It's easier to see in hindsight but servers have eaten a lot of macro economic headwinds.

1999 and 2002 correspond roughly to telecom and dotcom bubbles popping. So open source operating systems were also pulled up into these positions through a lot of work and by the early 2000s it was kind of obvious this was the way forward.

2008 financial crisis really knocked the high end (RISC/UNIX/Itanium) and started the long migration to renting vs owning. In hindsight it's remarkable how much money used to just be there in the economy of all this. But I guess it still is, considering how expensive public cloud is.

> But I guess it still is, considering how expensive public cloud is.

It's not like there's less servers being sold, they're just bespoke designs from companies like the big Taiwanese ODMs that go straight into hyperscaler facilities, and we don't get to see public marketing websites and product info about them. The open compute platform stuff that's been publicly shown is like the tip of an iceberg.

> The open compute platform stuff that's been publicly shown is like the tip of an iceberg.

I find it a real shame it's not easier to get OCP hardware for our homelabs. Would be so much easier to operate, upgrade, and so on. And where would you even get decommissioned OCP gear?

Some of the ethernet switching top of rack 1U stuff used to show up on ebay. I think large other portions of it go into an industrial shredder/recycling process.

> other portions of it go into an industrial shredder/recycling process.

This is just criminal. Reusing is much better than recycling.

Practically speaking, most of it would sit waiting for a buyer.

I'd pay more than the recycler.

OCP was designed by vendors, including ones that didn't want to get sunsetted. It was never going to be practical for homeless until EOL hardware started to filter down.

EOL hardware is usually fine for home labs.

I'm referencing the premium you pay to get some paltry VM in a public cloud with bizarre storage and networking that primarily make sense for the market maker versus the actual cost of the hardware. There are ways to make cloud economics work as a user, but only where staffing costs would dwarf spend (i.e. small businesses) and I've never seen them in practice.

People would sneer that you were using shoddy free software, but then the guys who bought the expensive vendor solution would discover that the paid software was also of poor quality and unlike the free version you didn't get the source so your only option for getting something fixed was to file a bug report and pray, despite spending 6 figures on a support contract.

On the other hand, Sun and DEC hardware from then still works today, if you care to power it on. How many dell devices do?

If you click through to the anecdote[0] mentioned in the article, the problem was not with having to contact a sales rep. In fact the startup wanted a sales rep. Sun specifically asked them to use the website:

> More than once though, the Sun people did suggest I just buy the servers off the web site.

Dell was just the only one to callback.

I don't doubt your experience but that was at the height of Sun's business, not it's nadir as this article is about.

[0] - https://fullhoffman.com/2006/03/20/the-sun-doesnt-shine-on-m...

One of the first "expert systems" was one that helped you spec your DEC computer. It was easy to order a VAX that was missing necessary hardware (or had incompatible hardware).

https://en.wikipedia.org/wiki/Xcon

Forcing customers to talk to sales is actually a failure mode.

ordered small item from Dell 7/31, still not received.

Love to hear stories and real-world experience like this shared! I feel us tech folks should start Facebook groups similar to those "Old Photos from <city I grew up in>", except photos and stories from tech :)

Would love to read about these stories if you ever decide to blog and/or write a book about it. :)

Same with the commercial LISP vendors back in the days. sbcl changed that.

The ultimate value of Sun, Digital, or even SGI was the fact that they were both hardware and operating system software companies. When they went down, it was a big blow to the American computer tech industry.

I've written several times here about all the mistakes that Sun made during the 00s that doomed it. Among the many mistakes it made are:

- Cancelling -if briefly- Solaris on x86 in 2002. This killed Solaris in the minds of many who didn't want to be locked into Sun for SPARC.

- Failing to make a deal with Google in 2002. Apparently Sun insisted on knowing how many servers Google had, something that Google considered a high-value secret, so Sun failed to make a deal with Google, so Google ended up using Linux and contributing to Linux. This was a tremendous mind-share disaster -- it's hard to overestimate the damage done by this.

- Closing Sun PS (professional services). Bad bad move, possibly the worst of them.

- Not giving up on J2ME earlier -- it's not the sort of thing that could last forever, and Steve Jobs killed it with the iPhone. This was a case of vendor lock-in clouding Sun's decision making.

- Failure to recognize that Sun needed to become a systems company, not a CPU company.

- Failure to respond to Active Directory. This was yet another case of vendor lock-in clouding Sun's decision making: the Sun DS product team was milking their existing customers more than they wanted to go after more business with a sustainable strategy.

- UltraSPARC was more than a decade too late to make up for SPARC falling way behind x86_64. Sun needed to give up on SPARC, but again, vendor lock-in sounds sweet but turns out to be poison.

- Failure to make a deal with Apple for it to use ZFS in OS X.

- The MySQL purchase. WTF, this was horrible and stupid. The only interesting effect of this was to make Sun a target of acquisition for Oracle. But of course, it turns out that Oracle -a company built on building mind-share- had become too blinded by vendor lock-in just like Sun, so...

There were numerous other mistakes along the way. These are the most salient, for me anyway.

What's shocking is how long it took Sun to fail under those circumstances!

Also shocking is how much amazing stuff came out of Solaris engineering and the systems division!

> - UltraSPARC was more than a decade too late to make up for SPARC falling way behind x86_64. Sun needed to give up on SPARC, but again, vendor lock-in sounds sweet but turns out to be poison.

UltraSPARC came out in 1995, and Athlon 64 in 2003. I'm confused on how it could be late?

> - The MySQL purchase. WTF, this was horrible and stupid. The only interesting effect of this was to make Sun a target of acquisition for Oracle. [..]

I disagree with this assessment strongly. I believe Oracle wanted Java and only Java. All other Sun properties were collateral damage of the acquisition. It might be weird that Oracle now owns MySQL, but Oracle never cared about it. (Of course, both your and my assessment are mere opinions.)

> UltraSPARC came out in 1995, and Athlon 64 in 2003. I'm confused on how it could be late?

Ah, sorry, I was referring to the CMT architecture.

My brain: Country Music Television? Rather, it's Chip Multi-threading Technology.

https://en.wikipedia.org/wiki/SPARC_T_series

Oh geeze I went from an UltraSPARC III to a T1 and performance tanked.

Turns out my use case was not large numbers of parallel integer only threads.

Basically no real use-case actually are pure integer like that. Basically it performed badly on pretty much all workloads that anybody cared about.

Web and database servers were the target maybe?

I ran Minecraft server on mine.

It's a good list, and it's supported by the anecdotal evidence from my own career: my first dev job after college was on Solaris, but that company moved away from Sun because of Sun DS.

Why do you think ZFS on MacOS would have helped in any significant way? AFAIK, and I may be wrong, but Apple doesn't have a history relying on OEMs for their software, especially something as critical as operating systems. Am I wrong? Was it different back then?

> Why do you think ZFS on MacOS would have helped in any significant way?

It would have bought Sun mind-share. In that time frame Sun was trying really hard to re-acquire mind-share it had lost to Linux due to the non-deal with Google, the brief cancellation of Solaris x86, etc. OpenSolaris was an attempt to rebuild mind-share. Was rebuilding mind-share enough? No, no way, but it was a start.

It could have led to Apple acquiring Sun, say.

> AFAIK, and I may be wrong, but Apple doesn't have a history relying on OEMs for their software, especially something as critical as operating systems. Am I wrong? Was it different back then?

Apple did the work of integrating ZFS into OS X. They believed in it. Steve Jobs wanted indemnification in light of the NetApp lawsuit. Jonathan wouldn't agree to it. Giving it could have been a betting-the-company event, but Sun needed that sort of thing.

IIRC the writing was on the wall by 2002. The x86 hardware was finally good enough that first there was a lurch to WinNT, then Linux once people realized NT wasn't as stable or developer friendly.

That's when I went to work for them. As far as forming my career went, it was a great move. And since it was Solaris engineering I went to, it was quite fun. But yeah, Sun was done -- it just didn't know it, and it spent almost a decade making mistake after mistake. I do think Sun could have been much more successful if senior management had made better decisions, in particular if they'd committed to x86_64 as the future.

Thanks for sharing. What do you think was the reason that the hardware part of Sun failed to keep up with competitors? Specifically why UltraSparc failed to match Pentium?

CPU design is expensive. Intel was ahead of the competition and wasn't fabbing, so Sun was a generation behind. That sort of thing.

Note that today things are quite different, and Apple can do what Sun wanted to do, but do it well. Market conditions are very different, and Apple, of course is the 800lb gorilla that Sun couldn't quite get to be. It's kinda funny: Apple and Sun weren't all that different, and Sun then and Apple now even more so. Apple just wasn't into servers, and Sun just wasn't into consumer hardware, but both wanted to vertically integrate hardware and software. Apple has a walled garden, Sun didn't. I do think these differences are relevant to why Sun failed, but the leadership differences count for a lot too: no one would compare Steve Jobs to Jonathan Schwartz, nor even to Scott McNealy -- it's just night and day. Now the differences in what Sun and Apple sought to do also evince differences in leadership.

Thanks for sharing. I know nothing about CPUs themselves so was curious. I always thought that Sun was into the more premium stuffs, but then I realized that Intel actually caught up with commodity chips. The other workstation/server companies seemed to fall into the same path unfortunately so I guess Intel/AMD was really strong back then.

I started using Sun workstations in the late 80s. I remember when their revenue reached $1b. I had a Sun on my desk as my dev machine for 7 years.

They, and the software that ran on it (Dataviews), and their customers (Westinghouse Software in my case) were all soon undone by the arrival of powerful commodity Wintel.

Do you remember "iPlanet", the "Sun Netscape Alliance"? Netscape's server software was pretty meh, if I recall.

> The MySQL purchase. WTF, this was horrible and stupid. The only interesting effect of this was to make Sun a target of acquisition for Oracle.

Strong disagree with this!

The MySQL purchase wasn't a lot of money and was a move towards becoming a systems company (like you suggested they need to be)

Oracle bought Sun for Java, not for MySQL.

My memory is that Oracle bought Sun for the Java lawsuit, not Java itself.

Oracle sued Google over Java - it wasn't some previously existing case.

Yes, it is Oracle so there's a great chance they were considering this when they bought it.

The disagreement had been going on for years (at least since Google launched android, perhaps before that), Google and Sun had been in “negotiations” that were publicly documented as going nowhere. All that had happened is Google implemented more “workarounds” to use less of Sun’s IP.

I actually remember media speculating that Sun didn’t want to take the next step and actually file a lawsuit, because they didn’t have enough resources to go up against Google in court.

Then Oracle bought Sun, and suddenly the unproductive negotiations transformed into a lawsuit.

And thanks to that lawsuit, we got to see Oracle lose (always nice!) and SCOTUS establish that using APIs constitutes fair use (awesome!)

I think it was both. They would have shitcanned it just like they did with so many other Sun projects. If anything Java has gotten better stewardship under Oracle than the very late Sun years with enough enhancements to make me almost want to try using it again despite Oracle. Almost.

> The MySQL purchase wasn't a lot of money

IIRC it was $1bn or so, and Sun only had like $6bn in the bank. It was a desperate play when Sun needed help.

> Failure to respond to Active Directory

Sun did really well in the academic workstation market, converting the old "VAX and a sea of terminals" into a "sea of Sun workstations".

X11, YP/NIS and NFS worked pretty well for a while, but then Microsoft came out with NT and AD, and Sun failed to respond. Like, ever. I think this was perhaps the worst software mistake Sun made.

It's worse because huge chunk of Active Directory is essentially building on what MIT Athena did, which was heavily used with Sun as well - and all packaged into something that can be brought up operationally by SMB team with no previous experience

Yes, Kerberos is a direct import, although extended quite a bit. AD is a lot more than Hesiod, but AFS is a lot more than SMB. Zephyr didn't make it over.

There was an opportunity to build out graphical management tools, but NIS+ kinda got in the way, and the politics of commercial Unix in general didn't help.

The nice thing with kerberos is that it v5 has extensibility effectively built in :)

I'd say the switch to DAP/LDAP was obvious better choice than Hesiod, and GPO essentially standardizes a lot of tooling that SIPB et al built for Athena as well

Building an AD-compatible service is not that easy, and it was not easy circa 2006, because there was a lot to reverse engineer. Sure, Sun had access to its own directory service (Sun DS), MIT Kerberos, BIND, OpenLDAP, NSS, and Samba, so it had a lot of the pieces, but there was a lot of work to be done putting everything together.

For sure. But Sun had great engineers, and it was a feature that I'd argue was visibly existential at the time.

Sun's engineering culture -and engineers- was the only reason it survived as long as it did. It and they were amazing.

The issue was not reverse engineering Active Directory to make a compatible system, it was that they didn't really capitalize in that direction. Sun has all the necessary pieces to make a compelling option at the time.

Microsoft really only wiped competition in the area when 2000 landed with Active Directory instead of the clunky previous NT Domain system.

Yes. Over-generalizing a bit -perhaps-, the issue was that any Sun division that was a profit center tended to rest on its laurels instead of innovating and disrupting. Solaris was a cost center, so Solaris engineering innovated. The DS folks were a profit center.

I tried to sell XAD, the Active Directory workalike I wrote 2002-2006, to Sun. Would’ve integrated nicely with SunDS (a big part consisted of SLAPI plugins). Was in touch with Jonathan Swartz, but no dice. Sold it to Novell instead. Ironically ended up porting SLAPI to eDirectory to integrate it.

I pushed XAD internally. But I didn't have the pull needed.

Sun not acquiring XAD was a big mistake.

I didn't know you tried at Sun. Obviously I was a big XAD fan :-).

At least they had the intelligence not to sue Google. I wonder how much money Oracle lost on that debacle. (The policy loss is big enough to them on its own! SCOTUS made the right call.)

> - Cancelling -if briefly- Solaris on x86 in 2002. This killed Solaris in the minds of many who didn't want to be locked into Sun for SPARC.

There is an interesting interview with they guy responsible. He basically even said it was a mistake and he knew it, and he internally signaled 'don't worry its just temporary' but there was a cooperate need to signal support for SPARC. Seemed to be internally political.

I think he didn't realize how externally this would look for the viability of Solaris on x86.

> - Closing Sun PS (professional services). Bad bad move, possibly the worst of them.

Can you give some context. I am interested in Sun history and I don't know that one.

> - UltraSPARC was more than a decade too late to make up for SPARC falling way behind x86_64. Sun needed to give up on SPARC, but again, vendor lock-in sounds sweet but turns out to be poison.

What do you mean, UltraSPARC was in 1995. A decade earlier was pre commercial RISC.

(Edit: I see you mean Sparc T1, but those chips were trash, they were not to late. They were good marketing above good product)

UltraSPARC was one of the few actually successful developments. Unlike pretty much every other CPU project at Sun starting in the 90s.

> - The MySQL purchase. WTF, this was horrible and stupid.

Also StorageTek.

> There is an interesting interview with they guy responsible. He basically even said it was a mistake and he knew it, and he internally signaled 'don't worry its just temporary' but there was a cooperate need to signal support for SPARC. Seemed to be internally political.

> I think he didn't realize how externally this would look for the viability of Solaris on x86.

I'd love to see that. Yeah, it didn't go well. It was a disaster.

> > - Closing Sun PS (professional services). Bad bad move, possibly the worst of them.

> Can you give some context. I am interested in Sun history and I don't know that one.

In 2004 Sun closed Sun PS. Well, it... didn't go away completely in that what was left became Sun Client Solutions, but the lay-offs IIRC hurt that unit a great deal.

> (Edit: I see you mean Sparc T1, but those chips were trash, they were not to late. They were good marketing above good product)

Yeah, and it was too late to edit my comment. My bad. But yes. The SPARC folks had some great ideas in the T line, but it was a) way too late, b) didn't have access to latest node size, so it wasn't going to be great-performing, c) performance sucked.

> Also StorageTek.

Eh, not sure about that. The acquisitions of StorageTek and Procom were the only ones I can think of where Sun actually managed to capitalize on what it acquired. The Procom side contributed a Microsoft RPC stack and an SMB/CIFS stack, which was in fact integrated into Solaris. The StorageTek side became the Sun storage appliance.

In 2009 Sun's greatest hope was that its systems work on the storage appliance was going to succeed and save it. That stack was far far better than NetApp's and anyone else's. Of course, that didn't materialize in time, and we know the rest of the story.

With all these mistakes there's enough there to think about many possible alternative paths Sun could have taken, but... there's no point, it's done. I don't recommend dwelling upon much unless you're building a business school case study, and for that I think Sun is an excellent case candidate, especially given that you can compare Sun to Apple and others, so you can see what could have been.

My diagnostic is that McNealy checked out with the 2001 crisis, Schwartz was just a really, really bad steward, and no one wanted to take the hatchet to the vendor lock-in products that were holding Sun back. In 2002 the right thing to have done was to announce less investment in SPARC and start winding it down -- that would have freed many billions for other things later in the 00s, and it would have saved Sun PS. But perhaps in 2002 Sun didn't have the systems expertise needed for the transformation it needed to undertake.

Meanwhile Apple was never wedded to an ISA for long, and even now that they make their own CPUs they could easily switch if they had to. I say 'easily', but it's monstrously expensive, yet for Apple it's totally doable. Steve Jobs wasn't afraid of disrupting Apple itself. That's what Sun needed: internal disruption.

You can find the interview here:

https://www.youtube.com/watch?v=-vDunup8v5M&t=2940s

I'm not totally convinced by the reasoning. Would love to hear some former Sun people give an opinion on his leadership and other perspective.

> Yeah, and it was too late to edit my comment. My bad. But yes. The SPARC folks had some great ideas in the T line, but it was a) way too late, b) didn't have access to latest node size, so it wasn't going to be great-performing, c) performance sucked.

Dropping performance a little bit for Multicore was reasonable for servers, and there were some good ideas there but in practice it was far to extreme to be practical.

StorageTek was quite expensive and sold mostly very large archiving solutions. Not sure that was really the right direction. Such a huge acquisition cost a lot, not just money.

But you are right that this was not totally unreasonable. Still its pretty aggressive move for the company in the position of Sun.

> Sun needed: internal disruption.

After the disaster that was Viking. They might have gone 32bit x86, 64bit Alpha. DEC was desprate for Alpha buyers and would have made them a good deal. But they double down on going all in on SPARC and UltraSPARC confirmed them in this being the right solution.

> > Sun needed: internal disruption.

> After the disaster that was Viking. They might have gone 32bit x86, 64bit Alpha. DEC was desprate for Alpha buyers and would have made them a good deal. But they double down on going all in on SPARC and UltraSPARC confirmed them in this being the right solution.

The only reasonable option in the early- to mid-00s was x86_64, especially after around 2004. Even just before x86_64, having a conversation with AMD about it would have been enough -- x86 was the present and future of the industry, and all that was needed was for this to be accepted by Sun.

Viking I am talking about was around 1992.

Of course by mid-2000s that is different.

Thanks for the link!

Since we're sharing, I have fond memories of my using my the Sun thin clients at university. They were slow to start up and use for the most part, but once you got to the terminal... it was great.

Being a hacker-type, I did everything with it.

Email? Forget waiting for some bloated email client, I'm using pine.

Want some html on my personal page? Use vi.

I think they didn't take away my access for years after college, and I would sometimes login and poke around just for fun.

I do blame them, along with the rise of Java and the awful gui toolkit motif for convincing me to drop out of computer science and switch to Computational Math for my bachelors degree. I was so frustrated that our grades were dependent on learning something that I saw as completely worthless in light of the dotcom boom happening at the time. I wanted them to teach us web technologies, or at least some good system code, but all I got was broken x11 and awful performance.

> I do blame them, along with the rise of Java ...for convincing me to drop out of computer science and switch to Computational Math for my bachelors degree.

I avoided studying CS for this reason: I saw my girlfriend's Java textbooks and thought if I had to appreciate this, I wasn't cut out to be a programmer, and stuck to network engineering. Years later, after 'Gang of Four' style OOP started dying, I have some code in a new things people use here everyday.

I appreciate this comment for reviving memories of pine and lynx and all of that

xtalk!

ytalk!

I used a machine that had 8MB of RAM and a huge b&w monitor. One day I found out it would crash if your process forked more than 127 times. These things were so cool at the time but are nothing compared to a Raspberry Pi.

It's absolutely crazy to realize that even a Pi 400 running from MicroSD would smoke classic workstations of yesteryear, and yet by today's standards it's slow.

I felt old when I realized that someone had put my first "big boy" unix computer, a decstation 3100 with 24 mb of ram, onto a business card.

https://dmitry.gr/?r=05.Projects&proj=33.%20LinuxCard

People used to joke that EMACS was an acronym for "Eight Megs and Constantly Swapping", just to give you an idea of how constrained memory was in those days.

Even the computers we think about as the first "PCs", the IBM 5150, shipped with 16 or 64kb of main memory. They were much closer to machines like the Apple II or the Commodore 64 than most people realize.

I supported a bunch of 8 and 16mb sparcstations, but they were a grant from Sun to the university, so no griping.

105 mb disks meant (almost) everything was NFS mounted, and NFS did a great job.

But to your point, with 8 megs, Emacs Makes A Computer Slow.

And there was no budget for upgrades to anything.

I was spoilt by SGI and their wonderful interface, where every detail was awesomely cool. The Sun machines were just old-fashioned at this superficial but important level of how it all looked, but only if you knew better, and that meant experience of SGI. In the world of IRIX, we had CPU-eater desktop wallpaper, meanwhile, on Sun, you had some badly drawn window decorations.

I imagine this to be the awful GUI that you speak of.

I say look and feel is superficial, however, when you have to learn a variant of UNIX with slightly different command line switches to the UNIX you know, with an interface worse than even Windows (3.11), for it to run dog slow, a lot of copium is needed. A poor interface gets in the way of what you are trying to do, a cool interface just lets you get on with it.

Motif wasn't considered ugly at the time (at least by most people). If you ran Netscape on your SGI, you know what Motif looks like.

Motif did have a reputation for being a total drag to develop with, though. It's based on Xt. So is Athena, so if you've ever written an Xaw app it's pretty similar.

Right, I still remember the dotted XaW scrollbars that would scroll a little or a lot depending on where you clicked them; and playing Freeciv with XaW in my early Linux days. Good times.

Motif was even released as open source OpenMotif, but faaar too late. The whole Xt architecture in general seemed like an overcomplex solution looking for a problem, and it was easier to either use Xlib directly or go the gtk route.

The resources system was really cool though. It gave you a unified configuration system and allowed deep levels of themeability. I remember you could assign a pixmap to every element of Netscape 3's interface, for instance.

Considerable portion of later Irix software was Motif too - just "Irix-special" version (major optimizations for rendering among other things by mixing 8bit pseudocolor and hardware compositing)

I think motif was fine for its time, but definitely not much better than OpenLook.

However, 30 years ago, developing a standard SunOS app with devGuide was the most enjoyable and productive programming I've ever experienced. Simply layout your GUI, link actions to methods, generate code, fill in the abstracted methods, compile and run. I didn't have to learn X or any other bloated low level graphics library.

AFAIK, nothing has been easier, especially XCode.

>Want some html on my personal page? Use vi.

Same guy who invented Vi invented Sun Microsystems. Bill Joy.

I sold my Sun stock at the internet bubble top for $70 a share. A few months later it was $7. I think of that when I see PE ratios in the hundreds for Tesla, SpaceX and other AI stocks.

Good timing. But on the other hand if you had sold AAPL, MSFT, NVDA, ORCL, AVGO, ADI, KLAC, LRCX, etc at the Internet bubble top then you would have missed out on huge gains since then.

Your point is correct, but let's not gloss over that most of those had 80% drawdowns or more. The nasdaq took 15 years to recover and it's only been 25 years total, meaning 60% of the time since then you'd have been living with a paper loss. Timing is difficult but powerful. (Just not as powerful as 25 years of waiting.)

People will eagerly tell you that some types of investments are guaranteed to show returns over a long enough period, but over a long enough period we'll all be dead.

The majority of people who were alive in 2001 are still alive today.

But possibly not the majority of people who might actually buy those stocks. Look into statistics on stock ownership by age.

> […] etc at the Internet bubble top then you would have missed out on huge gains since then.

Only if you never repurchased.

Or you could DCA out: have a standard policy that no single stock can be more that x% of your portfolio, and as any one gets above that limit you crystallize profits. It's no different than having a 60/40 portfolio and rebalancing your equities if they get >60%.

I lean more towards passive and (total) market index funds, and just riding the roller coaster, as anything else is fairly either impossible or too time consuming:

* https://ofdollarsanddata.com/even-god-couldnt-beat-dollar-co...

Scott McNealy had a few choice words in retrospect[1].

[1] https://news.ycombinator.com/item?id=40950311

The top was ~$120 or so. Ask me how I know ;-(

Making workstations even in the dominant market position that Sun had, was a cottage industry compared to technology today, and it was managed that way. I wouldn't blame management for Sun being irrelevant now.

What everybody except Steve Jobs got wrong was not taking user interface seriously enough. Not even Xerox. I've used aa Xerox Alto, a Sun workstation, an LMI CADR, and a Symbolics 3600, and none of them were as carefully crafted as a Macintosh with a tiny memory and a floppy disk. Next inherited this ethic.

Jobs valued the person using the machine more than anything else about the machine.

My personal favourite UI was HyperNeWS built on Sun's NeWS.

Edit: Writing PostScript and having no discernible security probably didn't make NeWS a great fit for the world of the Internet - but it was a lot of fun.

As long as it is local its fine, I mean X also doesn't have much security, its not that big a problem.

> What everybody except Steve Jobs got wrong was not taking user interface seriously enough.

But Linux took over the world and it had a crappy UI. I was there, back when Xorg didn't even exist, running X and messing with modelines on Linux. All the window manager sucked big times.

Sun, just like SGI, got attacked by cheap beige PCs running either Windows or Linux.

I don't think their UI had much to do with their downfall and, arguably, SGI's UIs were better than the competition and they still disappeared too.

Also weren't most machines sold by Sun servers anyway? Their famous "We the dot in .com" tagline.

Linux was free, and people will put up with a lot of shit for that.

Exactly. Free vs. $8k (in 1990 dollars) for a NeXT computer was a pretty easy choice for most people.

to be fair, nobody in 1990 decided between NeXT and Linux, because (A) Linux didn’t exist yet and (B) they were / would have been completely different markets and totally different capabilities.

True. I think linux maybe had just been released but there was nothing like a "distro" that was easy to install.

Minix existed at the time too, I know because I ran it on an 8088 PC.

But within a few years, linux started gaining mindshare and was starting to replace proprietary unix especially on individual PCs.

You're off by a year or two at best. Linus announced his kernel project on the Minix usenet group in Aug 1991.

It wasn't until mid 1992 that distros started to exist, and I'd say it took a bit of time for those to be complete enough to be usable for someone with a goal other than smoke-testing the kernel on their PC.

I can say for certain that I, a complete newbie, was able to boot SLS Linux floppies in early 1993, and within a couple months I was installing Slackware to HDD.

Yeah, 1993 is when things really took off. First SLS, then Slackware, and using Slackware as the build environment: Debian.

You also had SuSE, which really started as German-localized Slackware.

"Free", until mid 90s I guess most people bought Linux distros on CDs, later DVD (no downloads). For me the big, big plus on Linux (vs. Dos / Windows), had been all the free compilers.

I'd have to say that gcc is the unsung hero of FOSS. If you wanted compilers on your shiny new commercial-UNIX box, you either had to fork out $$$ or find a way to get the GNU toolchain into place. Even on PCs compilers tended to cost a lot, with Borland being a shining exception.

Somewhere, I still have a Red Hat 5 retail CD. I'm not sure, but I might have bought it at Borders Books rather than a computer shop. I know I bought a few CD-ROM collections at the bookstore.

Linux books that included a CD-ROM with the subject distro and software were pretty common in that era.

I also recall that Linux on a PC often beat the performance of Unix equipment I could access in contemporary times. There was a lore around those machines, but my actual experience doing basic FOSS-adjacent dev work (bash, make, gcc, autoconf) was that the Linux PC was faster as well as inexpensive.

The exceptions were mostly hardware graphics accelerators in some labs, when my Linux PC had to do it in software. And I got myself a surplus DEC Multia (alpha) that was really fast with Linux for natively compiled code, beating my contemporary 486DX3-100. But, the PC was still faster for web browsing, because running Netscape on alpha meant doing x86 emulation!

Likewise, my ~90 MHz Pentium MMX laptop with Linux was faster at regular dev work on my work-supplied Sun Ultra workstation in the late 90s. (Edit: Hmm, I am not sure about this laptop anymore, it might have been 166 MHz??)

Due to my positive experiences, I was an aggressive early adopter (and frequent beta tester) of nearly every Linux ecosystem frontier for decades. E.g. 2D accelerators, 3D accelerators, SMP, large file support, gigabit ethernet, wireless ethernet, power management, virtualization, 64 bit architectures, SCSI/SATA/Firewire/e-SATA/NVME, hardware and MD-RAID, ext2/ext3/xfs/btrfs, ...

The vast majority of Linux installations don’t have a UI, they’re headless, and it was the same with Sun. I.E. the UI is irrelevant to the success or failure of Linux and Sun.

Linux took over the world because any licensing model that requires a per CPU license simply can’t work in a massively scalable situation like server farms and cloud.

> But Linux took over the world and it had a crappy UI.

Linux took over in all the places where a good GUI didn't matter. In ran most of the Unix server software on hardware orders of magnitude cheaper than what was needed to run a commercial Unix. Windows ran on that same cheap hardware but was much more expensive for the same capability.

Despite Sun's marketing push Linux was really the dot in most of the dotcom darlings.

> Linux took over in all the places where a good GUI didn't matter.

like smartphones ;-)

There's a vast gulf between Android and a Linux desktop environment. Android is a Linux kernel with the Android environment on top and is not just some Linux distro like anyone uses on a PC. ChromeOS is very similar.

Android and ChromeOS are still Linux distros, with a UI dedicated for their exact purpose. There have been other distros in the past trying to explore different ways of building a Linux, Gobolinux for example tried to get rid of the traditional POSIX filesystem hierarchy. Sure Android and ChromeOS probably diverged more but that doesn't make them any less linux distros. For a start, termux couldn't exist if android wasn't a Linux distro as no emulation or vm is involved, these are typical linux userland and processes running on android.

FWIW and for good reasons current Android UI is terrible for a desktop usage and ChromeOS is too limited for some people.

> But Linux took over the world and it had a crappy UI. I was there, back when Xorg didn't even exist, running X and messing with modelines on Linux. All the window manager sucked big times.

My first exposure to Solaris was in 2003 when Linux had Gnome 2.6 and Solaris had CDE. The UI on my Debian box seemed decades ahead of the Solaris machines I managed, which looked like Windows 3.1 and performed about as well.

Combined with Linux package managers being infinitely better, the GNU core utilities having so many more conveniences and options than the Solaris equivalents, I felt like Sun was this dinosaur that couldn’t die fast enough. I’ll still never understand why so many people praise Sun for its engineering culture when free software seemed so superior to me at the time.

My favorite anecdote exemplifying my opinion about Solaris at the time: you log into the console of your Sun workstation, running SunOS, with your Sun keyboard plugged in, and press backspace. It echoes ^H back to you. They couldn’t even figure out how to configure their own keyboards correctly out of the box.

Maybe in the 90s the standards were different. Maybe their tech was better. But by the time I ever used their software is was the butt of jokes.

> My favorite anecdote exemplifying my opinion about Solaris at the time: you log into the console of your Sun workstation, running SunOS, with your Sun keyboard plugged in, and press backspace. It echoes ^H back to you. They couldn’t even figure out how to configure their own keyboards correctly out of the box.

That's really an old-school UNIX convention that should have died with the move from teletypes to CRT terminals. The default behavior was that ERASE was # and KILL was @ (rather than backspace and Ctrl-C). It was typical for these to get set properly on logging in.

Well, of course, getty doesn't know whether the thing plugged into the serial port is a teletype or a CRT terminal. But the actual Sun console isn't a serial port!

KILL isn't Ctrl-C. That's INTR, as you can verify in stty -a. KILL is Ctrl-U.

Ahh, ^H brings back memories. We had Solaris x86 machines in the computer lab at UC Santa Barbara when I was there from 97 to 02. They were deathly slow never mind that CDE was miserable too. I made it slightly less painful by loading the BSD versions of the utilities and using those. Pretty much gave up and ran FreeBSD on the desktop with Window Maker.

Sun got by because they had faster and more reliable hardware than what was available in the x86 space at the time. eBay's services ran on a handful of 64 CPU Starfire servers. And proprietary UNIX workstations had a bunch of specialized apps that weren't available on Linux at that point.

This was my experience as well, from the same time period 2003ish. My University's computer lab was all Sun. I thought CDE was shocking, I was immediately repelled by it when I started using it and had a similar experience with those Sun keyboards.

One of the other students in that class gave me a Mandrake Linux cd (It ran KDE) he taught me how to use SSH. After that I worked from home and submitted my assignments remotely. I have not looked back from Linux since.

I don't think it was limited to Sun. The first job I had out of university there were computers running HPUX also had CDE gave me flashbacks straight back to university. It definitely gave me the impression that all the commercial Unix companies were ancient Dinosaurs that had zero taste.

> My first exposure to Solaris was in 2003 when Linux had Gnome 2.6 and Solaris had CDE. The UI on my Debian box seemed decades ahead of the Solaris machines I managed, which looked like Windows 3.1 and performed about as well.

Linux having better UI than proprietary Unices (except SGI) was true from the beginning. In 01993, even before package managers, the Linux standard was color rxvt, color ls, Seyon, fvwm with multiple virtual desktops (really important at 800×600), Emacs preinstalled, and you could termify your web browser and whatnot so you could run them at home on a dialup shell account. Proprietary Unices (except SGI) had monochrome xterm, vi (with no arrow key support), and typically either twm or mwm, which both looked like shit and still do. Suns sometimes had olwm but Sun had sort of abandoned Open Look by that point. If you had a Sun at home connected through a dialup shell account, you could forget about running any TCP/IP apps on your Sun. By 01996 the Linux world had slirp, so you didn't even have to termify your TCP/IP apps, while Solaris didn't even include a C compiler anymore.

CDE seems like somebody thought that the problem with Motif was that, although it was butt-ugly, it wasn't quite ugly enough.

And, yeah, backspace worked. Also automatic window resizing. And for years Solaris had a totally fatal TCP round-trip estimation bug which made TCP connections to Solaris machines over dialup incredibly slow. Linux was just dramatically more technically competent.

Sun did have a pretty amazing engineering culture. They shipped SPARC, Open Look, NeWS, Java, HotJava, HotSpot, NFS, Sun RPC, yp/NIS, Spring, ZFS, OpenBoot/Open Firmware, and I think even Sprite, and for a while they employed the Tcl team, bringing Tcl out of the stone age. But they sucked at fixing the fatal flaws in their actual products, and half the engineering achievements in my list above were murdered by Sun's incompetent management.

I remember a web page put up by an SGI employee, saying that x86 wasn't going to destroy the Unix workstation business. The title was "Pecked To Death By Ducks".

Then Intel came out with dual-core processors, which was the new hotness. So he wrote a followup page, literally titled "Pecked To Death By Ducks With Two Bills".

At the time, I thought they were funny, and made reasonable arguments. But in retrospect, they were just trying to distract the customers from the fact that Intel was overtaking them.

At the end of the day, the UI on a Unix server was always shell based. That was just the best way to configure a server. (And, in some way Infrastructure as Code is an evolution of the shell scripts a unix admin would use.)

Linux won on the server side because they got just as right as Unix. The crappy UI (windows) was the one that didn't work with shell scripting, didn't work with ssh, etc.

IaC is really just declarative shell scripts. It's a different language, but it's often just kicked off by some bash in a git action.

Once you have git and actions, I don't think that the language really matters all that much.

> and it had a crappy UI.

That wasn't even true back then.

> Sun had become bored with the mechanics of running a business.

I would contend that Sun was never interested in running a business. They always cared more about building amazing technology and suffered the sales to make money.

You can't deny that Sun hardware was top tier and always ahead of its time (until Oracle bought them).

Edit: I had on rose colored glasses. I was thinking of late 90s SUN. They did in fact start getting crushed in the early 2000s.

> You can't deny that Sun hardware was top tier and always ahead of its time (until Oracle bought them).

From Brian Cantrill's original HN comment in 2011(https://news.ycombinator.com/item?id=2287033): "I never hesitated to tell anyone that was listening that our x86 boxes were starting to smoke the hell out of UltraSPARC". SPARC stopped being ahead of its time way before being bought by Oracle.

>> You can't deny that Sun hardware was top tier and always ahead of its time (until Oracle bought them).

> SPARC stopped being ahead of its time way before being bought by Oracle.

You seem to be focusing strictly on performance, but there were other factors: e.g., remote management is still a bit of a mess with x86. With SPARC everything can be done on the CLI (serials consoles or SSH), with x86 quite often you're still clicking on "open KVM window" for so many things. And of course many/most vendors make you purchase an 'advanced license' to use the remote KVM functionality of the LOM system.

Why is that a property of the ISA?

It's path dependence. If you built a Sun-syle x86 server with a serial console and inserted a random Linux installer CD, the installer would probably only output VGA and thus it wouldn't work.

Debian installer runs fine over serial, at least.

I would wager that almost no Linux installs are done by CD or displaying VGA anymore (maybe 0.01%).

> I would wager that almost no Linux installs are done by CD or displaying VGA anymore (maybe 0.01%).

When one of your Proxmox (or XCP-ng, or VMware/Nutanix/OpenStack) servers won't boot and you need go into single-user/rescue mode, then talk to me about the convenience or not of a remote KVM (versus having to drive to the DC and hook up the crash cart).

It's all very well if all you manage is VMs/instances, but some of us deal with the hardware that those VMs run on, and things break.

That 0.01% of servers is probably the layer that the other 99.99% run on (and yes, a lot of that 0.01% can also be automated, but if PXE isn't working (or you're getting strange CPU3VOLT or SLOT17ECC or BUS1RESET errors) then neither is re-imaging).

The alternative isn't driving to the DC; it's remote serial console through a console server or the BMC.

It's a very good habit to make your Proxmox hosts PXE-bootable to avoid this kind of situation. We're using this approach with Talos as Kubernetes host and it works very well.

Path dependence again. x86 servers in the 1990s had to have VGA so it was never removed. (Except Oxide.)

Oxide happened long after (U)EFI brought proper serial support to boot process

Yet every UEFI server has VGA and remote KVM.

Because pretty much every BMC out there in last decade is shipping AST2400/2500/2600 which include VGA and you want to deal with cases where people do not know how to navigate serial console, especially in case of windows servers

That's part that was changed with UEFI when the old IBM PC "contract" was finally severed.

Yeah, that was amazing. And so, I learned how to provide LILO + agetty on COM1 on every server I was admining :) So, unless there was HW fault, I could just connect to server via serial to check things out.

> You seem to be focusing strictly on performance,

Just like the vast majority of buyers do. SPARC was abandoned by customers due to poor performance.

> but there were other factors: e.g., remote management is still a bit of a mess with x86

That's a property of the systems integrator, not the ISA. Dell's iDRAC works quite well.

> Dell's iDRAC works quite well.

I currently admin several racks of Dells (and Lenovo, and SuperMicro, and previously HP). Just make sure you buy the license for KVM in case you ever need to go into single-user/rescue mode (otherwise better not mind having to drive to the DC and hooking up a crash cart).

Ask @bcantrill (the author of this article/story) about how well integrators integrate (as a hint to the answer, he co-founded Oxide Computers because he ran a cloud service with Dells/HPs/etc).

Integrators integrate very well at the level that they're operating, i.e. the single server. Rack-level integrated systems are a whole different thing, very specialised and unrelated to the old thing.

You can ignore KVM license if you have good netboot infrastructure and only install OS in UEFI mode - SOL works fine.

The big issue is usually "remote media" support, thus my recommendation for setting up netbooting infrastructure

I can deny it. It was OK, but not amazing. I had to make pretty frequent repair calls on their gear--much more frequently than the less-technologically-amazing-but-solid-as-a-rock Dell and Compaq gear. IBM, Digital, and HP (yes, that HP, before they lost the Way) also had very good UNIX gear, but Sun had the mindshare during the '90s.

In terms of performance, even Linux 0.x on a 33Mhz 486-class processor could outperform a uniprocessor Sun/SPARC box at a fraction of the price.

I also question the sanity of anyone who thinks Sun's choice of 13W3 for a video connector was a good one. :-)

I don't know, the clustering on Solaris was pretty amazing, if we are just judging "ahead of time"

DEC's VAX/VMS had decent clustering in the early 80's.

Any Unix "clustering" system I've used (Veritas on Sun, HA/CMP on AIX) always seemed bolted on.

I'd say the basic idea of 13W3 connector was fine, what was not was not trying to agree with others on pinout, and evolving the connector in a way that made invisible incompatible difference whether you had DDC-capable or not

I loved Sun hardware but I'll deny that they were ahead of their time after 2003 or so. I had a boss who loved his pizza box but Intel/Linux crushed them in the 2000s on a price/performance basis.

I think this sorta forgets how slow the cpus were - I was running mostly ASIC design workloads on big Sun hardware in 2001 and we eventually got some x86 boxes that were only 32 bit but could run some of our jobs - and the single-threaded perf of these commodity machines was amazing compared to the Sparc boxes. When x86-64 came around, this was the death of all the Sun hardware in that group.

Also sometime in 2000 I had interviewed at Compaq - the old Alpha group who I think later worked on Itanium at Intel. They were constantly frustrated because they couldn't even get a build from Synopsys of the design tools they needed to run on Alpha and were forced to use Sun hardware they described as "gasping and wheezing" to design their crazy fast cpu.

Sun lost on a bunch of fronts, but I think the amazing thing is they let happen to them what they did to the other big UNIX vendors before - they were eaten from the bottom by faster cheaper hardware.

Yes, I had the same experience while using various Sun computers between 1995 and 2005. During all that decade the Sun computers were reliable, but excessively slow.

Around the beginning of 2006, I had a laptop with a 64-bit AMD Turion CPU and I could run on it Cadence and Mentor tools for ASIC design and the simulations were much faster than on a big Sun multi-processor server. Later that year our team finally got some servers with AMD Opteron, which accelerated dramatically the work in comparison with the traditional Sun servers.

Both SPARC and PowerPC met the same fate. A brilliant ISA done poorly was no match for a poor ISA (x86) done really well.

I had the same experience twice in a few months from those two. Moving from a Sparc server to a Xeon based system, and again when the first Intel Mac Mini's came out and was faster than the dual-G5 systems we had.

I recall a fork/exec heavy shell script at a previous job that ran about an order of magnitude (~25s vs 3s) slower on Solaris/SparcV9 vs Linux/Intel P3 circa 2003. The standard retort back in those days was to rewrite it in Perl.

Same here. I've been in the chip design industry since 1997. Everything was Sun and I was right out of college and convinced my manager to let me use a Linux/x86 machine and I used the savings to buy a large 21" monitor that would run at 2048x1536 resolution and use it as an X terminal to the Suns. Everyone else loved it and did the same.

Around 2000 we started getting some EDA software released on Linux. I remember getting some Linux kernel patches and recompiling the kernel to change the user / kernel split from 2GB / 2GB to 3.5GB user / 0.5GB kernel. But we still needed the 64-bit Suns for some jobs that needed over 4GB RAM. Itanium was really expensive and slow and then AMD released the 64-bit Opteron in 2003. We bought them immediately and never bought another Sun.

My high school in 1992 got a bunch of old Sun3 and first gen Sun4 systems. I absolutely loved them. My dream then was to have my own Sun workstation but they were way too expensive. My other dream was to go to college and then get a job at Sun. I heard about Linux in 1993 and got my Unix system at home. I did work on some Sun UltraSPARC III companion chipsets but Sun couldn't compete on the price to performance ratio with Linux/x86

We had the Sun workstations in college (some with that crazy laser mouse) and I think towards the end of my tenure, most of the labs were switching to linux boxes, but at that same time Solaris x86 actually came out - so on commodity hardware you could run Solaris which was kinda fun.

I did this a little, but the things you could do with actual Linux started to get interesting for me at that time - building routers for our shared home network, hosting Quake servers, doing actual programming with gcc etc and the hardware support was a bit better as I recall.

I also interviewed at Sun in Boston - I think the small group servers group or something - I really liked the engineers I met there and I did consider working there for a minute, but ended up in Silicon Valley which I think was better fit for me.

Thanks for sharing. I just read an article comparing UltraSparc III and Pentium 4. The frequency is the biggest difference, and while the article also highlights a few pros for the Sun processor, like being 64-bit and super scalar, the benchmark shows that P4 has a clear win. I don’t know the price tag then, but I guess Sparc was actually more expensive?

The article is here: https://www.silkstream.net/blog/2006/08/comparison-ultraspar...

The Sun system would have cost several thousand dollars more than a generic Pentium 4 box.

One of the things that Larry Ellison found utterly baffling when he acquired Sun was the way that sales commission was calculated. It was all on the value of the contract, with no requirement for the contract to be profitable.

At least in the later stages of life Sun sales folks were literally selling the company into bankruptcy. They'd find out what competitors were offering, undercut it to the degree they'd make a loss, just to get the contract and their sweet commission.

To not realise you've got this going on really speaks to how little they were interested in the actual running of the business.

Sun's various divisions all cared very much about their respective vendor lock-in, so they didn't innovate fast enough. The divisions that didn't have that innovated. On the way downward Sun cannibalized itself (think Sun PS getting closed).

That's the whole gist.

The Sun model of beefy server, ultra-thin client worked incredibly well and presaged the widespread adoption of virtualisation that eventually led to cloud computing and containerised software. Unfortunately that model made it very easy to undercut their prices using commodity hardware; I managed a Solaris/Sun Ray network c.2004 and it was cheaper to switch to Linux/Intel and buy spare hardware to keep in a cupboard “just in case” than to keep the Sun network going through its support contract.

it is often cheaper to buy a spare of something and throw it in a cupboard rather than have a support contract.

I have a bunch of Aruba switches and this is what we do, because it's a lot cheaper.

If you are only buying a single spare that is the case. Support contracts make sense when you would want several dozen spares.

if a support contract is 70% of the cost of something, then for every 2 of something a spare is cheaper.

For Aruba I think it was 1:1; a support contract was the same price as the device itself over 2 years or something.

Support contracts never cover a "site" they always cover individual devices, so your cost scales with the amount you have... so I'm not sure I follow what you're saying..

Unless you mean to imply that you're replacing units more than once every 2 years, in which case of course you're right... but then I might consider going with another vendor entirely because that is a pretty terrible reliability record.

There are lots of different support contracts. Some of them really do cover the entire site. You seem to not realize the scale of a large data center. If every device lasts 5 years you are replacing 10 per day is not unheard of.

Support contracts never cover a "site" they always cover individual devices

Wrong. I've signed many support contracts that were negotiated basically to "one flat fee for everything we sell that you use, including future purchases[1]" for some period of time. Some people think that they 'optimize' contracts by pushing for "I just want a service contract only on the SKUs I have". That's not always a real optimization.

[1] Often, this includes a tacit "including things you are using that you didn't tell us about".

Interesting, I've literally never seen that (though obviously not doubting your experience) and I have (at one point) been in charge of 1% of web traffic..

I'm wondering if this is something uniquely american, because we don't seem to have much negotiating power in the UK/SE.

I'm guessing it is the size of your company or datacenter. You have to be throwing around millions of dollars to get the opened ended contracts.

Sorta. Writing a 7- or 8-figure check certain gives one the leverage to negotiate. That said, if you're talking about US$250k DC switches, the vendor cares about each and every one. But if you're talking about 250 US$1k switches, you can talk about "let's make this easy on both of us...". Software licensing contracts are even more malleable. Having a really ballbusting purchasing and contracts team is fun.

Java applets!

Is this how the whole LLM thing will go down once providers raise prices?

Maybe - ask me in 20 years...

Nobody knows how the future will be. There are lots of options. There are self hostable open models today - they are not as good, but some report they are good enough. Right now I don't have the hardware to try them (I could - if I'm willing to accept a small number of tokens per minute - useful means more tokens per second as I can get in an hour). However I expect in a few years I'll be able buy consumer hardware with good enough GPUs (or perhaps an AI chip???). Will anyone other than a few hobbyists buy them? time will tell.

I think prices will go down not up eventually and everybody will have access to it in abundance. That might make most current AI companies go down of course.

And space launches. The Big Names will lose a ton of money and disappear as the tech commoditises.

The moat is Being Able To Do Things No One Else Can and as both hardware and software commoditise that moat disappears.

Open LLMs are already only a few months behind the frontier models and as soon as someone works out that accessible and cheap domain-specific custom training has the potential to be a gamechanger the Big Names will die.

Math puzzles only get you so far.

LLMs are in their Big Compute phase, and it's only a matter of time before that ends - because the intelligence of the frontier models isn't increasing fast enough and providing big enough benefits to make the models more valuable than cheaper, smaller competition.

i mean, imagine if your a business and suddenly you had to expense > $200 a month for every employee just to run a compiler, or you could just buy a computer and use it for everything else and that as well…

i think llms will be the same.

n=1 but at $work they are forcing us off enterprise and on to personal claude max that caps at $200 and people are like “you don’t need the top end models anyways just use the cheaper one for coding”, which begs the question how long till those “good enough” models run locally (with relative ease) and our company can cut that huge monthly cost with just the macbook pro they are gonna buy anyways.

I worked at Sun labs and used a Sun Ray daily for a whole summer. It worked...OK. Definitely not "Incredibly well". We had a network of a few hundred Sun Rays and two E10Ks backing it. More than a million for the servers and $1000k a piece for the Sun Rays was not cheap. Basically any $1000 laptop was more powerful, without the need for a crazy powerful Sun server. The experience of taking out my ID card, walking down the hall to another cubicle and popping it in and getting my session was magical. But I did that less than once a week, so I don't think it was overall worth it. The Sun Rays also had a pretty crappy LCD, about 1-2 years behind the SoTA.

It was a cool idea. It will keep coming back again and again. But at Sun's price points around the early 2000s, it was a loser, and I actually agree with the market in this instance. Sun Ray was a flop.

"It will keep coming back again and again."

It lived on in the world of Windows Terminal Services and things like Citrix - maybe still does in some places.

It lives on in the world of LLMs in a way.

Citrix is still everywhere you need a client that can do things a web browser can’t—like run ancient VB4 software or talk to device hardware—deployed at scale.

Citrix was bought out by PE for $16.5B a few years ago, under the (sadly correct) assumption they hadn’t been charging their customers enough money for this essential tech.

Chromebooks…

$1000k ?

Stadia? GeForce Now? Xbox Cloud Gaming? :-)

GeForce is pretty successful. But only because Nvidia can sell itself GPUs at cost and reuse old data center hardware to get lower prices than anyone else.

If you're not cheaper than buying a PC or console you can't win. No one wants to pay more for the privilege of input lag and compressed video, or getting in trouble with their ISP if they have a strict data cap.

The "two E10Ks" part is the important part there, as you need a very powerful server to support SunRay users running Solaris. At my university there was something like 200 SunRays supported by cluster of T2000s (7 nodes IIRC), it was fine for CDE, Firefox and few dtterms, completely unusable with Gnome (it took Gnome like 10 minutes to even start).

On the other hand I have heard of some success stories about using SunRays as RDP clients, which is actually supported configuration (you still need a Solaris box that manages the sunrays and translates RDP to ALP).

I think it was not a technology that should have been designed for people actually doing series work. But for things like kiosk, self service terminals, and stuff like that.

And yes of course, a rack of commodity servers should how powered the server side, as this was a task that could be scaled vertically quite well.

The also didn't use the cheapest possible Sun Ray terminals, they used their internal developed embedded Sparc chip, not mass produced ARM chips.

Remember, "The Network is the Computer".

Which is why it is kind of ironic having folks discussing microservices as something groundbreaking.

Counterpoint: it actually sucked. Entire universities lost a day's work when their editors were all fatally stuck in an rpc.lockd bug.

the lab I was at got on this train right around the beginning of the sparc architecture. yellow pages. nfs based swap, nfs based boot. 10Mbit thinnet. we suffered for a few months and then moved to xterms for the cheap seats (which was a much better place to cut services) and went back to buying self-sufficient workstations.

the best was having everyone with a disk cross-mount each other. any failure snowballed into a global failure.

Buying from Sun may have devolved into a direct-touch upsell disaster. Esp. compared to Dell which at one point was almost unique in having a working, easy-to-use web product configurator. Dell really nailed "getting products ordered and to the customer is part of the value equation"—a supply chain virtue no one else was really optimizing 1990–2005.

But selling to Sun Microsystems as a vendor was a joy. It paid bills like clockwork (net 35 IIRC). Completely showed up all the multi-$B IT competitors. They preached hyper-efficiency, but Sun delivered it in its own dealings. Unfortunately after the dot-com downfall Sun extended days payments outstanding (DPO) just like everyone else.

That was Dell in the past. Now Dell gives you this, https://www.dell.com/en-us/shop/dell-500w-power-supply/apd/c..., which tells you almost nothing about connectors it has. Don't ever buy Dell.

I think the most important thing Sun got wrong was having no credible onboarding path for new clients. Why would someone invest in SPARC and Solaris when a generic x86 with Linux would do 99% of what the SPARC box would do, for far less? Why would someone who is developing their software on an x86 box with Linux care about deploying it to SPARC+Solaris? Or SPARC+Linux? Or x86+Solaris? There is a huge advantage in deploying to the same platform you develop for, which means, not having a credible desktop will hurt you in the long run.

The same applies to IBM's POWER and Z - how many green field projects are being built for them? Apart from weirdos (such as myself) who is even interested in that? And even then, I will not suggest building anything new on AIX or z/OS, or Linux on either, unless there is a really compelling (such as "we got the hardware for free", or "we really need instruction-cycle latencies to run inference and we can't match that with any other NPU") reason.

Don't get me wrong - I love using uncommon hardware with uncommon OSs (which expose bugs that are affected by endianness, or Linuxisms, or blindly assuming a string is ASCII, or that a file stays put while you use it).

I’m interested in oxide, but I feel like you could level the same criticism. The startup cost of using azure or aws is almost nothing. The cost to use oxide is 6 figures?

I feel like they need to run a public cloud just to let people tinker with lightweight stuff and scale up to owning the thing.

That said, I’m also a moron about certain things, and this might be a moronic take.

> but I feel like you could level the same criticism.

Exactly. Oxide builds machines for the few companies that won't go with Azure or AWS, or that got so big Azure and AWS are no longer competitive (and it takes A LOT to be in that space, because pricing is ridiculously flexible). This is a niche market.

The question I always ask is "why would I deploy my software on your platform?". The answer is, most of the time, I wouldn't. I don't want to play platform bingo with company money.

> Why would someone who is developing their software on an x86 box with Linux care about ... Solaris?

There was a time when ZFS would have been a good answer for this. Of course, now it's available on FreeBSD and Linux.

At one point also there was zones, but again, containerization is pretty standard elsewhere now.

I guess also if you go further back, like the Linux 2.6 era, which is close to when Solaris was open sourced ... the 2.6 release involved a concerted effort to improve SMP support. So maybe you'd be interested more in commercial Unix in the 2.4 era, for better SMP. But again, Linux surpassed this ~20 years ago.

And not overcommitting memory.

But Illumos is a real modern viable option over Linux (and *racle Solaris) for server hardware.

On the onboarding thing, Oracle Cloud didn't offer Solaris as an OS option last time I checked. And, of course, they never offered SPARC because abandoning it was one of the first moves. IIRC, IBM Cloud also doesn't offer Linux on POWER (but they do offer AIX and IBMi, as well as z/OS - and Linux - on s390x). Not that long ago I tried to convince VMSI to make a deal with cloud providers and allow OpenVMS to be as easy as any other OS on amd64.

I mean, flashback to 2010 ... zones, dtrace, smf, iscsi and zfs were very well integrated together and lightyears beyond what was available in the Linux space at the time.

Zones were lightweight, more akin to the Linux vserver project or lxc. You could make a zone on its own zfs filesystem, clone the zone (which creates a zfs clone), launch the clone, run a throw-away task, tear the zone down which also discards the zfs snapshot+clone. It was quick and cheap but also half a decade before Docker was released or popularized.

zfs integrated into other parts of the system just as well. eg: iSCSI volumes backed by a zpool and export properties configured in zfs. All of these technologies were built with the idea of being "self-healing." Meanwhile, Linux has a disparate iSCSI daemon, lvm+ext4/reiserfs, initd, and probably 20 different tools to learn if you want to grab metrics across the stack like dtrace on Solaris was capable of.

The out of band management was amazing too. Yes, some x86 hardware had ilom but like everything else in the space, it's bolted on and not truly integrated.

Sun made really nice stuff that outpaced Linux in a lot of ways. The ecosystem came from a time of competing BSDs and looked for paying customers for the engineering marvel they had created. They were used to customers figuring out how to use Unix, and the Linux crowd at the time still fit that rubric. The OS was not optimized for low-latency terminal interaction and thus "felt slow" (aka: Slowaris) but a well tuned DB on Sparc really cooked.

Finally, I went to a few Sun events and had Sun reps come and look at what we were doing. They were definitely happy to help with any kind of outreach/onboarding we needed. The issue was none of "onboarding" but was a lot of "Linux is a movement." In early times, Linux was an anti-corporate movement and some of that energy carried through to the 2010s. It's sadly ironic because Sun itself has roots in open standards and an anti-establishment mentality.

> zones, dtrace, smf, iscsi and zfs were very well integrated together and lightyears beyond what was available in the Linux space at the time.

True, but did you need that? These are all high-end (therefore low-volume) server stuff. I loved that, and their high-end systems with dozens of SPARCs, but I had one customer who had one, and everyone in my company knew they made a terrible decision - they needed a web server, and you could do more with a rack of Dell boxes for a fraction of the Ultra Enterprise [very large number] price tag. They also decided they should run an enterprise application server (they went with Dynamo) instead of Tomcat, so, again, they made a stack (maybe a directed acyclic graph) of bad decisions. I think I facepalmed so much that is the point my hair started falling.

We used it all to great success ... along with our Linux hosts. We had a stack of T1's and eventually a few thumpers (x4500's) which we ended up running a variant of OpenSolaris on. There was also some bigger iron that was humming along on Solaris 8 which provided a very stable environment (until I fat-fingered a command one day.)

Later on, we even ran an ipfilter based router from a T1 on OpenSolaris for decent IPv6 connectivity with link-aggregation+vlans when our Cisco 6509 setup was found to be inadequate for the task.

I think you have to keep in mind how IT contracts and purchase decisions are made in large enterprises. You will almost never have an on-the-ground engineer making those decisions. CTOs collect requirements from other high-level managers who collect requirements from other managers and eventually a final list of checkboxes bubble up to the CTO. The CTO evaluates the asks and comes up with their own checklist of features they are looking for then go shopping.

Solution providers then try to check as many boxes as they can on the list. It doesn't have to make sense; you just want to check the box. When a decision is made, the chosen solution gets to the individual engineers to "figure it out". There is also a considerable amount of CYA in all of these decisions. You never want a project to get delayed of not implemented because you as a CTO forgot to check a box. The engineers using a product could decide that the box check doesn't work for them and they can then workaround it, but management (and the solution provider) get to CYA based on whether a box is checked or not.

My favorite flavor of this is when things are lost in translation, and a box gets accidently checked without understanding the actual requirement. Then it suddenly becomes a de-facto feature request because "the box was already checked".

Back in 2010, Linux in fact had Zones: It was called OpenVZ, and by early 2011 a bunch of tiny web hosting providers were giving people root on OpenVZ Linux virtual servers for $15 a year. I still have two KVM Linux virtual servers which cost me only about $40 a year.

I used OpenVZ to turn a decommissioned IBM desktop (which I asked corporate IT to fill with memory and disks from the other identical machines) into a departmental development server. It was on this machine we tested the scripts that migrated half a million blogs from a proprietary tool into WordPress.

Years later, the machine was still chugging around on top of that floor's networking rack. Someone added a PostIt with "Do not turn this off".

But I have to say OpenVZ didn't do all the tricks one could do with Zones, and Zones combined with Crossbow, were able to test a huge number of networking scenarios to see how things would break.

Solaris x86 launched in 1993. I had one on my desk at work in early 1997, running Common Desktop Environment.

Even back then, the CTO of our startup said Sun had missed the boat on dominating x86 Unix. They could have had a larger role in x86 Unix world if they had wanted to. It was definitely a misstep for Sun.

Having said that, throughout the 1990s Sun was amazing. They were even good right up to the Oracle purchase, although by that time RHEL on HP (or Dell) servers was eating their lunch.

> They could have had a larger role in x86 Unix world

They were always a hardware provider. If they could have offered credible desktops at PC prices, they could have made a serious dent in the low-end server (one step up from desktops), which is an essential stepping stone for securing midrange and above.

This. Sun behaved like it had vendor lock-in. Who wants a vendor like that?!

As much as this resonates with me it smacks a bit too much of an Engineering vs Sales fight. Engineering blaming Sales for not selling, and Sales... where is the voice of Sales? By 2005 Sun's margins on hardware sales had to be under vicious attack from Dell and all the old incumbents. Google and Amazon were ushering in the era of commodified compute and soon offering it on demand on the cloud. Proprietary hardware platforms were under the most vigorous multi-front assault since the inception of computing.

Meanwhile I have to imagine Sun, like IBM and everyone else at the time, was noticing what incredible margins you get from software services. No factories or fabs. No supply chain logistics. Sun's proprietary hardware business should have been dying (or at least radically shifting: a product/engineering problem, not a sales one) by all market indications of the time.

So if I was a sales person and got a call from a startup for a colo's worth of machines... I probably don't have much incentive to pick up. The startup will probably fail, as most do, so the opportunity to build a relationship and sell higher margin services is probably nil. Startups hate paying for that stuff anyway.

I have incredible respect for Bryan Cantrill. He obviously knows far more about this situation and business than I do, so he's almost definitely more correct than I am...

However I would ask readers to at least be curious why sales didn't pick up the phone. Were they "bored?" Or was it a rational choice and much deeper problems with Sun's business model were the cause of their demise?

I feel like Sun's main problem was that that era was pretty much the steepest part of the Intel S curve as far as chip performance goes, and it was outpacing the older chips on fab progress alone. I'm pretty sure had something like TSMC been around then at current strength, and Sun fabbed their excellent designs there, we'd have a mirror of what Apple is doing but in server space.

Suns designs were not excellent. In fact their history with CPU making is pretty damn terrible. The made the wrong choice almost the whole time.

They got it right initially, making Solaris with gate-array and that was a big success. Small company got RISC chip out fast and it beat what was out-there.

Then they went all in on CMOS-Bipolar chip, that was massively late, massively expensive. The completely lost the plot and were not competitive in the early 90s. Thankfully they had the software buy in from costumers, and did some good stuff otherwise (they also did the disastrous Solaris transition) but they overcame all that.

Then they did a bit better with UltraSPARC in 1995, they were still not top of the line, getting easily crushed by Alpha and others. But it was 64 bit and that helped them long term. Nowhere near 'excellent' for the time period. More like, good enough. Then they rolled on from there, but were never anywhere close to Alpha and others until around 2000.

They made all the mistakes you can make in the 90s, going heavy into Gallium Arsenide that was a disaster. Then they went heavy on VLIW technology in another disaster.

Then they completely lost the plot in the early 2000s, and eventually pretty much gave up completely and switched to marketing T1 chips and 'threw-put computing' because they couldn't produce competitive chips on single thread performance.

In fact they did switch from Texas Instruments to TSMC in that time period. You can read about that in 'Life Under the Sun: My 20-Year Journey at Sun Microsystems'. Don't take everything in that book at face value, its very much putting a positive spin on things, but it tells some of those stories.

I don't know what Sun's strategy was in the 2000s, but doing all of the R&D to develop exotic new hardware and then focusing the sales force on software seems like they're getting the worst of both worlds.

Sure, I'm not saying that IBM's switch to services is some brilliant panacea for all proprietary hardware makers, just citing it as one of the market changes at the time that Sun seemed unprepared for.

What's interesting is that the other RISC outfit at the time, little old Acorn in the UK, did manage to adapt their proprietary chip business to the future of compute and now we all use many many ARM processors every day.

So clearly there was still a hardware route available, just again: a huge product/engineering shift.

It didn't hurt that ARM was spun out entirely. The computer side of Acorn was wound up in 1998/9, and then the remnant of that went onto DSL boxes, exiting by getting picked up by Broadcom for £366 million.

Well, definitely read Jason's blog entry that I linked to[0], which gets into the structural problems. To be clear, there were some extraordinary sales folks at Sun (as was said to me when I first came to Sun: "Remember that our sales folks are so good that they sold Solaris 2.3 on Viking!"), and I always personally got along very well with them. I was happy to be put in front of customers, and they were happy to use me -- and some of my fondest memories were with sales folks in some of the geographies which were particularly strong (shout out to Sun Canada, Sun Australia, and to the Wall Street and Itasca offices in the US).

So this isn't about the people at all (they will express the same frustration!) but about leadership that wasn't interested in running a business. I do want to stop short of overly personalizing it, but the simple truth is: Scott visited customers where they lived -- and Jonathan more or less didn't.

[0] https://fullhoffman.com/2006/03/20/the-sun-doesnt-shine-on-m...

Ah, I love this framing of "visiting customers where they live." Definitely gets the bad taste of an eng-v-sales spat out of my mouth. Thanks for the details!

> I probably don't have much incentive to pick up.

This is what Dell got right - for their sales team, this was an easy process - the product line was simple and easy to customise. Their sales reps wouldn't spend much time creating the proposals and could spend the remaining time building relationships with a lot more customers, some of which wouldn't fail.

> curious why sales didn't pick up the phone. Were they "bored?"

Unless you create incentives for bringing new customers, they'll leave the new names for last.

I worked on enterprise software around the turn of the century. There was no database/os combo more bullet proof than Oracle on Solaris. Solaris was a great OS but the speed and ferocity that Linux killed Sun was something I will never forget.

I went to the Menlo Park offices to see a demo of their 64-cpu (I think) system at the time but it didn’t take long for Linux on intel killed the entire market.

I was once SUN Microsystems Campus Ambassador at Oxford University and our first lecture was about dtrace! The guy from SUN was blown away by attendance so the higher ups wanted to do more & more events in bigger rooms. But as corporate weeks passed, I started telling them to postpone because everyone was entering the exam sessions. Corporate of course did not listen. Long story short, SUN sent 3 experts but we couldn’t get the crowds and the main lecture room was embarrassingly empty.

I worked at Sun from 1995 to 2004. My take is that Sun had major structural problems all along, but as long as money streamed in from the tech bubble, these issues could be ignored. When the tech bubble ended, it was too late to fix the problems.

One big problem was that there was no cooperation inside Sun. Groups in Sun kind of viewed HP as a competitor, kind of viewed SGI as a competitor, but the real competitor to be destroyed was that other group in Sun. The leaders of the project I worked on spent most of their time in political battles, trying to acquire or outmaneuver the other teams working on similar projects.

Another problem was that the main parts of Sun had conflicting strategies. The Solaris/SunSoft division wanted to run on SPARC, x86, and Power PC for the largest market. The SPARC division, of course, wanted none of that. The hardware division wanted to make expensive servers, but the other teams saw cheaper hardware as the right direction. The market ended up moving to cheap rack-mounted Linux x86 servers, so nobody at Sun won in the end.

Right before they fell face-first into the grave, they did finally ship the v20z, which was a completely reasonable way to run Solaris x86. Its management board ran Linux on PowerPC, for irony purposes.

Haha, that's a fun fact. (Solaris+x86)+(Linux+PowerPC), what a setup.

There is a simple rule they forgot to follow: never make it difficult for customers to give you money. They had excellent hardware and software but that wasn’t enough to save them.

Sun was just never really setup to sell lots of small servers. You have different pipeline when your goal is to sell million dollar E10K servers.

I got to see a server installed via crane because they couldn't go up in that building's elevator.

As an outsider at the time, when Linux was taking off, there seemed to be a lot of people asking why they wouldn't Open Source Solaris.

It seemed to me like they couldn't decide whether they were a hardware company or a software company.

Mind you, I was young at the time so possibly didn't have the best understanding of the situation. Seems like they left the decision too late though.

Dismissing Linux as a hobbiest OS definitely turned out badly.

I remember the attitude was that solaris was for serious professionals and had the highest calibre of code. For the most part it seemed true and these were solid workhorses. But, i did end up finding concurrency bugs when they introduced their multi-core integer computing behemoth.

>Dismissing Linux as a hobbiest OS definitely turned out badly.

That actually made me laugh. Not because it's untrue, but because it reminded me of this:

   One of the questions that comes up all the time is: How 
   enthusiastic is our support for UNIX?

   Unix was written on our machines and for our machines 
   many years ago. Today, much of UNIX being done is done on 
   our machines. Ten percent of our VAXs are going for UNIX 
   use. UNIX is a simple language, easy to understand, easy 
   to get started with. It’s great for students, great for 
   somewhat casual users, and it’s great for interchanging 
   programs between different machines. And so, because of 
   its popularity in these markets, we support it. We have 
   good UNIX on VAX and good UNIX on PDP-11s.

   It is our belief, however, that serious professional 
   users will run out of things they can do with UNIX. 
   They’ll want a real system and will end up doing VMS when 
   they get to be serious about programming.

   With UNIX, if you’re looking for something, you can 
   easily and quickly check that small manual and find out 
   that it’s not there. With VMS, no matter what you look 
   for — it’s literally a five-foot shelf of documentation — 
   if you look long enough it’s there. That’s the difference 
   — the beauty of UNIX is it’s simple; and the beauty of 
   VMS is that it’s all there.

   — Ken Olsen, president of DEC, DECWORLD Vol. 8 No. 5, 1984

Ok, that is funny! Though interesting to consider. Why did no-one go with a free OS that was VMS based in the same way?

It's basically does Linux win or why not BSD? Never what about OpenVMS.

Because history[0][1][2][3]. The timelines (and license, in the case of VMS/OpenVMS -- even to this day) didn't make it inevitable, but certainly paved the way for Linux (although one or more of the BSDs could have filled that niche instead, had a fully unencumbered[5][PDF] BSD become available sooner) to have the level of adoption it ended up having.

VMS has always been proprietary, despite the name, and is still an expensive[4] option for commercial use

[0] https://en.wikipedia.org/wiki/History_of_the_Berkeley_Softwa...

[1] https://en.wikipedia.org/wiki/Minix

[2] https://en.wikipedia.org/wiki/History_of_Linux

[3] https://en.wikipedia.org/wiki/OpenVMS

[4] https://vmssoftware.com/products/licenses/

[5] https://dn721902.ca.archive.org/0/items/att_unix_licenses_19...

>Ok, that is funny! Though interesting to consider. Why did no-one go with a free OS that was VMS based in the same way?

>It's basically does Linux win or why not BSD? Never what about OpenVMS.

While my original reply was accurate, it could have, more concisely, read:

   Licensing[0][1][2][3][4][5]

I mean Olsen was kind of right. Most VAX sold didn't run Unix and VMS and VAX were incredibly successful. Unix at that time was successful on workstations more then servers.

And by the time Unix became successful it was as complex arguably VMS was at the time.

DEC didn't fail because they supported VMS, in fact VMS was great costumer lock in for them and its still made money for HP despite being developed in the late 70s.

And in terms of clustering, Unix has never matched VMS.

DEC didn't fail because of VMS. Their big failure was not to make a fast RISC workstation that ran VMS early enough. And then in then in the late 80s not switching to RISC fast enough with VMS.

So I think he had a point, most serious banks and insurances did run VMS and paid lots of money for it for the next 20 years. VMS was not the reason DEC ran into issues. Their complete management of first personal systems, then workstations, then mainframes, then RISC servers is what destroyed them.

>I mean Olsen was kind of right. Most VAX sold didn't run Unix and VMS and VAX were incredibly successful. Unix at that time was successful on workstations more then servers.

>DEC didn't fail because they supported VMS, in fact VMS was great costumer lock in for them and its still made money for HP despite being developed in the late 70s.

>And in terms of clustering, Unix has never matched VMS.

Absolutely. Even the filesystem was made for redundancy and, AFAIK, no one has implemented the automated file versioning available to VMS back in the 1970s.

I used VMS at several jobs and it was both rock solid and light years ahead of Unix back in the 80s and 90s.

It's only funny because of how things turned out -- with VMS falling by the wayside for a variety of reasons.

Most folks these days think UNIX is the dinosaur, ignoring the BSDs that are still used (not even including MacOS) for many purposes and while they never got the kind of reliability/redundancy that VMS (or AS/400, for that matter) enjoyed, Sun (SunOS/Solaris), HP (HP/UX) and DEC (Ultrix) did provide levels of reliability still unheard of in linux.

When I first saw that Olsen quote (early '90s) I thought it was funny because Unix had come pretty far since 1984 (when that quote was published).

I thought of it because the comment[0] to which I responded reminded me of Olsen's quote when they pointed a finger at Sun for taking the attitude that Linux was a hobbiest[sic] OS.

Which wasn't all that wrong either. Given that MINIX was the model for Linux and MINIX definitely was a hobbyist/proof-of-concept OS, not something that was actually useful.

My thought was mostly that "times change, people don't."

[0] https://news.ycombinator.com/item?id=49790242

I think it worked out for the best. That said if we had Linus implementing LVMS instead of Linux history might not be that different.

I think one serious issue was that they took way long to realize portability.

They had rough group implement MICA OS that was supposed to be partially compatible. But the dropped MICA and PRISM and instead adopted MIPS and Ultrix. But then they never bothered to port VMS onto MIPS and their workstation line.

Then they mismanaged their whole VAX line and massive lost out to the improving Unix offerings, partly for performance and partly for 'openness' reason.

I think if they were smart they would either have gone 'all-in' on MICA and make it the future of both Unix and VMS. Or simply support both Unix and VMS on all of their platform. They were big enough that this wasn't some incredibly complex task.

They ported VMS to Alpha, but that was a 64bit machine that most people didn't need. Meaning they lost in the lower spec server spaces where Sun and HP were selling tons of Unix servers.

Had they ported VMS to MIPS and also had sold lower spec server with all these features, VMS might not have become so niche.

Personally I really believe that their complete mishandling of RISC, despite having arguably the best chip design team in the industry to be the reason for much of their failure.

> Linux was a hobbiest[sic] OS.

Long time since I've been sic'd! Ok, got it wrong but at least you know my comments aren't llm'd...

As someone that buys hardware today, all the hardware companies are now in the "we don't want to do business with you" territory.

It's full RRP for everything less than 1000 units. If you want a 100 unit refresh you are better off going to your local corner shop for price and service.

Part of my maturing as I've gotten older is realizing how much business success actually comes from Sales, BizzDev, Product, etc. Engineering is great, but if you don't have people actually getting things shipped, getting customers, and talking with customers, you will eventually fail. Sure sometimes some internet companies find a money printer and get around this, but I think they are the exceptions to the rule. Sun having great tech, but having a shit sales channel, is not going to lead to success. Dell, small or large, they are going to get you someone on the phone and sell you a server.

Part of my maturing with getting older in addition to the above is that luck is a larger factor than most people are willing to admit. So I'm with you that GTM is just as important as engineering, but execution on all fronts is what tilts the luck factor. And with luck you get exceptions which is why you can get companies that seem to succeed despite themselves.

Gwern has a great article [0] about commoditizing your complements as a strategy to both boost demand for your product and keep competitors at bay. (this was originally an idea put forth by Joel Spolsky).

He points out that Sun, a hardware company, was smart to work on open source window managers to make it easier to use their hardware.

In turn, they were dumb to create an open source language (Java) that could run on any hardware. This was a strange move as it dramatically reduced the need for Sun's specific machines.

Highly recommend the article as it has lots of other examples of this.

0 - https://gwern.net/complement

Although I am fairly well aware of the vendors of these full systems like SGI and Sun had with IRIX and Solaris, I'm often disappointed I never got to experience them as they were before my time. I've seen photographs of well preserved personal collections of their machines in users' homes, and they look wonderful in a way you look at a specific kind of classic car (that surely has odd quirks) and there's a resonance making you feel and know it will drive and handle joyfully.

I've been amazed in the past looking at the Wikipedia article on Bill Joy, and all I have to say right now as a UNIX philosophy leaning Linux and BSD user is: thank you for NFS.

HN lift of James Gosling's story about the radioactive UltraSparc II

https://news.ycombinator.com/item?id=10638929

I was a systems engineer aka sales engineer aka technical account manager for Sun and I worked evenings and fought like hell to do the best for customers, having previously been a Sun customer.

Perhaps my story will explain what others experienced. I flew out to visit a customer on my first day on the job with the most capable sales rep in the world. Well, we did great, but eventually she left, and I was working with pinch-hitter sales reps from SoCal, doing roughly twice my previous workload, and holding the fort well.

It was not easy, so when there was a division meeting in Santa Barbara, I didn't feel like going, but my wife booked a flight and a car, on the spot, and I ended up driving the 3 or 4 hours through LA to the meeting, and got an SE of the quarter award.

My sales rep's replacement was a kid with no product understanding, and who hung around his boss, learning the ropes, a lot of 880 traffic from my home and home office. We didn't coordinate sales calls and brought duplicate literature and presentations. He did manage to get one customer to go ballistic.

During all this time, even as a techie, I was bamboozled how Sun actually sold as much as it did. The sales side of the fence looked to me, as a newbie there, like a mess, so I started reading "MBA" books and that helped me personally, but no greater understanding of my organization. But what the hell did I know, being on the front lines.

I was considering shifting home base to Santa Clara but left for a startup rather than be part of a team with a minor league talent and a very large territory.

That was before our market went to hell, and before Oracle.

A shame, but I gave the job 200% or more. And wear the Java jacket proudly.

I bought it at a thrift store for real cheap.

Having read a lot of these things from ex-Sun employees, I dearly want to read one with the topic my department is the one that fucked up Sun. I don't think I have seen a topic like that yet.

I actually haven't read a ton of these, so would love to be pointed to what you have found. But yes, everyone will be biased, and I am too. I think that the organization that I was in fucked up plenty (when I joined the company in 1996, SunSoft was led by truly one of the most incompetent executives I have ever encountered, a bumbling oaf that Sun kept putting in charge of different business units, letting him asphyxiate them one by one), but the fact that everyone also sees something else wrong probably tells you a few things: everyone at Sun earnestly wanted the company to succeed; Sun did a bunch of stuff right; Sun did a bunch of other stuff wrong.

Ultimately, the leadership of the company needs to bear the responsibility for the outcome -- and I think it's pretty telling that Sun's executive leadership basically went on to do more or less nothing after Sun. I loved Sun -- but it was a breeding ground for engineers, not executive leadership.

I'm reluctant to call anyone out. I liked Sun a lot, as well as the people I've encountered who worked there. There was a thread between a couple of ex-Sun guys here on hn years ago - I can't find it right now - which made me feel there was a humorous and very human pattern in Sun postmortem comments: "man, that other team really killed Sun, we were doomed after that thing they did." I was pretty curious what the people on that other team (the SPARC microprocessor designers, in the case of that comment thread) might have said in their own defense, where they might have spread some of the blame, and so on.

(perhaps it doesn't do your rather full blog post justice to compare it to something considerably less complete like a comment thread)

> Ultimately, the leadership of the company needs to bear the responsibility for the outcome

I emphatically agree. Maybe it goes without saying but with Sun, multiple generations of leadership, I think.

You can read 'LIFE UNDER THE SUN: My 20-Year Journey at Sun Microsystems' if you want to know what the leader of SPARC said at the time. The book does a lot to sweet talk some of the issues, but also admits to them.

Well he became leader when it was clear that they were deep in the shit. Then he was ask if SPARC should just be killed of. He said know but said he would need 4-5 years to turn it around. And I would argue he didn't even if they made some waves with Sparc T1 chip.

Ultimately I would argue anybody reasonable would go back to conversation and say, we need to kill SPARC and switch to x86 as fast as possible.

Actually now that I have worked for 4 companies, I’d like to work for a Sun, even if I know that it would fail in a few years.

I seriously don't know what Sun could have done to survive - once Linux was stable, running Linux on commodity hardware was just a better solution than anything Sun could offer.

They should have seen commodity hardware coming and built cheaper hardware themselves. They could have. Other companies were making clone Spark machines for much less so it would have been possible.

sure, they shoulda woulda coulda, but isn't that the innovator's dilemma?

Yes. There were lots of other things they could have done.

Early Linux distros were very rough. Remember messing around with modelines in X11 configs?

Sun could've been the "Apple" of x86 Unix: it just works.

I'm willing to bet they couldn't have done that because of the mind-boggling array of 1990s UNIX standards Solaris seemed to support. By the mid 1990s it was clear that the (platform-independent) GNU command line tools were generally superior to what was on Solaris, but presumably they had to keep all the old fossils around to satisfy their long-standing supply / support contracts with industry, defence, and government.

That was my guess back then, and it's my guess now. Someone please correct me if I'm wrong and you know for certain why.

I'm not saying it would've been easy. They could've installed the GNU tools in a different path and left it up to the user to change their preference. They did something similar with putting the BSD tools in "/usr/ucb" (I may have that path wrong.)

that would have required them to swallow their pride, and admit GNU tools were in demand, which didn't fit the marketing narrative.

They could've also just built a real package manager, left it up to the community to add GNU tools. I remember the Solaris package situation being annoying, having to download crap off FTP and install manually. Or often build from source.

Solaris was pretty bare bones, out of the box. I spent days customizing it. Even early Linux distros, like Slackware, were in better shape.

https://en.wikipedia.org/wiki/OpenCSW was a thing, but yeah go off

I've never spent much time with Sun equipment, but the hardware and OS had features I haven't seen on commodity hardware with Linux. IIRC, Solaris could deal with an unrecoverable ECC error by killing the process that had the bad memory. And I think they had hot swap memory on some systems.

ZFS was pretty unrivaled for long term storage for a long time. Solaris zones were containers before they were cool. Dtrace is pretty neat. Etc.

Maybe they could have survived with their OpenSolaris push driving low end adoption and high end customers buying their hardware. Pretty sure they would have had to migrate to x86, but they were dabling in that.

Maybe make some low end commodity x86 servers. Sell enterprise a fully engineered big ass database server and a bunch of commodity web servers. Doesn't have to be exceptionally priced, just good enough to let customers have single vendor server purchasing instead of getting the big stuff from sun and the little stuff from dell or hp.

More systems consulting? Sun had great engineers, but you don't see too many war stories about them fixing stuff for customers (maybe they keep quiet though).

zfs + solaris zones were amazing

> IIRC, Solaris could deal with an unrecoverable ECC error by killing the process that had the bad memory. And I think they had hot swap memory on some systems.

Both of these are supported on Linux now. The kill-on-ECC is handled by hwpoison: https://www.kernel.org/doc/html/v5.1/vm/hwpoison.html and the hot-swappable RAM has been present for quite a bit longer.

I saw references to Linux support for hotswappable ram a long time ago, but I've yet to run into a commodity server that supports it. And honestly, I've yet to run a system that needed it nor did I have systems where are hard stop from an unrecoverable ECC error was a problem.

I'm not terribly surprised that Linux grew support for poisoning pages eventually (and I appreciate the link!), but I believe Solaris had memory retirement in Solaris 10 (2005), and Linux got page poisoning in 2009. If you were running workloads where it would be important, then Solaris was better for you at that time, unlike the claim from the poster above that

> once Linux was stable, running Linux on commodity hardware was just a better solution than anything Sun could offer.

I think only a curmudgeon would claim Linux wasn't stable in 2005. Although certainly the userland could use less churn. :P

Linux is not a monolith :)

There was (and still is) a bunch of niche Linux kernels. I remember reading about a team that used Xen to do triple-redundancy with voting for Linux. They virtualized _all_ the non-deterministic IO paths (including rdtsc) and observed the outgoing network packets, ensuring that they are completely identical. I think this was around the mid-2000-s timeframe.

But yeah, it was all super-niche. The consensus now is that you should design your systems to be fault-tolerant and self-recovering, rather than depending on perfect hardware functionality. And for everything else IBM still exists.

Exactly, I used desktop Sun machines and administered many very large Sun machines from 1997 through to 2010.

I saw the end coming for Sun when I had a dx2/66 at home running Linux in the late 90s. It was brilliant.

Sun clearly suffered some from being a bit too early to what would become cloud computing —- didn’t help that their tagline was “the network is the computer”, which IMO was a bit too obtuse, because I didn’t really understand what it meant (sounded like a violation of the 7-layer OSI model lol) until I saw actual cloud computing come about.

But as some sibling comments indicate they already had a lot of the software infra for distributed computing the way it eventually came to be done today, with SOA/microservices, service discovery, or serverless lambdas etc. via frameworks like EJB or JXTA. They were admittedly pretty cumbersome, like the contemporary equivalents COM/DCOM, and made the fundamental mistake of trying to abstract away the fallacies of distributed computing, but also solved most of the common problems involved.

Potentially they could have pivoted to monetizing that software infra even if it got deployed on arbitrary hardware, which may have tided them over until they could spin up their own cloud service, even if it was a fast follow to AWS. However Sun seemed committed to making their expensive servers their primary business model and relegated the software to “loss leader” complements.

If they had just looked at how services were being developed on Linux + commodity servers, they’d have seen they already had offerings in that space that could be monetized.

With the benefit of perfect hindsight, which is a bit silly?

Open source Solaris as early as possible.

Really compete with MIPS, ARM, Motorola, etc. in the embedded space. Don't even try to make it a huge financial win, just get the SPARC architecture and dev tools out there with good Linux support.

Consistently support Solaris x86 and frequently release new generations of Intel and AMD workstation-class hardware.

Partner with TSMC for SPARC production a lot earlier.

Since we're just having fun here: acquire Nvidia in 1999, at which time it was pretty obvious workstation graphics was going to be commodified, and Sun could have bought them with their pocket change.

That doesn't exist. No department is every completely at fault. No department has enough budget to sink a company alone. It is always a lot of departments that don't turn in expected results - often for reasons not in their control.

The fault is always upper management not doing their job. Even if one department really would be that bad (which again they are not), upper management allowed them to be that bad.

Forget the hardware, I feel Sun could of continued their life as the business AWS became.

Later on, when Schwartz was the CEO, they had a datacenter in a shipping container concept selling to management/IT folks. Delivering that infra via APIs to developers being the key differentiator. I'd love to hear Bryan's take since he was involved in the cloud space after he left.

I worked there right before they sold to Oracle for a bit—my impression was a lot of brilliant engineers but no unified product story.

when I was a student in the waning days of Sun, the SPARC/Solaris machines were impenetrable Big Iron guarded closely by the greybeards -- not to be touched by the likes of mere undergrads. Never really did get beyond noodling around with cast off gear from eBay, though I did get to enjoy a bit of it via the Sun DNA in SmartOS years later.

Our Sun rep served us well at an academic library. I had no problems provisioning a server with a nice storage array. When things fell apart at Sun our sales engineer from Sun wound up working for us.

I did get to sit in front of the consoles that served the whole school (via telnet) and even hard rebooted them a few times and I wasn't even in a techy major. Just had good relations with the head of school IT. That much exposure was enough to crave a similar computing experience and that's when I installed Linux at home right after college.

I remember we where a sunos/ hpux shop. I was working on a compatability layer that allowed our ada to call out to the underlying OS. You figured system V would make them the same, but no.. So many #IFDEFs.. Sun's where our display and console machines. SunOS (it was the early 2000s..) had some weird network quirks (of course the udp multicast bug our group discovered was in HPUX.) HPUX had a really cool real time environment (turn of interupts and away you go... crash? reboot required..)

Being a Unix shop on our project didn't stop them from creating a new timecard system that worked only on windows.... The solution, citirx. It was a difficult time for non x86 / windows machines.

At some point we got SunRays as light terminals. Those were pretty good I must say.

Plus they put the Control key in the right place...

I interned for Sun and then worked as an MTS in Sun Labs for a couple of years. I miss Sun; I think they were very much an engineer's company that was spoiled by two things: big success in the early workstation market, and the dumb luck of the dot com boom. Sun hardware was solid (even though they fell behind the curve because of mismanagement of a couple of CPU lines), and its kernel (Solaris) was one of the well-engineered kernels ever. While any business makes some bad business decisions from time to time, one thing that was fatal was a crippling enterprise focus that failed to understand the huge growth opportunity that OSS and Linux represented. It was growth in a direction they not only didn't understand, but refused to understand, study, or adapt to.

Sun's heyday was in the boom. The fish were jumping in the boat. So naturally they were building bigger and bigger boats.

There was always the one-off ideas that might have gone here or there, but that core server cow just seemed like an endless source of cash. Thus they neglected the workstation market and ironically, the market for anything bigger than one single server rack. They didn't understand horizontal scaling, and the rise of cheap-but-replaceable consumer hardware like how Google did things was alien to them. They poo-poo'ed Linux, they killed and then unkilled Solaris x86, and a number of other things.

I do miss Sun though. As far as engineering goes, they were a very serious company full of serious engineers. Basically the polar opposite of 10X tech bros and startup culture.

Oof, the killing and subsequent unkilling of Solaris x86 in 2002 brings back very bad memories -- Sun management at its worst. It also highlighted the relative power of Sun's engineering in that everyone in Solaris knew it was the wrong decision, and we more or less disobeyed orders: during that period (January 2002 to August 2002, when it was reversed), we didn't change our treatment of x86. (And in particular, breaking x86 was grounds for a putback to be backed out.)

When Solaris x86 was unkilled (and then became increasingly important as x86 eclipsed SPARC), there was damage done that I don't think we ever fully repaired.

Agreed. When I was in the labs (2007 - 2010), my workstation was an AMD with Solaris on it, with a modern window manager and all, with IntelliJ and a great development environment. I almost didn't know it was Linux. But by then the ship had long sailed.

> highlighted the relative power of Sun's engineering

This is one of the top reasons I loved and love Sun. Truth, engineering, had power.

I've never experienced this in any company since Sun.

Oral History of Mark Himelstein goes into that:

https://www.youtube.com/watch?v=-vDunup8v5M

He said he killed x86 but wanted to it only temporary, as some sort of political move around Itanium.

I worked at sun (sunsoft) right out of school near the peak. It was great. I was very excited to have all of the sources for sunos easily available to read.

Later, in grad school I went to work at a startup… google. For me it recaptured everything I liked about Sun. And had the same CEO.

It indeed was a fantastic place, doors nailed to the walls, trying out the newly fledged Mapreduce and Charlie's. Good times. Good times.

Great perspective to share, thanks.

> They didn't understand horizontal scaling

What of Jini, JavaSpaces / Linda, JXTA, "grid computing"?

Were they too early? Dismissed as (Bill Joy's) hobby projects?

At the time, I was very enthusiastic. Especiall grid computing. So much so that when cloud computing arrived, I couldn't recognize the sea change. Square peg, round hole.

We even POC'd some Jini support. Demo'd for hardware manufacturers, customers, our dealer channel. Customers loved the idea.

But like UPnP, Jini failed to get traction.

As for JXTA (peer-to-peer), although I didn't gave any skin in that gane, I really expected it to vecome the norm. eg My brother (for his ISP) POC'd video delivery in anticipation. But that got mooted pretty quick.

Arguably, AWS Lambda (et al) was is "dumb" grid (run anywhere in asandbox) and the OpenClaw agentic (madness) is the "evil" incarnation. (I'm aware of efforts like Emerald AI (et al) to make a "smart" grid.)

RE: JXTA, right around the turn of the century, it felt like there was an opportunity for a globe-spanning peer-to-peer application layer, based on content-addressable storage.

DHTs—Chord paper was 2001—started popping up. The big software vendors looked at the architectural (if not legal) success of Napster & the other P2P networks and were invested in finding legitimate applications. Open standards were seeing real adoption left and right.

But it didn’t happen. Maybe simultaneously too late in the Internet’s evolution and too early.

Too late because the big kids were involved. Especially Microsoft, who would never allow any standard they couldn’t EEE to emerge. Too early because the players like Google who later could muscle through core infrastructure standards weren’t there yet.

And now it’s likely too late, with mobile embedding a client-server model with the weight of 10B devices.

Back in the early 90s, I ran several procurements for university computer labs. We were under severe budget constraints, and, as a computer science department, we had constraints not normally found in such labs (for example, we needed to use certain compilers, so they had to support the workstation architectures). We wrote RFPs in accordance with university policies, and, while a number of potential bidders couldn't meet them, the companies in question all understood the constraints, and unsuccessful bidders were constructive, on the grounds of “consider us next time, ok?” All of them were like this, except one. The only time I have ever had someone threaten my job was the Sun Microsystems sales rep, after they lost a competition.

In it's heyday Sun shone very brightly indeed and was key to stopping a dismal Microsoft hegemony in the late 1990s.

In the end commoditisation eat it's lunch, just as with SGI, and they didn't manage to adapt in time.

A lesson for AI companies perhaps....

Here is my experience with Sun and why they failed in the 00s: Linux

The only way you could get people with Solaris experience was to hire people from colleges where students had access to expensive hard to access servers. This limited the number of people a company could hire to handle their Solaris servers.

I remember being told by the now forgotten snap.com—back when snap.com was a web portal business owned by NBC (these days it’s owned by Snapchat but is a completely different company)—to pound sand because I had Linux but not Solaris experience. There was a certain elitism among Solaris users at the time that Linux was a toy operating system. [1]

I already knew that wasn’t true; I remember, before the height of the dot-com wave, installing Linux on my desktop PC at work because the Sun servers we logged in to to run X applications were overloaded and difficult to access, so I just had a local instance of Slackware (and later on RedHat) so I could run X applications locally and just telnet in to the Sun servers, which was a good deal faster.

A few years after my unpleasant experience being interviewed by the NBC portal incarnation of snap.com, I saw that the company folded and went under—which didn’t surprise me because they weren’t being economical about the servers they were running. The company I was at was running a couple of Dell RedHat Linux servers, which kept us on the Internet cheaply and reliably.

It didn’t surprise me that Linux soon overtook Solaris and ate them for breakfast.

[1] Bryan Cantrill—the person who wrote the blog this thread is about—infamously said “Have you ever kissed a girl” to a Linux Kernel developer who explained why Linux was more efficient that Solaris on Sparc (and was easier to get support for); this is the prime example of the snobbishness Sun users had at the time.

[2] https://landley.net/history/mirror/linux/kissedagirl.html

Cantrill of course was wrong in saying what he said, but he was actually right about about the argument they were having.

I have long since accepted that this one is going to follow me to the grave, and I have (repeatedly?) expressed remorse over it,[0] but if you want to hear a longer discussion about this, Ryan Peterman asked me about this very directly on his podcast and we had a good conversation about it.[1]

[0] https://news.ycombinator.com/item?id=9041086

[1] https://www.youtube.com/watch?v=qhSL-5GtmQM#t=1h02m37s

I honestly think its a incredibly silly thing to bring up over and over. But I guess that's what it like to be in public. I did hear the podcast and checked the argument.

I was working in a UK financial blue chip (FTSE 100/high street bank) from 1999 to 2008 where I got my main Sun exposure.

I loved the Sun kit and Solaris. Touched everything from Sparc workstations to E10K/E15K. It felt like home!

A random selection of areas where they went wrong from my viewpoint as a junior to senior unix admin at the time..

Biggest of all - IBM did a complete number on them in my workplace. Hugely aggressive presence. We had a regular Sun PS person onsite. IBM dropped a whole bunch of people in. Sales, pre sales tech, anything we wanted. Completely undercut Sun and leveraged mainframe deals to push their p5 kit. Before we knew it there was a 'unix consolidation project' and I found myself grumpily using a HMC and bloody AIX. Millions in lost revenue. Went from a tiny IBM presence in a lovely multicultural Unix estate (HP-UX, Solaris, AIX, even Dynix) to bland banks of Power racks in the datacentres. A complete capitulation.

That whole "attributing mysterious system crashes and memory corruption in SPARC Enterprise servers to stray cosmic rays" thing. They handled this really badly. I got called out so often for this. An open goal for IBM. Sun was so expensive and yet we'd be having to report

They should have made more of an effort with their estate management software or made stuff free to use. They had such good ideas around patching etc but everything seemed to cost money. Our Sun estate was a real mess of patch levels. Our poor PS guy would be sent along and try to get jumpstart implemented but would say it'll cost ££££. IBM ate their lunch (even if their stuff wasn't as good, or ever really implemented properly in our shop). They had Dtrace and it was never used in our estate despite being free.

They were unfortunately too early on a bunch of things. Such good ideas around open source and things like technical blogs! But the culture was different, certainly in corporate UK at the time (I started an internal blog in the Unix team and people thought I was insane). They should have given away compilers and stuff. Everything seemed to cost money.

They could have aggressively supported Linux as something to differentiate them from IBM. The battles I had trying to get Linux in the door for anything, but when it did arrive it was running on Power. Their whole Solaris x86 thing was just confusing.

ZFS seemed to be fumbled. We spent a fortune on Veritas products. I did love Veritas filesystem and their clustering stuff. Sun could have gone for that market and somehow it never happened.

We had a similar company in Norway in the 1980ies. Norsk Data (literally means Norwegian Computers) made computers, a multi taskin operating, a word processor thar inspired MS Word, a relational database on the same level as Oracle, the firsr web server was made by Tim Berners-Lee on one of their computers. It all went down because the managers kept insisting that they were a hardware company. The software was supposed to help selling their hardware. They were not good at making hardware.

MS Word was a descendant of Bravo and Gypsy on the Xerox Alto, not ND-NOTIS. NOTIS is an interesting footnote in the history of software, but PARC's influence on early microcomputing is well-known and recognized.

[1] https://en.wikipedia.org/wiki/Xerox_Alto#Software

[2] https://en.wikipedia.org/wiki/Bravo_(editor)

[3] https://en.wikipedia.org/wiki/Gypsy_(software)

[4] https://en.wikipedia.org/wiki/ND-NOTIS

Berners-Lee made the first web server true but it was on a NeXT not Norsk Data

The good thing about Sun (when working at a corporate customer) was that they were very good at getting their distinguished tech people into give talks - Tim Bray, James Gosling etc.

Some of us say when SunOS stopped being BSD based and went SysV into Solaris, we knew the end was coming.

I actually appreciate many things post Solaris were net beneficial. The scripted install stuff presaged a lot of what emerged as puppet/chef/ansible/helm type processes. (this is pre YAML/JSON) -The disk/drive/segment labelling scheme has been completely normalised, the BSD device/partition scheme had limits.

And of course ZFS.

Solaris 2.4 and earlier was a little rough. I no longer remember the exact details, but 2.5.1 was the first release I felt comfortable running instead of SunOS 4.x.

I'm perceiving a lot of enthusiasts of the race to the bottom here. Yes, Dell and Linux could offer prices and convenience that undercut frontier hardware companies like Sun and SGI. But now what do we have? The loss is palpable to those of us who used to work with varied hardware competing to awe us, not to mention filling niches much more satisfactorily than one-size-fits-all.

I know OP has an intimately inside perspective, whereas what I know about Sun is only from what I read online as an admirer and developer on its platforms… but “gotten bored of the mechanics of running a business” does not match what seemed to be more about having gotten “too enterprise-y” or “too out of touch with the market” and maybe also “too hubristic.”

Having missed this era of computing growing up, I have a completely different view of Sun. I see Sun as this legendary old power that invented cool things like ZFS, zones, and lament that they sold themselves to Oracle. It shocks me to read about them making IBM-style mistakes.

I mean, they were both.

Wild that around that same time one of my fellow students at university managed to get a free trial of a Sun Thumper shipped to him. It arrived to our campus workplace on a pallet. Just to mess around with. No way was he going to actually purchase the roughly $70,000 machine.

I enjoyed this article because I've lived this story before and it's bemusing to be on the wrong side of a vendors distribution strategy.

But it was the "Steve from Dell" revelation at the end that absolutely killed me!

My only exposure to Sun was using EDA tools for chip design, and even those machines were replaced with Linux by the time I graduated. The stock price never recovered, unlike say AMD.

This article started series of intertwined blog post reading, and I love it. It's so sad knowing that all Sun blog is not there anymore, I enjoyed Jonathan Schwartz post back at the time.

First work computer was Sparc IPX, a brief dalliance with HP D and K series, then had various Ultra, and servers were all sorts including E10k then various SunFire, and the Fujitsu Prime Power.

They were quite fun.

But can confirm, buying Sun was PITA.

The 300+ comments here are a testament to the affection, respect, positive & negative feelings Sun employees had about it. Absolutely the best decade of my 30 year career in this industry!

In jist 5 minutes waiting to deboard my plane, I strike gold in a short blogpost to go about reading more about the relevant histories mentioned in this blog.

Me gusta

I wonder if bcantrill will ever get back into cloud hosting ... to revive his Joyent days (which he alludes to without naming directly in the post).

I mean in a way isn't that what Oxide is doing? Aren't they just providing you the hardware to do cloud hosting yourself on prem?

On-prem vs cloud though, is two very different things.

In the later, I don't have to worry about hardware/power/networking/etc at all.

How timely, I was just thinking about Sun after doing some office rearranging last week and running into a bunch of sun branded ethernet cables.

Sun couldn’t handle the cold. Obviously in terms of the dotcom bubble burst, inobviously in terms of the company’s character. The things people loved about Sun (giving Java and NFS away, treating engineers as the point of the company, McNealy's loyalty to his people) were exactly the things that kept it from doing what it needed to survive. Very warm, very caring.

Oracle expressed the opposite. Within a year or two Larry killed OpenSolaris, let the MySQL, Hudson and OpenOffice communities fork away, sued Google over Java, and watched Gosling and most of the engineers who embodied Sun walk out.

The part that rankles the most, and undermines many a retrospective I think, is that Larry the lawnmower turned out to be a better steward of Java & MySQL than Sun was. Coldbloodedness is a survival trait.

I am not sure if Java would have survived Oracle without OpenJDK being started well before the acquisition, or without IBM.

Since then, companies had to develop policies about installing JVM from anywhere but official java.com address, ban VirtualBox, and so on, because the lawnmower is lawnmowing.

And I do not really think Sun/Java is in anyway major income source for Oracle other than the form of providing integrated database appliances cheaper than previous deal with HP-UX on IA-64

Disruption. Digital getting killed is what prompted Christensen to write The Innovator's Dilemma.

While we're reminiscing, I never did understand why Sun paid a billion dollars for MySQL in 2008.

So far the best theory I've heard was that it was bait to make them tastier to IBM and Oracle - but even that seems kind of weak; had they really given up at that point? Does anyone have a better theory?

Yea he’s wrong. Plenty of people switched to dell cause of Linux and open source . In our case the switch was from alpha and vms

> all of these homage shirts are amazing

You can't just say that without sharing those too!

Brian, I know you lurk and post here but i'd love to see those designs make their way to the store so the general public can purchase them.

Heh, yeah, we're hearing that a lot. We'll find a way of getting these out to people, but we're still debating the best way to do that (running an online store isn't zero work -- but it's also not an unsolved problem!). Stay tuned!

Awesome. I'm not in a position at my company to move the needle much in terms of buying, but I would love to support you guys any way I can.

Very expensive and valuable information to come by, thanks for sharing.

I liked Sun Microsystems. And they were not that wrong because in 2009, Oracle acquire Sun for 7.4 billion$. Granted, Sun was perhaps more worth at that time; and most definitely before that but it is also not a total disaster either. Except, of course, that Sun died. And I do not like Oracle at all. It is a very different company. Like a slow behemoth - it keeps on bulldozering over but nobody is excited about it while it does so.

I think the big US mega-mega-corporations, while powerful and dominating, also became super-boring. Nobody mentions how epic Google allegedly should be, or is; in 2012 that was much more common. People fatigued from corporate propaganda. And now the AI slop propaganda - that one accelerates disinterest and decay.

I think Sun should probably have pushed more on its key technologies. Simplify java, simplify Solaris while pushing on it hard - who knows what could have happened. It is idle to want to talk about it now though.

Speaking of another Steven, the Dell Dude:

Things were going great at Dell until its wildly popular advertising campaign suddenly came tumbling down over an unfortunate indiscretion on the Lower East Side that surprised absolutely nobody...

https://edition.cnn.com/2003/LAW/02/10/deli.dude.arrest/

>'Dell Dude' arrested for marijuana possession

>Monday, February 10, 2003 Posted: 3:55 PM EST (2055 GMT)

>NEW YORK (CNN) -- Benjamin Curtis, better known as the "Dell Dude" from the computer company's television commercials, was arrested Sunday while he allegedly attempted to buy marijuana on Manhattan's Lower East Side.

Steve The Dell Dude Commercial Compilation (DUDE WE'RE GETTING A DELL!)

https://www.youtube.com/watch?v=oJxTHMygpDY

Where can one buy the Oxide t-shirt

What Borland got wrong

Solaris lack of a package manager and crappy patches where patches replaced things wholesale, caused us a lot of overtime, but hey, got me a bigger house! Thanks Sun! Oh btw their hardware was way ahead of their shit software, which wasn’t as bad as shittier IBM or Digital or HP

I still feel like we're catching up to SMF.

But yeah, the lack of package manager hurt a lot, and there were competing third-party package managers which had totally different pro's/con's and packages and were incompatible with each other... what a mess.

Compared to apt/yum it was kinda comical... but the first party software really was excellent otherwise.

Yes. The software really wasn't all that great. I played a lot with Sun gear and had SGI stuff as well, the polish of the SGI machines vs the 1980's vibe that the Sun gear gave off was on a completely different level. Sun was quality hardware but the software was really a time capsule of what Unix workstations had looked like in the past.

Not to mention the horrible installer. At that time, Debian and Red Hat installs were super-easy compared to Solaris. And Sun controlled their own hardware stack too!

Oh, I thought this was a critique of The Art of War by one of the author's buddies.

Love that t-shirt. Does it have the Meta logo on the back of it? /s

lol. at first i thought this is going to be about what Sun Tzu got wrong and i was ready to refute.

that right

Sun? Sun Microsystem?

Solaris was worse than Linux, and SPARC was worse than Intel. A lot worse.

Even ZFS was way better integrated with the Linux kernel even while Solaris was supposedly maintained.

Eh, depends when. In 2005, sure. Not so much in the 1990s

Yep. Solaris was the Unix for the 90's. I worked at a couple of early ISPs and users demanded Sun Solaris shell servers. At a couple of startups, we built everything on Solaris because Linux wasn't accepted in the enterprise yet.

By the early 2000's, 1) Linux was solid, why bother with Solaris? 2) ebay and other channels were flooded with used Sun hardware from failed dot-com companies anyway. No need to buy new.

I was asked to benchmark some Solaris/SPARC vs Linux/Intel hardware in around 1997, and the price-performance of the Linux gear was easily 3+ times better. There wasn't really any comparison, especially when you consider how you could buy white box PCs from a local shop, grab a Red Hat ISO for nothing, and have an installed Linux server in 24 hours, compared to weeks to get something more expensive and worse for the Sun option. Even if Sun had been more reliable, it wouldn't have mattered because you could buy 3x the PCs and keep two in a cupboard, or more likely just replace everything with more numerous and better performing Linux PCs which was what we did.

Assuming that the PC was actually supported.

I had to survive with 800x600 on a 1024x768 monitor for quite some time.

The paucity of screen real estate in those days. Now, a 4k ultra wide monitor is less than $2,000 and has so many pixels!

Not in 2000, at my employer back then, our Linux server was only good as MP3 storage exposed via Samba/NFS.

All development and production deployments was being done across Solaris, Aix and HP-UX in regards to UNIX flavours.

I had a similar experience. I forget the exact timing, but it was probably around 2002 - 2003 that Linux felt "good enough." I was at a startup that finally considered putting its "enterprise" stack on Linux.

Later in 2003, when I joined CERN, there were still Sun workstations being used, and I was an earlier user of Scientific Linux in 2004.

Afterwards Nokia Networks were still deploying into HP-UX, and the first big Linux project started around late 2005, to Red-Hat.

I worked at smaller companies that were more risk tolerant. At an earlier startup (late 90's), all the developers ran RedHat on Dells, but the actual production environment was Solaris. I remember going out to a customer site and deploying some massive Sun Enterprise setup. It probably cost a half million USD for the whole configuration. Multiple servers (Enterprise 450 and 250 I think, two of each), multiple storage boxes (StorEdge), Veritas filesystem software, some other Veritas HA system, several Cisco switches, some firewall brand that I forget. All this was connected to a fractional T1 (512kbit.) It never went live due to some contractual issue. All that money wasted.

At my employer in 1999 we were maintaining home-grown binary modification to the Solaris kernel so that TCP segment send and receive were not O(N^2) where N was the number of addresses on the interface :-/ It was, as far as I could tell, an operating system that nobody had ever tried to use before. For anything where we could avoid Sun we used FreeBSD. One of the nice things about the free Unixes of that time was that process and thread creation or destruction were orders of magnitude faster than on Sun. To me, Sun was obviously in a lower category than Linux/FreeBSD/NetBSD.

The "Slowaris" nickname was there for a reason.

If time stopped in 2000 Sun would still be relevant. However, time did not stop in 2000.

Well...

Around 1998-2000 my dad made a little business out of setting up linux servers on commodity hardware in my hometown. Primitive social networks, LAN provider servers, mail servers all worked just fine. Not without some involved convincing, and tinkering, and kernel patching but they did work.

One or two of the companies later became regional champions, running 100s of linux/x86/dell machines.

None of them would be able to afford a proper Sun server. Sun would never bother itself with these original tiny contracts.

It dont think Sun even stood a chance in this game. They couldnt even realize this happening!

The linux kernel didn't even gain SMP until 1996. Solaris was running circles around it both before and after that point. Solaris was vastly more mature and stable.

Of course, after that, Solaris just kept running in very expensive circles while linux went on to make steady progress.

And if nothing happens after 1996 then Linux would not have been better than Solaris.

it was called "Slow arse". This was because it was rather reluctant in handing out resources (memory fe). Having fought it, I remember the system APIs being really well defined and picky (which was good). At one point, the C compiler had some identity issues "am I 32 bit, or 64 bit?"

Reply on news.ycombinator.com