js-utils VS xbattbar3

https://github.com/uxtely/js-utils/tree/main/react-create-el...

ReactiveVar was my favorite part. I wrote a clone of it [1] ReactiveState. It’s a PubSub that binds to the ‘state’ of one or more React class components.

Also, I wrote a clone of their ‘match’ library, I call it type-check [2].

Lastly, I made something like their DDP for my app. [3]

In summary, I highly appreciate Meteor’s ideas. In a sense, my app is architected based on them.

Thank you MDG!

1. https://github.com/uxtely/js-utils/tree/main/reactive-state

2.

I just open sourced (a few hours ago) the way I build the static pages for the documentation, blog, and website of my product.

https://github.com/uxtely/js-utils/tree/main/static-pages-bu...

I depend on my battery monitoring tools every day (xbattbar[1] for X and wattbar[2] for Wayland), and each of those was written over about two days time.

However, the coolest thing would have to be the project I'm in the middle of now, but it requires some explanation. At Hackerspace.gent, the center of the lounge area is Bloembak[3], a 1x1m table with a 32x32 pixel display covering its surface. During a discussion at a local bar with its creator, I decided it would be absolutely brilliant to be able to run shaders on it. So in my spare time over the last week, I wrote an interpreter for SPIR-V shaders to check my understanding, and then over the course of about 2 days, I rewrote the entire thing to target LLVM. While it's not finished (I only implement ~2/3 of the opcodes in SPIR-V and 1/10 of GLSL.std.450), it's already sufficient to run quite a few shaders off shadertoy at a reasonable framerate.

[1] https://github.com/thequux/xbattbar3