According to antirez, he understood the implications of licensing Redis as BSD: https://news.ycombinator.com/item?id=39863371
1,567 karma · joined October 12, 2010
According to antirez, he understood the implications of licensing Redis as BSD: https://news.ycombinator.com/item?id=39863371
AWS revenue is about $90.76B, though most of it isn't from Redis, I'd assume. But let's be generous, and assume 10% of that is. So about $10mm. For the recent version, Redis-the-company contributions to Redis-the-software were less than third of the code base, so let's say they get $4mm. That's very little revenue for a company that has a valuation of over $2B.
I won't blame them for regretting their past actions, but I hope the lesson would be learned: if you want to put limitation on the use of your software, you shouldn't have licensed it in a way that doesn't allow such. You can't recall a gift because you don't like how the recipient is using it. Though you are more then welcome not to gift them ever again.
IIRC, it only need libc and OpenSSL (the latter only if you build TLS) on your system, and provide their forked copies of Jemalloc, LUA, fpconv, HiRedis, Linenoise and Hdr_Histogram.
Tesla fails all, with frequent misaligned panels, paint bubbling, ill-fitting parts, etc. It has software bells and whistels, but shitty build quality for the hardware.
20+ years ago, we did a trade-off in the datacenter, replacing single piece of expensive hardware with multiple copies of cheap hardware, with software to patch over the deficiencies. That doesn't work as well when the product is a single piece of hardware.
With some smart software, I can run 3 servers at 50% uptime each, and get 100% uptime. I can't get one nicely assembled car from two shitty ones.
The reason I don't think about flies on a UNIX-derived systems as a key-value store (filename->file content), is that in such systems, we have many things that aren't really files that expose a file system interface regardless.
The _marketed_ intent behind those regulation is a good one. The actual regulations are just favoring one player over the other: I guess the lobbyists were ahead of the process this time (good for them). As much as everyone would claim ignorance later, I'm not willing to give them the credit of being that stupid.
ofc, like in any security-related field, many are LARPing instead of practicing, and that's a different issue.
It does require some organizational changes, and a slightly different set of skills, and some fail to realize they lack both.
Telegram is mostly few-to-many.
But all the tax bills are published (though in a harder to navigate format) on the country website. I went and checked all my neighbors property taxes there when signs against a modest tax increase for road fixing started going up in the neighborhood.
As for property tax drop: there are such mechanisms, like those in the Mills act. They’re not easy to use though
And in South Berkeley, I pay almost $30k/year. Neighbor pays $3.5k.
After the first task, we were asked "what do you think about the task?". I raised my hand: "it's humiliating", and left the room.
I didn't had any other offer at that time, and got a call from them a day later, telling me they'd like to talk with me. Replied that I don't think it'd be a good match.
I later learned that role was for the infamous "binary options", a gray market betting website.