Reactive Extensions for Ruby(rxrb.codeplex.com)
rxrb.codeplex.com
Reactive Extensions for Ruby
http://Rxrb.codeplex.com/
3 comments
I had a similar reaction when I came across it 4 months ago. I spent an hour or two refactoring it, including turning it into a valid Ruby gem.
PR here: https://github.com/Reactive-Extensions/Rx.rb/pull/1
The pull request sat in limbo until just over a week ago when Matt asked me to sign the Microsoft open source contributor agreement, which I haven't got around to yet.
Unfortunately I don't hold much hope for the library in its current state.
PR here: https://github.com/Reactive-Extensions/Rx.rb/pull/1
The pull request sat in limbo until just over a week ago when Matt asked me to sign the Microsoft open source contributor agreement, which I haven't got around to yet.
Unfortunately I don't hold much hope for the library in its current state.
The fact that you have to sign a contributor agreement is cause enough to leave it alone or fork it. I read through your commit comments, read "Please sign this agreement" and thought to myself "this is why Microsoft is dying. They just can't join the rest of us here in the present."
Yeah, I'm in two minds as to whether I'll bother signing it.
It's mostly just sad, because I had so much enthusiasm for the library when I first found it which has now simply dissipated. Oh well.
It's mostly just sad, because I had so much enthusiasm for the library when I first found it which has now simply dissipated. Oh well.
I think it's important to note that Ruby was just one target of the many ports for ReactiveExtensions: node, jquery, mootools, vanilla js, Obj-C, etc.
The code very much looks like C# to me. It echos C# in both OOP style and organization: There are multiple classes per file (allowed in Ruby but not generally conventional). There are implicit Disposable interfaces everywhere -- I guarantee that somewhere there's C# code that says:
Also, class variables.
This doesn't look like a good-faith attempt at becoming involved in the Ruby community, but rather a C# port that was assigned to someone who had just enough Ruby experience to pull the code over.
I supposed that makes it somewhat understandable? It's clumsy, but it looks to me like the result of some PM or tech lead up in Redmond deciding that not porting ReactiveExtensions to Ruby was worse than a clumsy port to Ruby.
The code very much looks like C# to me. It echos C# in both OOP style and organization: There are multiple classes per file (allowed in Ruby but not generally conventional). There are implicit Disposable interfaces everywhere -- I guarantee that somewhere there's C# code that says:
class MutableDisposable : Disposable
Also, class variables.
This doesn't look like a good-faith attempt at becoming involved in the Ruby community, but rather a C# port that was assigned to someone who had just enough Ruby experience to pull the code over.
I supposed that makes it somewhat understandable? It's clumsy, but it looks to me like the result of some PM or tech lead up in Redmond deciding that not porting ReactiveExtensions to Ruby was worse than a clumsy port to Ruby.
This is not clumsy. It is completely broken, it cannot even be used as a library.
Also...
Even if the method were named sanely and consistently `Observable::on_error`, I still don't want to write code like the above.
BTW, I don't see any class variables in the re-opened Enumerable module.
Observable.throw(Exception.new("woops!")).subscribe(Class.new(Observer) do
[...]
end.new)
Even if the method were named sanely and consistently `Observable::on_error`, I still don't want to write code like the above.
BTW, I don't see any class variables in the re-opened Enumerable module.
Seperate things. It monkey-patches Enumerable. It uses class variables. But not in the same context. Thanks for finding that.
Yes, the code looks like it is directly taken from Java/C#.
Yes, the code looks like it is directly taken from Java/C#.
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.
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?
Is there something Microsoft affected you personally with or is it their business practices in general?
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.
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.
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.
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.
I too enjoy absurd comparisons.
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.
Comparing "embrace, extend, extinguish" to the Holocaust isn't exactly helping me not judge you.
I was just invoking Goodwin's law earlier rather than later.
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.
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.
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.
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.
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.
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.
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.
Now the thread is just worthless.
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.
Bookmarked for later use, I'm sure it will come in handy, thanks for posting.I wish it was hosted on GitHub though, but given that it's backed by Microsoft, I can see why not.
Why, Microsoft has other projects on Github: https://github.com/windowsazure/
But yeah, most stuff ends up on Codeplex.
But yeah, most stuff ends up on Codeplex.
Is there any practical example? I've browsed through the source and it seems like a framework to provide asynchronous queries over arbitrary datasets. Am I right?
http://rxrb.codeplex.com/documentation has a more detailed description. It also has code examples, though they are misformatted.
Could people please have a look at the source before posting stuff here? This is not a project to be taken seriously and a waste of time. "Someone at Microsoft was playing with Ruby" is the only valuable thing you can get out of it.