Hey frontend devs. Are signals just a kind of event emitter?

@mauve no I mean “reactive signals”, it’s a trendy new front end pattern

@heapwolf Ha ha, are we going to get another wave of rxjs type hype? Personally I loved that era.

@mauve seems possible. I guess I’m going to have to code read an implementation of signals to find out if it’s just an event emitter, there are 100000 tuts on how to use them, and none of them say specifically how signals work 😅

@heapwolf @mauve let's go back to backbone apps with control flow via global pubsub 🙈

Follow

@naugtur @heapwolf LMAO. In all seriousness I've gone back to putting ID's everywhere and ".addEventListener" on buttons.

It's like the joy of simpler times. TBH I miss adding jquery and hoping for the best.

@mauve @heapwolf I recently wanted to make a PoC of an idea and I wrote my own minimal jQuery for the front and express router for the back. Zero dependencies, lots of joy. github.com/naugtur/timely-tuto

@naugtur @heapwolf Oh wow I love seeing WeakMap's being used in the wild. It's just so nice that they exist now specifically for nice stuff like this.

I like how straightforward the router declaration is. Just shove em in there and it handles the rest.

Ty for the link 🙇

@mauve @heapwolf it surprised me how little I needed to do to get convenience on top of default http module.

I remember my pal wrote a minimal react like renderer that didn't diff but flush everything and it was 1kb 🙂

Sign in to participate in the conversation
Mauvestodon

Escape ship from centralized social media run by Mauve.