427 karma · joined March 3, 2011
https://github.com/indeyets https://thisalex.com/
Redis is still much more powerful: lists, sorted sets and bazillion of other data structures
As long as you consider developers of derived software to be your users — permissive makes most sense.
But if you consider end-users of software it’s definitely copyleft.
right?
This part was not obvious. In a lot of cases geodata is mostly stable and reads/searches dominate over appends. And that’s why we keep this in DB (usually postgis, yes).
So DuckDB is optimised for very different use case and it is not always obvious when it’s mentioned
1. it works on top of git — you keep using all the same infrastructure (GitHub, etc.) 2. in your local repositories you still have access to git-tools, as jj maintains git and its own states in sync.
After all of these months with jj I still find myself using GitUp when I need to review a long chain of commits or do some quick repo-archeology. And, from time to time, I even use Idea's merge tools because their "magic wand" saves a lot of time.
I mentioned this in the first part of series
Ferron is different.
Is that a choice or just something you didn’t work on yet?
yes. https://github.com/serde-rs/json
> Can you work well with a rust application that interacts with react?
can you write an API-server in Rust? sure. or what do you mean?
Creating stuff from scratch is not a fun experience
An expectation is that “wrongdoers” just do not bother to oppose and everything works faster.
Then there are corporate policies which make this weirder (like YouTube who says: “if people send too many dmca request towards you, we chose not to see you as a customer”. But this has nothing to do with law)
Fair question