Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Support for Ruby 1.9.3 will end on February 23, 2015

ruby-lang.org

Post reply on HN
Print view View original

1–10 of 24 posts

Re: Support for Ruby 1.9.3 will end on February 23, 2015

#4

Post by diminish »

With many apps stuck on DataMapper, thus ruby 1.9 - I can't help but think: why do programming languages evolve so quickly? I suppose the language must be the slowest moving part in the architecture...Due to immense competitiveness from other languages, all language designers rush ahead to add more and more versions..

I wish, Python/Ruby moved slower and focus on non-visible or backwards compatible improvements

Re: Support for Ruby 1.9.3 will end on February 23, 2015

#5

Post by gary4gar »

diminish wrote: post #4

With many apps stuck on DataMapper, thus ruby 1.9 - I can't help but think: why do programming languages evolve so quickly? I suppose the language must be the slowest moving part in the architecture...Due to immense competitiveness from other languages, all language designers rush ahead to add more and more versions.. I wish, Python/Ruby moved slower and focus on non-visible or backwards compatible improvements

Ruby 2 is almost dropin replacement for Ruby 1.9.3. so upgrading should be easy & backwards compatible with following exceptions

    Incompatibility
    There are five notable incompatibilities we know of:

    The default encoding for ruby scripts is now UTF-8     [#6679]. Some people report that it affects existing     programs, such as some benchmark programs becoming very slow [ruby-dev:46547].

    Iconv was removed, which had already been deprecated when M17N was introduced in ruby 1.9. Use String#encode, etc. instead.

    There is ABI breakage [ruby-core:48984]. We think that normal users can/should just reinstall extension libraries. You should be aware: DO NOT COPY .so OR .bundle FILES FROM 1.9.

    #lines, #chars, #codepoints, #bytes now returns an Array instead of an Enumerator [#6670]. This change allows you to avoid the common idiom "lines.to_a". Use #each_line, etc. to get an Enumerator.

    Object#inspect does always return a string like # instead of delegating to #to_s. [#2152]

    NEWS: https://www.ruby-lang.org/en/news/2013/02/24/ruby-2-0-0-p0-is-released/
I would encourage you to try out ruby2 today, you will be surprised how easy the upgrading process is. Plus, your app will run 20% faster due to performance improvements

Re: Support for Ruby 1.9.3 will end on February 23, 2015

#6

Post by gnufied »

gary4gar wrote: post #5
diminish wrote: post #4

With many apps stuck on DataMapper, thus ruby 1.9 - I can't help but think: why do programming languages evolve so quickly? I suppose the language must be the slowest moving part in the architecture...Due to immense competitiveness from other languages, all language designers rush ahead to add more and more versions.. I wish, Python/Ruby moved slower and focus on non-visible or backwards compatible improvements

Ruby 2 is almost dropin replacement for Ruby 1.9.3. so upgrading should be easy & backwards compatible with following exceptions Incompatibility There are five notable incompatibilities we know of: The default encoding for ruby scripts is now UTF-8 [#6679]. Some people report that it affects existing programs, such as some benchmark programs becoming very slow [ruby-dev:46547]. Iconv was removed, which had already be…

Or which Datamapper issues we are talking about? I see datamapper has not seen an update in a year, but It should be fairly trivial to fix whatever incompatibilities are because of 2.1.

Re: Support for Ruby 1.9.3 will end on February 23, 2015

#8

Post by gafads »

diminish wrote: post #4

With many apps stuck on DataMapper, thus ruby 1.9 - I can't help but think: why do programming languages evolve so quickly? I suppose the language must be the slowest moving part in the architecture...Due to immense competitiveness from other languages, all language designers rush ahead to add more and more versions.. I wish, Python/Ruby moved slower and focus on non-visible or backwards compatible improvements

I certainly don't. Who argues for slow innovation, that's dumb really. Argue for minimal breaking changes. Python got into trouble because it introduced a huge swath of breaking changes, and not enough sugar to coax people to 3. Ruby has it's problems, but the 1.93 to 2.0 transition was not one of them.

Re: Support for Ruby 1.9.3 will end on February 23, 2015

#10

Post by Demiurge »

gafads wrote: post #8
diminish wrote: post #4

With many apps stuck on DataMapper, thus ruby 1.9 - I can't help but think: why do programming languages evolve so quickly? I suppose the language must be the slowest moving part in the architecture...Due to immense competitiveness from other languages, all language designers rush ahead to add more and more versions.. I wish, Python/Ruby moved slower and focus on non-visible or backwards compatible improvements

I certainly don't. Who argues for slow innovation, that's dumb really. Argue for minimal breaking changes. Python got into trouble because it introduced a huge swath of breaking changes, and not enough sugar to coax people to 3. Ruby has it's problems, but the 1.93 to 2.0 transition was not one of them.

Obviously no one is arguing for slow innovation of everything. However, it is not dumb at all to argue for slow innovation of something foundational, if it allows for things built on top to innovate faster. This is arguing for faster overall innovation. This sentiment might be wrong in this case, because the transition 1.9 to 2.0 might be painless, but I'm replying to your original misrepresentation of the argument.
Post reply on HN