Here's the launch presentation at jscamp.asia: http://www.youtube.com/watch?v=7T0PJbJaMwA
RubyJS: A JavaScript standard library based on the Ruby core-lib
21–30 of 38 posts
Re: RubyJS: A JavaScript standard library based on the Ruby core-lib
#22Is Underscore.js not good enough for you guys? Really?
Re: RubyJS: A JavaScript standard library based on the Ruby core-lib
#23I'm not a rubyist, and I can see how this can be nice for ruby developers, but IMHO, if you need javascript - use javascript. Why add another layer of complexity and error proneness? What happens when a different js programmer needs to review your code? Or when you need to write some Node.js code and forgot all about syntax? "The main motive is to have a decent standard library for JavaScript" - jQuery works just fin…
Re: RubyJS: A JavaScript standard library based on the Ruby core-lib
#24 If I had to code JavaScript I would use RubyJS.
Yukihiro (Matz) Matsumoto, creator of Ruby
Of course, the best authority for writing ruby-like JS is Matz, who else would be better? ;-DRe: RubyJS: A JavaScript standard library based on the Ruby core-lib
#25If you're after a standard library for Javascript, you could do worse than including es5-shim. Which has the advantage of being a library that (partially) implements a standard: Ecmascript 5. > es5-shim.js and es5-shim.min.js monkey-patch a > JavaScript context to contain all EcmaScript 5 > methods that can be faithfully emulated with a > legacy JavaScript engine. It provides Array::map, Array::filter, Array::reduce…
Sure. You could do worse than RubyJS as well. This project is implementing the standard set by the reference implementation of Ruby and its standard library. And having used Ruby a bit, I’ve come to find its standard library quite good, as dynamic languages go. So it doesn’t much matter that ES5 features are “more native”—here and now, it’s still a matter of preference.
And I'm definitely not saying that PHP.js should be used.
[edit] To be more specific, I really don't see the point of using a third-party library when the native methods are available. IMHO, if you choose a language, you should stick with it.
Re: RubyJS: A JavaScript standard library based on the Ruby core-lib
#26I'm not a rubyist, and I can see how this can be nice for ruby developers, but IMHO, if you need javascript - use javascript. Why add another layer of complexity and error proneness? What happens when a different js programmer needs to review your code? Or when you need to write some Node.js code and forgot all about syntax? "The main motive is to have a decent standard library for JavaScript" - jQuery works just fin…
Prototype, Underscore, jQuery, Coffescript, .... RubyJS - nobody love pure JS, when you've got a chance to write nice code(short and descriptive) - why don't use this ability? And about "different js programmer needs to review your code" - if you don't know smth then you need to study it. That's a fundament of programming world(probably not only programming))
jQuery, Prototype and afaik Underscore helper functions have been wrote when the standard wasn't ready. Now that it is, developers should start using them.
Re: RubyJS: A JavaScript standard library based on the Ruby core-lib
#27Re: RubyJS: A JavaScript standard library based on the Ruby core-lib
#28Is Underscore.js not good enough for you guys? Really?
I use ES5 shim instead. That way when I ditch support for IE8, I don't have to fix anything.
[1] Obviously Underscore doesn't have methods, it has utility functions attached to punctuation.
Re: RubyJS: A JavaScript standard library based on the Ruby core-lib
#29How are callbacks handled in this library? I prefer js anonymous functions to Procs & lambdas in Ruby.
I do as we'll. After working in node for a bit I have come to appreciate how nice the call backs work, but I hate the fact I have to use them every where. Plus ruby has a few ways to implement callbacks which can be confusing.
Re: RubyJS: A JavaScript standard library based on the Ruby core-lib
#30Earlier quoted context omitted.
Sure. You could do worse than RubyJS as well. This project is implementing the standard set by the reference implementation of Ruby and its standard library. And having used Ruby a bit, I’ve come to find its standard library quite good, as dynamic languages go. So it doesn’t much matter that ES5 features are “more native”—here and now, it’s still a matter of preference.
I don't really see why RubyJS would be better than PHP.js. And I'm definitely not saying that PHP.js should be used. [edit] To be more specific, I really don't see the point of using a third-party library when the native methods are available. IMHO, if you choose a language, you should stick with it.