10 hours ago

In order to future-proof the Unsandboxed project I'm making the not very difficult (in fact, the very easy) decision to migrate our fork of TurboWarp's next compiler back to a much closer system.

This is in order to prevent future regressions.


For context, our compiler is based on the one TurboWarp currently uses, but it was forked from it before TurboWarp merged it. Once they merged it we were incompatible in some areas, and I saw no reason to switch.

Now that the one person who understood it is gone, and its relation to TurboWarp is much more nuanced again, there's nothing holding me back. I have much more faith in GarboMuffin to provide a compiler with 100% compatibility with Scratch, and I will sleep better at night knowing that our compiler is as close to upstream as possible.

Furthermore, I'm removing a lot of pointless and unused rewrites from the VM to try and minimise merge conflicts.

Unsandboxed Announcements
7


0 comments

Loading...

Next up

Ok nevermind my count was TOTALLY wrong, 1000 BLOCKS

Also HOLY CYBERSECURITY RISK, I'm SO glad this never happened!!!

Please give me feedback on groups btw, the auto-resizing was a nightmare. Finding a balance between what the user controls and when it snaps to the bounds of the blocks inside was not easy, and I'm still unsure.

An update has been released for Unsandboxed.

Full changelog is in the article.

An update has been released for Unsandboxed.

Full changelog is in the article.

How often do people use the right/bottom workspace scrollbars? I don't mean how often do people scroll or move the workspace's position, I mean specifically click and drag the actual scrollbars?

Something something "the only thing holding caine back is that he likes us"

Our extensions will be loaded and treated as built-in extensions from the VM, but from a separate repository. No URLs, just raw Unsandboxed extensions. In the true spirit of our name, and without the VM clutter.