kirillrogovoy

While not 100% same thing, I've been a happy user of nanostores to manage state in vanilla JS.

It has `computed` too which works very similarly. On top of that, it has integrations with front-end frameworks such as React.

https://github.com/nanostores/nanostores

One interesting thing about learning Elixir and its (+Erlang) ecosystem after 5+ years of JS/TS is that half of the most popular libraries seemed abandoned.

However, when you look closer, turns out that most of them just finished the work within their scope, fixes all reproducible bugs, and there's just not much left to do.

If there's a JS dependency with the last commit in 2022, it probably won't even build. (I'm half-joking of course, but only half)

I like how this comment set me off spending the next hour reading and watching stuff on ADHD while the time passed like it was one minute.

Now I'm actually surprised to have returned back to this HN thread.

Meta ADHD.

Yes.

It'd have to ask you for the FS permissions again though since the active FS handle is stored in the IndexDB which of course is separate in incognito.

If you use Tailwind and React, you might like Impulse[1] (disclaimer: I made it and use it almost daily)

Not only does it provide means for visual editing (for Tailwind only), but it also saves all changes to your code.

Free and open source.

[1] https://impulse.dev/

I use https://github.com/karthink/gptel to talk to GPT in Emacs and, by extension, have a record of all my conversations (unless intentionally removed) as simple Org files in my single Org-Roam network.

Great job, Wix team!

If you'd like something more code/dev-oriented and open-source, check out https://impulse.dev/

> There's no such thing as "no architecture".

I kind of agree with it as an absolute statement, but I tend to use the word "architecture" rather relatively.

There's always _some_ structure to anything, yes. The question is how much is too much (or too little).

I think the world of open source would be a better, not worse, place if we had some usable bounty system at the level of issues/PRs.

And I say it both as a contributor, but also a consumer. Sometimes I'd be happy to throw $100 on top of some specific issue of a lib/app I use regularly to incentivize its resolution.

I wish this service didn't require repo owners to do anything before they see some actual bounty assigned to one of the issues. So, theoretically, I could go and assign a bounty to any repo on Github right now, and the owner (and maybe the public) would see it right away.