[0] https://www.usenix.org/legacy/publications/library/proceedin...
[0] https://www.usenix.org/legacy/publications/library/proceedin...
As a concrete example, the failure to add USB printing support killed SunRay at airline kiosks in the early 2000s. American Airlines was the first airline to adopt kiosk-based check-in; they were very hot on SunRay, but needed USB printing. When American found out that Sun had just gutted the team (including everyone responsible for USB support!), they (reluctantly!) used Windows-based PCs instead. Sun tried to put the group back together, but it was too late -- and every airline followed American's lead.
Could/would SunRay have been used for airline kiosks? There are reasons to believe that it would have -- and it was certainly a better technical fit than an entire Windows PC.
There were examples like this all over the place, not just with SunRay but at Sun more broadly; despite the terrific building blocks, Sun often lacked the patience and focus to add the polish needed for a real product. (Our frustration with Sun in this regard led us to start Fishworks in 2006.[0])
RIP SunRay -- and what could have been!
[0] https://bcantrill.dtrace.org/2008/11/10/fishworks-now-it-can...
Oracle did try to monetize SunRay but for whatever reason it didn't meet their profit threshold. It was fantastic technology and I'm almost certain I still have the dual monitor variation in my basement somewhere.
Occasionally you'd find one where the security was about as well executed as the function they were meant for and there was some fun to be had, but not much.
I find it hard to have much sympathy for SunRay. Their advantages were supposed to be price, but they were never cheap, and security, but that required hiring engineers that understand mainframe unix security, which management just didn't do.
Seems like a tricky problem but clearly at least some of it was solved given USB ports were on the machine
But I just realized the "USB printing support" stuff was maybe less about USB printers themselves and more about being able to have, say, 30 thin clients with 30 different printers hooked up but the application would know which printer was the right one (instead of showing 30 printers available, for example)