But it had many of the core pillars e.g. remote home directories, remote/RPC applications. NeXT in particular with frameworks like EOF/PDO pushed for more network centric desktop applications.
It doesn't sound like much today but were pretty new concepts for GUI users.
The reason I mentioned it was that there was talk that the iMac was going to be potentially the first consumer-grade thin client.
The JavaStation ran JavaOS, not Solaris. Not sure about the Sun Rays.
To my knowledge, NeXT never supported a diskless config. (Or did they?? Did anyone work with that?)
Diskless may have been an option when NeXT software was detached from NeXT hardware, though.
https://wiki.preterhuman.net/NeXTcube_running_68030_and_6804...
I get what you're saying — I'm just remembering Jobs demoing how his NeXT user account was remote and any NeXT machine he sat down on and logged into suddenly became "his" computer.
That's the "thin" client I'm thinking of. But maybe that's just "client".
That’s something that thin clients also promise, but doesn’t require using thin clients.
Its claim to fame was bringing the term Architecture Astronaut into common parlance.
https://www.joelonsoftware.com/2008/05/01/architecture-astro...
In retrospect, it's quite funny in light of how webapps and Cloud evolved. As Spolsky predicted in 1998:
"between Microsoft and Google the starting salary for a smart CS grad is inching dangerously close to six figures and these smart kids, the cream of our universities, are working on hopeless and useless architecture astronomy because these companies are like cancers, driven to grow at all cost, even though they can’t think of a single useful thing to build for us"
"And the fact that customers never asked for this feature and none of the earlier versions really took off as huge platforms doesn’t stop him."
Go ahead, try and take away that feature now, see if any customers complain.
NeXT rendering engine was display postscript and they had a common set-up of rendering the DPS on a remote computer while logged in over a network. The overall set-up meant that all the data was at headquarters and users could login in from any location and have a local DPS rendering of the centralized user account.