The CPU emulator tries to be pretty accurate about timing, but the I/O is not throttled, so that might be unrealistically fast (depending on your Internet connection).
Author of the post/creator of the site here. To save everyone the click, NeXTStep 3.3 is probably the best release to try out: https://infinitemac.org/1994/NeXTSTEP%203.3 (it was the last release that ran well on the original NeXT hardware, OPENSTEP 4.0 and later were mostly focused on Intel support).
If you'd like to play the NeXT version of DOOM and explore a few other apps, they're in the "Infinite HD" drive (you can get to different drives by clicking on the computer icon in the Workspace file viewer).
Yep, that tracks. I used to have a NeXTCube on my desk and tried to hold on to it (and 3.3) for dear life, but sadly the research institute I was in at the time didn’t allow it. Thank you so much for grafting previous into your wonderful site, I’ve been having a blast with it on idle moments.
You can reduce the mouse speed a bit using Preferences.app.
The fundamental issue is that there’s two acceleration curves being applied (the guest OS’s and NeXTStep’s). I experimented with the unadjustedMovement option (https://developer.mozilla.org/en-US/docs/Web/API/Element/req...) but it didn’t seem to help (and if anything, made things feel even harder to control)
I love getting to play with these OSes that I never got to touch 20 years ago, so thanks for this! Now that you've got NeXTStep, have you considered Rhapsody?
Hey there, this is an off topic question but I recently picked up a Next computer (the slab) with a monitor. I am a complete newbie in this world and just getting my feet wet. Did the community ever find a solution to the 'dim monitor' issue? Thanks for this slick release.
That would be Project Builder and Interface Builder. Project Builder was kind of a graphical make tool and Interface Builder was the real star of the show, it was the graphical user interface builder. And there was Edit for source code editing.
There were sold as separate product, NeXTStep Developer that had all the development tools, but if you bought the education version of NeXTstep the developer tools came bundled.
One cool feature of Infinite Mac is missing from these, unfortunately. That is the clever virtual disk system and block by block fetching of the images over HTTP that allows for practically instant execution. Most people have internet connections that are at least as fast or even faster than the HDDs of 90s computers, so reading a remote disk allows for emulation that has no slower I/O than the real machines had.
One change that went into 1.36 is that you can no longer use an exit node while advertising one (https://github.com/tailscale/tailscale/issues/3569). The Mac UI was not updated for that in time, but the next release the menu items should be disabled correctly.
Can you sent a message to support@tailscale.com about this and include a bug report ID (option click on the Tailscale menu icon and choose Debug -> Bug Report…)?
What would you recommend? dlopen is only used when running in CLI mode (which is not super performance sensitive), but not making it slower than it needs to be would be good too.
You should link against the library directly. dyld’s optimizations are complex, especially when it comes to third party code, but by linking directly the system can cache some of the work.
upx is not used in the macOS build (we only mention it as a possibility in https://tailscale.com/kb/1207/small-tailscale/, which is for embedded systems), so I have no done any benchmarking with it.
There is a way to build an even smaller version of Tailscale for embedded systems, though there are some trade offs with regards to ease of use and security. https://tailscale.com/kb/1207/small-tailscale/ has more details.
Method described gets most of the win from UPX.
That's not applicable on openwrt as it already uses lzma on filesystem level. Switching to UPX would cause excessive ram usage as binary would be in anonymous memory and no longer be backed by filesystem pages.
