5 ms·
So, let's talk about the incentivization issue first. Why is it OK for them to ask antirez to support Windows, but not OK for antirez to ask them to support Li
by angersock 15y ago
So, let's talk about the incentivization issue first.
Why is it OK for them to ask antirez to support Windows, but not OK for antirez to ask them to support Linux/POSIX?
Because antirez has a tool whereas BigCorp presumably has a problem. Because all of us could benefit from this, while only some of us might benefit from BigCorp switching to Linux.
Asking somebody to make their tool more available is, I posit, much more reasonable than asking somebody to change their problems.
BigCorp has potentially hundreds of thousands tied up in existing equipment, IT infrastructure, and training for employees. You and I might not flinch at spinning up a VM to run a database, but we (and the rest of the HN community!) should not fool ourselves into thinking that this is in any way always appropriate for a company.
Meanwhile, a huge fraction of antirez's time will be spent dealing with the effects of trying to maintain a high-performance, low-level datastore on two utterly incompatible platforms, and the time he spends on that is time taken away from work on other bugs and features, which also amounts to time taken away from all the people who already use Redis on POSIX.
Or, you know, he might talk with the Microsoft development team and try to get them to take over maintenance of the Microsoft codebase, and clean up the platform-specific architecture that gets in the way--and in so doing, write better code.
If you can't/won't write platform-independent code, you are either lazy or your problem domain is heavily dependent on your platform. As far as I know, in-memory key/value stores aren't a Linux-specific problem, so...
<rant>
There is no incentive at all for antirez, his employer VMware, or the Redis community at large to go through the pain of integrating Windows support into Redis mainline.
Let's look past incentives here. Let's talk about Doing the Right Thing.
A huge number of people here make daily use of software packages and stacks that are open source. We owe our livelihoods to the folks that have been kind enough to release the source to their programs and, more importantly, work with the community to improve their code.
We owe it to ourselves and our community to call out people being lazy and selfish, and letting politics overrule sound engineering and decency.
This is an unreasonable decision by antirez. He's got a cool framework. He's got a bunch of code and (presumably) people that are happy to work with him on making it even more useful.
He's also not going for it, because "use linux lol".
Not because it's hard, not because he doesn't have folks that can add it, not because the problem extends beyond some refactoring and #ifdefs and makefiles.
Because he's lazy.
Because Linux is the One True Way.
Because helping out anyone who can't just change their infrastructure on a whim is too much to ask.
Really folks? You don't see a problem with this?
</rant>
- nknight 15y agoWhat a disgusting assault on Salvatore's character. I really don't think anything more needs to be said, your resorting to such attacks pretty well speaks for itself.
- angersock 15y agoSir or madam, if you would like to articulate why you classify my observations (and in the rant section, opinions) as disgusting, I would very much appreciate the insight. If I have misclassified the situation, by all means, enlighten me.
- tptacek 15y ago"use linux lol" is probably the point where you really set him off, but your entire argument is juvenile. There is a dollar amount that would get Salvatore to do a first-class WinAPI Redis implementation (he won't advertise it, and may not even believe it exists, but I assure you that there is one). Pitch numbers to him until you find it, then, pay him. You may or may not choose to share your newly purchases WinAPI Redis with the rest of the world --- bear in mind that there are enterprise products with mid-5-figure per unit price tags that do nothing but provide WinAPI-friendly .NET-compatible memcached.
- tptacek 15y agoGuy writes code for Linux. Code could theoretically be made to work on Windows. Windows users are therefore entitled to a Windows port. That's roughly your argument here; I've just done you the favor of adding concision to it. The motivations of all the parties involved, enterprise IT costs, all that jazz, none of that matters. Fundamentally you're saying "if something can be made cross-platform, it's wrong not to make it cross- platform". That is, to say the least, a comical argument coming from people who want Linux code deployed on Windows.
- angersock 15y agoGuy writes code for Linux. Code could theoretically be made to work on Windows. Windows users are therefore entitled to a Windows port. Not quite. Guy writes code for Linux. Code could theoretically be made to work on Windows. Microsoft team submits patch to achieve this functionality. Users can reasonably expect a Windows port. Guy decides using submitted code is too much effort (from article says will get harder and harder) and that besides, there is no demand for it (from article: "I don't think Redis running under win32 is a very important feature."). Users have been denied functioning code because of arbitrary decision by guy.