Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft team submits Redis patch to enable Windows support

github.com

Post reply on HN
Print view View original

61–70 of 103 posts

Re: Microsoft team submits Redis patch to enable Windows support

#61

Post by test2754 »

Ecio78 wrote: post #50
beagle3 wrote: post #46

Earlier quoted context omitted.

> Microsoft has made a good gesture When on the other hand they are poisoning the Android/Linux ecosystem with FUD, patent extortion and the like. While I would prefer the discussion to stay civil and technical, Microsoft is consistently earning every snark they are receiving, and then some.

I dont want to defend Microsoft, but i think that if we dig deep enough we found bad "habits" in every big society: what about Google[1] or Apple suing everybody from Samsung [2] to Luxembourgish restourants[3]? [1] http://www.theverge.com/2011/05/12/google-android-skyhook-la... [2] http://www.businessweek.com/news/2011-08-02/apple-lawsuit-pu... [3] http://news.ycombinator.com/item?id=3190944

Apple is the worst.

- They don't allow to run your own programs on your own computer. Can you imagine Windows blocking Firefox? Microsoft was about to be disintegrated just for making a web browser, yet Apple can fully block competing programs.

- They are very expensive, so the great majority of world population can't use software made for Apple systems.

Re: Microsoft team submits Redis patch to enable Windows support

#62

Post by motti »

dugmartin wrote: post #37
kogir wrote: post #23

Earlier quoted context omitted.

It's reserved for compatibility: "Do not use the following reserved device names for the name of a file: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9. Also avoid these names followed immediately by an extension; for example, NUL.txt is not recommended."[1] [1] http://msdn.microsoft.com/en-us/library/windows/desktop/aa36...

I once saw some interesting behavior on a Windows 95 machine - my brother printed a drawing for a convention to a file. The printer was a HP LaserJet with plug in module that enabled Postscript. He named the file "con" and when he hit OK on the print dialog the entire screen buffer (over the windowing interface) started filling with Postscript.

Windows tries to prevent you naming a file "con". I once renamed a text file con in Win95; using a raw disk editor to change the file entry and it did this too - every time I saved text in the file it would write it console/DOS style to the screen.

Re: Microsoft team submits Redis patch to enable Windows support

#63

Post by Legion »

yread wrote: post #28

Wow, I'm kind of surprised by the amount of snark ("eww it's 140k lines", "mini git tutorial", "patch file instead of pull request"). It seems it's so big because it contains the libuv. The instructions to compile on Windows don't seem trivial at all and if I cared enough to try this I would appreciate that they wrote it step-by-step. The guys at MS just sat down and made it work while antirez was throwing out sugges…

I think patch versus pull request is a valid complaint, but there's absolutely no reason to be snarky about it.

Everything else just reeks of MS bashing that reinforces the negative view of the open source crowd that many on the MS side of the divide have.

Github is looking to pull the Windows crowd into their world; on the blog, they stated that as an explicit goal for their hiring of Phil Haack.

So, please, play nice. I would much rather Github stay a fairly harmonious place than be another open source vs. MS battleground.

Re: Microsoft team submits Redis patch to enable Windows support

#64

Post by jf »

Legion wrote: post #63
yread wrote: post #28

Wow, I'm kind of surprised by the amount of snark ("eww it's 140k lines", "mini git tutorial", "patch file instead of pull request"). It seems it's so big because it contains the libuv. The instructions to compile on Windows don't seem trivial at all and if I cared enough to try this I would appreciate that they wrote it step-by-step. The guys at MS just sat down and made it work while antirez was throwing out sugges…

I think patch versus pull request is a valid complaint, but there's absolutely no reason to be snarky about it. Everything else just reeks of MS bashing that reinforces the negative view of the open source crowd that many on the MS side of the divide have. Github is looking to pull the Windows crowd into their world; on the blog, they stated that as an explicit goal for their hiring of Phil Haack. So, please, play ni…

> So, please, play nice.

Working on it. Microsoft is a big company.

Re: Microsoft team submits Redis patch to enable Windows support

#65

Post by plorkyeran »

rbanffy wrote: post #29
adrianpike wrote: post #11

Can somebody more familiar with the Windows environment explain why prn.h is an "invalid file name"? edit:// thanks all! :)

PC-DOS inherited it from CP/M 80. Windows was built at first on top of it and then replaced it in stages. I have no idea why would this still be present in the current codebase. It would probably be easier just to fix the filesystem.

There's countless batch files that rely on NUL (including with extensions, usually because some other batch file is appending the extension). Most of the other ones could probably be safely removed, but it would still run contrary to Microsoft's policy of not breaking backwards compatibility unless absolutely necessary.

Re: Microsoft team submits Redis patch to enable Windows support

#66

Post by d0mine »

mythz wrote: post #58
rbanffy wrote: post #49

Earlier quoted context omitted.

> give credit where credit is due Sure. Just don't forget they profit from Windows sales and, thus, will do anything to justify the deployment of a Windows server instead of a Linux one. Including contributing to a Unix-native product. If, in the end, Redis' codebase becomes cluttered and performance and maintenance suffer, we all lose. I mean, all of us except Microsoft, who wins both by us losing and from gaining s…

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

It seems you've skipped the sentence:

If, in the end, Redis' codebase becomes cluttered and performance and maintenance suffer, we all lose.

Re: Microsoft team submits Redis patch to enable Windows support

#67

Post by slig »

briancurtin wrote: post #26
splitbrain wrote: post #4

A patch file in a gist instead of a pull request? sigh

It's really no wonder why people don't contribute to open source when this is the first response.

Except they're not a person contributing in his free time, they're Microsoft, working exclusively on their own interest.

Re: Microsoft team submits Redis patch to enable Windows support

#68

Post by shinratdr »

nknight wrote: post #56
Ecio78 wrote: post #50

Earlier quoted context omitted.

I dont want to defend Microsoft, but i think that if we dig deep enough we found bad "habits" in every big society: what about Google[1] or Apple suing everybody from Samsung [2] to Luxembourgish restourants[3]? [1] http://www.theverge.com/2011/05/12/google-android-skyhook-la... [2] http://www.businessweek.com/news/2011-08-02/apple-lawsuit-pu... [3] http://news.ycombinator.com/item?id=3190944

[1] is a link to a story about Google being sued by Skyhook, not Google suing anybody.

They were being sued by Skyhook because they were using Android compatibility tests "as a club to get OEMs to do what [they] want" (their words). In this case, they were using it to push out Skyhook in favour of Google Location Services.

Re: Microsoft team submits Redis patch to enable Windows support

#69

Post by nknight »

kenjackson wrote: post #60
nknight wrote: post #56

Earlier quoted context omitted.

[1] is a link to a story about Google being sued by Skyhook, not Google suing anybody.

Yes, but look at why Skyhook is suing them. We live in a weird bubble where if a company gets sued then they are the victim. No one even fathoms, when it comes to Google at least, that maybe they did something to deserve being sued.

He didn't say "Google is being mean", he said they and Apple were "suing everybody", a statement in no way supported by one of his references.

Re: Microsoft team submits Redis patch to enable Windows support

#70

Post by burgerbrain »

Legion wrote: post #63
yread wrote: post #28

Wow, I'm kind of surprised by the amount of snark ("eww it's 140k lines", "mini git tutorial", "patch file instead of pull request"). It seems it's so big because it contains the libuv. The instructions to compile on Windows don't seem trivial at all and if I cared enough to try this I would appreciate that they wrote it step-by-step. The guys at MS just sat down and made it work while antirez was throwing out sugges…

I think patch versus pull request is a valid complaint, but there's absolutely no reason to be snarky about it. Everything else just reeks of MS bashing that reinforces the negative view of the open source crowd that many on the MS side of the divide have. Github is looking to pull the Windows crowd into their world; on the blog, they stated that as an explicit goal for their hiring of Phil Haack. So, please, play ni…

The complaint about the size is most certainly not just "MS bashing". Dumping massive flawed pieces of code on people out of the blue and expecting them to be grateful is bad form, no matter who you are.

Unfortunately this seems to be Microsoft's MO.

Post reply on HN