3 ms·

Of course they're selfishly motivated - everyone is. The point is this time Redis/NoSQL stands to benefit as well.

• d0mine 15y ago
  It seems you've skipped the sentence: If, in the end, Redis' codebase becomes cluttered and performance and maintenance suffer, we all lose. </quote>
  • mythz 15y ago
    That's a case for not merging, not for a parallel win32-based project - which this implementation could serve either of.
    • rbanffy 15y ago
      It would risk diverting attention from the Unix port to the Win32 one. Even if the Redis developers don't pay attention to this distraction, its mere existence fragments the codebase and creates two semi-compatible versions. And if the Windows version sucks badly, any Windows user who tries to install it on Windows will end up blaming Redis and try something else. On Windows. Microsoft wins and we lose on all scenarios.
      • mythz 15y ago
        This is a very pessimistic view of the world and future events (which I don't share). I'd get that looked at. A bad Redis port by Microsoft makes them look bad, whilst their endorsement of Redis makes Redis looks good. The 'pro developers' that Redis attracts are going to be more than capable of identifying the culprit behind a shitty port.