Показали в одном чате как умельцы с помощью https://cheerpj.com затащили Minecraft и IntelliJ IDEA в браузер. Указываешь .jar, подключаешь либу и готово. Конечно же работает через #WASM.

И конечно же я попробовал затащить редактор #OpenStreetMap написанный на Java (JOSM). TLDR; Оно работает! [1] Но есть нюансы:

- Заявляется поддержка Java 8 и 11. На практике JOSM, собранный под Java 11 через него не запустить. То из недр Files.сreateTempFile вылетает что-то, то из библиотек. Удалось допатчить до отсутствия исключений, однако интерфейс так и не появился.

- Пришлось брать последнюю версию JOSM для Java 8 и черри-пикать критичные коммиты (слава Open Source за эту возможность).

- CORS. Если это важно, то либо отключать расширениями [2], либо настраивать их проксю. Прокся также нужна будет, если приложение ходит по UDP.

- Cheerpj — продукт коммерческий, но бесплатен для личного использования. Однако у них есть открытые проекты для запуска бинарей [3]

Если у вас завалялись Java-апплеты, то можете их воскресить :)

[1] https://github.com/deevroman/web-josm
[2] https://webextension.org/listing/access-control.html
[3] https://github.com/leaningtech

#wasm is magic

https://github.com/deevroman/web-josm

Cool, we're in the latest Golang Weekly!

#golang #tinygo #wasm #computerVision #openCV

https://golangweekly.com/issues/552

Another take on #wasm debugging, previous one was over-complicated 😅

I wanted a way to embed comments in generated WebAssembly code, to orient myself when stepping thru disasm'd code in the dev tools.

Turns out named globals is a handy trick for that!

1/x

Ok, so I’m now a few months into building a custom (almost from scratch) #Lua implementation for @silverbulletmd dubbed #SpaceLua (for reasons).

A few things that panned out really well, and a few surprises that I did not anticipate:

0. General recommendation: don’t do this. Don’t just implement a full programming language because you think it’s a good idea. I also told this myself. It didn’t work. It was a “I’ve don’t this stuff before, I can do it again” type of deal. I was mostly right. But don’t do this.

1. Initially I opted for a custom interpreter (implemented in TypeScript) because I wanted to expose asynchronous (promise based) JS APIs to Lua, and I didn’t see how to do that nicely with a #Wasm-compiled version of the official Lua interpreter. Also I felt that having full control of the running system would turn out to be valuable down the line (I was right on this one).

2. I got the parser part mostly free. I found an existing Lua grammar for the Lezer parser library that #SilverBullet uses. Had to add a few things and had some struggles. This part was pretty seamless with a few glitches here and there.

3. Implementing the core interpreter runtime was actually quite easy. Lua is a mostly simple and small language. Again, I’ve done this before so that helped. Writing good test suites makes this doable and AI helped a lot generating those test suites (because it knows Lua).

4. What I didn’t anticipate is the pain in implementing the full Lua API, especially the `string.*` one which has its own pattern matching language (similar but distinct from regular expressions), which honestly I could do without. But it’s there, and people want to use it, so I need a full implementation. Issues keep coming up, though.

In exactly one week from today I will be at GoMAD in Madrid, giving the first ever talk in Spanish about
@wasmvision ¡Vamos!

https://www.meetup.com/go-mad/events/307495616/

#golang #tinygo #webassembly #wasm #computerVision #openCV