rosco_m68k VS wasmer

Nice! I’d be interested to see how it handles https://github.com/rosco-m68k/rosco_m68k , it’s a mixed software / hardware repo, with a lot of code in assembler and C (for an old platform). Might be a challenge?

Probably not exactly what you’re looking for (since you mention “outdated”) but there are similar projects with 16 and 32 bit architectures, e.g. https://github.com/rosco-m68k/rosco_m68k

(Disclosure: I’m the designer and lead developer on that project).

Maybe the rosco-m68k computer kit would be up your alley. If you want to stay in z80 land, there's the omega MSX2 clone but I don't see any kits, so you'd have to get the boards and parts yourself.

Hi. The 68000 is an "old school CPU", like the 6502 and has no programmable memory inside the chip itself. To operate a 68000 system there generally needs to be some external ROM and RAM chips (and the type can vary). However, the same as with Ben Eater's 6502 and 8-bit kits, the TL866-II will likely be useful to program EPROMs and GALs on a 68000 setup also (it sure has been on the 68000 single board computer I have been tinkering with recently).

I am working on a similar project Xosera, aimed at adding video to a 68000 era home-brew system (the rosco_m68k). It is basically all working and there is a prototype PCB made. I am just finalizing "blitter" unit design and hopefully I'll have room for some "Amiga style" audio.

This is awesome. I'd love to have upstream support in Wasmer ( https://wasmer.io )

WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.

Unfortunately cosmopolitan wouldn't work for dockerc. Cosmopolitan works as long as you only use it but container runtimes require additional features. Also containers contain arbitrary executables so not sure how that would work either...

As for WASM, this is already possible using container2wasm[0] and wasmer[1]'s ability to generate static binaries.

[0]: https://github.com/ktock/container2wasm

[1]: https://wasmer.io/

I could not find any guide how to add WASM container capability to Docker running on Colima. This guide provides a few Colima templates for exactly this, which adds WasmEdge, Wasmtime and Wasmer runtime types.

Just suggested as well Wasmer on Twitter! https://github.com/wasmerio/wasmer

Looking forward to seeing the results :)

The Biome team has been incredibly fast on solving the challenge and achieving 95% compatibility with Prettier [1]

Just as a note, as it was not mentioned in the article, Wasmer [2] also participated with a $2,500 bounty to compile Biome to WASIX [3], and it has been awesome to see how their team has been working to achieve this as well... hopefully we'll get Biome running in Wasmer soon!

Keep up the great work!!

[1] https://github.com/biomejs/biome/issues/720

[2] https://wasmer.io/

[3] https://wasix.org/

It's funny how WebAssembly can help overcome most of the issues mentioned on the blogpost (packaging, configuration, portability) if addressed properly.

That's the main reason Wasmer [1] was created :)

[1] https://wasmer.io

Thanks for the mention to Wasmer.

I'll put here a link in case is useful for future readers: https://wasmer.io/