v86 VS squoosh

> As a thought experiment, we're almost there! We could technically have `win95.img + bochs86vm.wasm + autorun.inf + msword.exe` wrapped in a "browser evaluator"

I looked into this and... holy crap! We are there. Not for modern programs quite yet, sure, but this is amazing. You can use Windows 2000 from your browser.

https://copy.sh/v86/?profile=windows2000

I think you are looking for Shadow.

https://shadow.goose.icu

Or just the whole kitchen sink. Why not?

http://copy.sh/v86/?profile=windows98

Also: https://github.com/copy/v86 - more productized browser x86 runtime, used by eg https://github.com/snaplet/postgres-wasm

Wonder if you could put all those databases in a Linux image and boot it using v86 [0], eliminating the need for a server.

[0] https://github.com/copy/v86

Trying it out in https://copy.sh/v86/?profile=kolibrios , it's also clearly a love letter to Windows 95 in particular. That could be an unstated goal here, create a very particular PC experience under very particular constraints. I don't know anything about the creator but it's very possible that this kind of work was actually their career in the 90s.

It's incredible how much work was done. Maybe this should be an internet curiosity like how TempleOS has become, though Terry's personality was a unique factor.

hmm, why would people still use VMWare? Isn't vbox open source, or even things such as https://copy.sh/v86/ would do most virtualization trick now days?

Oh, there are more OSes one can use at the parent page:

https://copy.sh/v86/

My highlights:

- First version of Windows (1.01)

- SerenityOS <3

- and even ReactOS

Squoosh: A webpage that allows you to quickly optimize images for your blog.

One of the most complete image compressor out there, squoosh.app by Google, uses web assembly for decoding/encoding images and it works pretty well.

First off you want to shrink your images. Every mb your page is the more it will hurt your score. I use https://squoosh.app/

https://squoosh.app/

Having a quick look at squoosh, it uses lossy compression of webp by default.

Size images appropriately (https://squoosh.app/ can be used for this). Ideally, the size of the image should be kept below 100 KB.

if your images a large file size, remove them from the page, reduce file size, and place new reduced file size images in their place - publish the site to bring the new pics live - clear your cache - go the page and test it (good tool to reduce image file size is Google Squoosh - https://squoosh.app/ )

I'm just exporting normally from Figma, but then using squoosh.app (browser based) to adjust quality/compression and even for making sure png files are optimized for prod.

Hey I see your friend made a clan, but this guy found a workaround here if you still need it. I just used https://squoosh.app/ to basically save a new copy of the image and that worked