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.
rbanffy · · focus · HN ↗
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).
nickpeterson · · focus · HN ↗
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.
rbanffy · · focus · HN ↗
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.