31–34 of 34 posts
I'm pretty uninformed on the subject, but I am interested to hear why an adjacency matrix is chosen over an adjacency list when it is sparse. My basic data structures and algorithms class would lead me to believe that an adjacency list would be better. Is this due to the nature of how the database is constructed?
Glad this was posted on HN because Roi's work is outstanding. I see there is a thread about the license here, you know my position. I think in short that: * It makes sense for MongoDB / Redis Labs to change licenses of what they produce if they want / need. * In the case however of the Redis core, it's BSD, no way it will be changed. But for modules produced by Redis Labs, it's their choice and there is something to…
Glad this was posted on HN because Roi's work is outstanding. I see there is a thread about the license here, you know my position. I think in short that: * It makes sense for MongoDB / Redis Labs to change licenses of what they produce if they want / need. * In the case however of the Redis core, it's BSD, no way it will be changed. But for modules produced by Redis Labs, it's their choice and there is something to…
> * I don't like the attempt at getting things like SSPL OSI approved. Why?
Just a warning that this is one of the modules that's licensed under the controversial "Apache 2.0 with Commons Clause" license.
This motivated me to reread the commons clause again. I remain so disappointed in the naming and positioning of it. If you want to sell commercial modules that is totaly fine, but Apache 2 with commons doesn’t jump off the page as an unfree license (which prima facia it is). Should be called the ‘free for personal use’ email us for pricing clause instead.
But this is a totally unfair characterization of the license, so they wouldn't call it this.