Re:“I'm basically giving myself a permanent vacation from be...
by jessaustin on Thursday July 12, 2018 @03:54PM
(#17518080)
Sure, there are growing pains with any breaking change. Do you think the ruby 1.8 -> 1.9 transition went more smoothly than the python 2.7 -> 3.x... transition?
Re:“I'm basically giving myself a permanent vacation from be...
by coldtea on Thursday July 12, 2018 @05:43PM
(#17518878)
Sure it did. Barely took a few years, and it also had a large performance boost (whereas 3 initially came with regressions until 3.4 or so).
Plus, basic things like Rails were working from the start.
Re:“I'm basically giving myself a permanent vacation from be...
by jrochkind1 on Thursday July 12, 2018 @04:57PM
(#17518536)
My impression is that it did, yes.
Re:“I'm basically giving myself a permanent vacation from be...
by jrochkind1 on Thursday July 12, 2018 @11:24PM
(#17520279)
But on the other hand, Python's overall popularity has grown (mostly on the back of 'data science' I think), while rubies has shrunk, and python is definitely more popular than ruby at the moment... so python's lesser success at that transition didn't actually matter much in the end?
That's the ruby solution. I like the ruby API here. When ruby introduced it in 1.9, it did cause similar upgrade pain, since you weren't used to having your strings tagged with an encoding, and suddenly they all kind of need to be if you want to do anything with them as strings-not-bytes.
As someone else noted would be the result, indeed the result was lots of "incompatible encoding" exceptions.
I think ruby actually has a pretty reasonable API here, but several years on, there are still _plenty_ of developers who don't understand it.