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 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.
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.
I've made a UI editor for React that allows you to edit any element visually but commits changes right to your code the same way you'd do it with a code editor.
Whoa! It takes a lot of directness and a bit of self-deception to put it like that. :D
When I was studying, we would have nine guys for each one girl learning CS, and it was fairly hard for the girls to fit in terms of actually learning things. Some of them would show real interest for the subject, but they were being more or less alienated when it came to working on projects in groups.
The most surprising thing to me was that it's actually fun to use this search! I mean, I spent 10 minutes just throwing different kinds of questions at it, and I didn't even care if the answer was correct – it was just fun and curious to see what it answers.
My two favorite answers:
1. "what's the meaning of life?" — 42 (dah! what else could you expect)
2. "why is ukraine in africa?" — Ukraine is in Africa because it is a part of the African continent.
I don't think you can enforce a constraint on which nodes are supposed to have which edges, etc.
I'm curious: is there a reason why you're putting NoSQL and graph databases into the same bucket, other than them both having the aforementioned limitation?
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