News for hackers. Stuff that matters.
Re:Reactive Extensions for Ruby by steveklabnik on Sunday July 21, 2013 @04:41AM (#6078260)
I tweeted about this release, and they specifically asked me for contributions, saying they would love help with making the project more Ruby like, actually following conventions. I told them that I don't work on anything Microsoft related, for personal ethical reasons, and they actually handled that response quite gracefully.
Re:Reactive Extensions for Ruby by tinco on Sunday July 21, 2013 @06:13AM (#6078399)
That's interesting.. Where do you draw the line as far as Microsoft relatedness goes? Is your motivation more to make sure you never contribute to Microsoft goals, or is it actually never to be exposed to Microsoft technology yourself?

Is there something Microsoft affected you personally with or is it their business practices in general?

Re:Reactive Extensions for Ruby by steveklabnik on Sunday July 21, 2013 @06:36AM (#6078427)
Microsoft attempted to destroy humanity's crowning achievement (so far): the World Wide Web. Totally unforgivable.

Now: people sometimes use Microsoft products, and they're often beginners. I will write software that runs on Windows, as that's often the people who need help the most.

But contributing directly to a Microsoft product is too much for me.

Re:Reactive Extensions for Ruby by seanmcdirmid on Sunday July 21, 2013 @08:57AM (#6078643)
Germany attempted once to take over Europe and lots of people died. Totally unforgivable.

Now: people sometimes visit Germany, and they're often just tourists. I will build things for Germans, as that makes me money.

But contributing directly to Germany is too much for me.

Re:Reactive Extensions for Ruby by steveklabnik on Sunday July 21, 2013 @08:59AM (#6078648)
I too enjoy absurd comparisons.
Re:Reactive Extensions for Ruby by seanmcdirmid on Sunday July 21, 2013 @09:03AM (#6078653)
Well, stop judging the Microsoft of today with the one of yesterday. Many of us worker bees never went through that time period, and we really are just trying to build better things.
Re:Reactive Extensions for Ruby by steveklabnik on Sunday July 21, 2013 @09:08AM (#6078663)
Comparing "embrace, extend, extinguish" to the Holocaust isn't exactly helping me not judge you.
Re:Reactive Extensions for Ruby by seanmcdirmid on Sunday July 21, 2013 @09:42AM (#6078756)
I was just invoking Goodwin's law earlier rather than later.
Re:Reactive Extensions for Ruby by pbsdp on Sunday July 21, 2013 @11:18AM (#6079026)
Your management hasn't really changed. I grew up with MS in the 80s and 90s -- I'm not quick to forgive a monopoly that set the whole industry back by 10 years.
Re:Reactive Extensions for Ruby by seanmcdirmid on Sunday July 21, 2013 @09:41PM (#6081312)
So what does senior management have to do with this? Just crap on any peon at MS who wants to engage with open source doesn't really hurt them.
Re:Reactive Extensions for Ruby by pbsdp on Monday July 22, 2013 @11:57AM (#6084541)
The peon actively chose to work there and participate in Microsoft's attempts to dismantle any competition in any field they enter through highly questionable tactics.
Re:Reactive Extensions for Ruby by seanmcdirmid on Monday July 22, 2013 @08:11PM (#6087358)
So Machiavellian huh?

Such cynicism and paranoia just breeds an equal amount of such on our side. It makes it that much harder for those of us who wish to engage and do good in the OSS community.

Re:Reactive Extensions for Ruby by pbsdp on Tuesday July 23, 2013 @10:54PM (#6094224)
I'm not really sure what you could possibly expect after MS spent most of the natural lifetime of this industries senior developers' behaving badly.
Re:Reactive Extensions for Ruby by tinco on Monday July 22, 2013 @06:45AM (#6082923)
Rather weak response. You could also have said why you think Microsoft either hasn't changed, or that regardless of having changed hasn't earned their respect yet.

Now the thread is just worthless.

Re:Reactive Extensions for Ruby by Argorak on Sunday July 21, 2013 @07:39AM (#6078493)
This goes beyond being 'not ruby-like', as it shows bad craftsmanship (e.g. mixed identifier case, bad indentation, unrunnable code). You don't need help by others for that.