Reactive Extensions for Ruby

http://Rxrb.codeplex.com/

by CalinBalauru • 13 years ago

24 29 13 years ago

rxrb.codeplex.com

pallandt2• 13 years ago

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.

lucisferre• 13 years ago

Why, Microsoft has other projects on Github: https://github.com/windowsazure/

But yeah, most stuff ends up on Codeplex.

bjg• 13 years ago

See: https://github.com/Reactive-Extensions

pallandt2• 13 years ago

Thanks!

xentronium• 13 years ago

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?

roryokane• 13 years ago

http://rxrb.codeplex.com/documentation has a more detailed description. It also has code examples, though they are misformatted.

Argorak4• 13 years ago

This is very much the definition of a code dump: a single file, not following any standard ruby code conventions - not even naming conventions (it would be called "rx" otherwise), tests within that file, misformatted code. snake_cased and camedBacked variables mixed. It monkey-patches Enumerable and uses class variables. `gets` at the end of the file, to keep the Windows console open, rendering the whole thing unusable as a library. Also, the author clearly doesn't know that you don't need ".rb" when requiring files. Last commit on December 22, 2012.

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.

steveklabnik4• 13 years ago

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.

tinco2• 13 years ago

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?

Argorak4• 13 years ago

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.

coolj• 13 years ago

Also...

    Observable.throw(Exception.new("woops!")).subscribe(Class.new(Observer) do
    [...]
    end.new)

http://rxrb.codeplex.com/SourceControl/latest#lib/Rx.rb (bottom)

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.

Argorak4• 13 years ago

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#.

jms_2• 13 years ago

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.

bitcrusher• 13 years ago

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."

davesims• 13 years ago

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:

  class MutableDisposable : Disposable

and so on.

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.

Argorak4• 13 years ago

This is not clumsy. It is completely broken, it cannot even be used as a library.

Reactive Extensions for Ruby

Related Stories