I'm a new visitor to this site and want to express my appreciation to those who took the effort to make a destination where disappearing knowledge and resources can be rescued.
I'm one of those folks who had access to NeXT machines when they were released, and running the OS again in virtualization brings back memories.
-ray
So, what are you doing with it these days?
Was curious to see Sir Tim Berners-Lee's WorldWideWeb HTML editing app, so i was building it from source.
It does build, and runs, but his release was missing stylesheet files needed to completely stand it up.
After starting, found that there were some emulations that provide general flavour.
But it would be nicer to actually run it on the OS used.
BTW here is where it stands. With a little more work it could look proper...
https://github.com/cynthia/WorldWideWeb/issues/2
Hello Pomosapien: Have tried our NeXT 68K emulator?
http://www.nextcomputers.org/NeXTfiles/Software/Previous68Kemulator/ , if you need images of NeXTstep please let me know , it would be fun to update some of the existing browsers to add modern features as well Best regards Rob Blessin
Hello Rob! Thanks for the offer, if you have a disk image of 3.3 with working networking along with the previous.cfg and knowledge of which platform and which version of Previous worked, that could be helpful.
In fact, i am just starting to use Previous to finish the reincarnation of Sir Berners-Lee little app. But I need to get networking up to check the remote page fetch functions.
Ultimately it would be good to have a directly runnable WorldWideWeb app.
At this rate, i'm getting so nostalgic i may have to obtain a Cube...
Cheers, -ray
https://duckduckgo.com/?q=ray+haleblian&va=b&t=hr&ia=web
I can drop box you a download dowlink
Oh, for completeness -- networking was working in Previous, I just wasn't testing it correctly... :O
And re: modern browsing, of the few ideas flying about the one that uses an external proxy to render a modern page that an old browser can understand seems good - it tackles lack of up-to-date TLS, plus the complexity and resource cost of rendering HTML5/ECMAScript pages.