Re:Ruby is beautiful (but I'm moving to Python)
by mnutt on Sunday November 28, 2010 @05:27PM
(#1948536)
> It's true that you don't have this issue in Ruby as the "standard" is simply the original implementation (aka there is no standard at all, and not really any competing implementation).
Check out https://github.com/rubyspec/rubyspec.
And there are plenty of competing implementations: JRuby, Rubinius, MagLev, etc.
Re:Ruby is beautiful (but I'm moving to Python)
by masklinn on Monday November 29, 2010 @02:28AM
(#1949687)
Checking out an effort to extract a viable specification from an implementation which manages to be incompatible with itself every other release? Why?
Re:Ruby is beautiful (but I'm moving to Python)
by bad_user on Wednesday December 01, 2010 @04:13AM
(#1957333)
The C# compiler in .NET also has incompatibilities with the ECMA standard. Need I mention C++, the most widely used and at the same time poorly implemented language ISO standard ever?
In fact, can you mention a single language with a standard that doesn't brake compatibility with its standard?
And yet the point is moot, because compatibility between implementations is manageable for popular languages like Javascript, C++ and yes, Ruby (JRuby, Rubinius). That's not the case for Smaltalk.
Re:Ruby is beautiful (but I'm moving to Python)
by steveklabnik on Sunday November 28, 2010 @05:34PM
(#1948553)
Not to mention the impending ISO standard.
Wow.
> I don't appreciate that ML doesn't have a simple concept like operator overloading
ML operators are nothing more than functions. The issue of "operator overloading" comes from the type system and the simplicity of the language.
> or that in LISP every DSL still looks like LISP
You might want to read on Scheme reader macros.
> I don't like that a Smalltalk application is not portable between implementations
It's true that you don't have this issue in Ruby as the "standard" is simply the original implementation (aka there is no standard at all, and not really any competing implementation).
> or that applications are big, monolithic images of the virtual machine with everything included, even the IDE.
That definitely isn't the case. That's not the case in GNU Smalltalk, and most commercial smalltalk let you create a stripped production image which contains only the necessary code.