I was wandering around the expo floor at PAX East last year when I noticed Earthion at the Limited Run demo arcade. I had a lot of fun playing it on the floor so I bought the full game on Steam. It's a quality shmup! For me the difficulty really spikes on stage 3 and that's where I got stuck, though I did make it to stage 4 once or twice. The initial release had some bullet visibility issues that were improved in subsequent updates. The default CRT filter is fun but I turned it off almost immediately for more visual clarity.
It's my favorite comedy of all time. It's been going for over 10 years with a lot of little spin offs along the way. For those that want to take the plunge you can watch the first first ten seasons, Oscar specials, Decker, etc. for free on YouTube. Use this playlist to watch everything in chronological order.
On one hand atproto has content-addressed storage and portable identity that AP still lacks (but could have!), on the other hand atproto is far more centralized. The data layer is decentralized but everything on top is effectively centralized. Phrases like "practical decentralization" and "credible exit" are used to describe this design.
I am excited by the prospect of booting Wasm binaries without any JS glue, but when I've looked at the documentation for the component model and WIT it says that resources are references passed using a borrow checking model. That would be a serious downgrade compared to the GC-managed reference passing I can do today with Wasm GC. Do you know if there are any plans to resolve this mismatch?
In my experience people are often disappointed by the shared-nothing architecture of the component model. I guess that shared-nothing architecture makes it impossible to properly share GC objects across component boundaries. But they can still be shared across core module boundaries.
A lot of the time I think you just won’t want to use multiple components. It’s nice to be able to compose them together, I guess, but in general it seems to me that a toolchain will typically just want to generate a single big component so that everything can interact without limits internally.
I'm building a new Wasm GC-based language and I'm trying to make as small as binaries as possible to target use cases like a module-per-UI-component, and strings are the biggest hinderance to that. Both for the code size and the slow JS interop.
I have a compiler flag to switch from wtf-8 and wtf-16 so if you compiler for your host you don't have to reencode strings. That means that strings in my language hide their byte representation, don't allow indexed access, and only have code point iterators.
reply