News for hackers. Stuff that matters.
Re:JavaScript Isn't Scheme (2013) by haskellandchill on Wednesday April 25, 2018 @07:17PM (#16927299)
Python is awful. Since you haven’t heard any complaints. Maybe 3 is ok, can’t use it don’t know. Have to use 2.7 at work. Can’t make jars for Spark with Python and yes I am salty about it. Meanwhile we are on Ruby 2.5.1 because they didn’t fork the whole ecosystem with a language upgrade.
Re:JavaScript Isn't Scheme (2013) by chc on Wednesday April 25, 2018 @07:47PM (#16927522)
Ruby's 1.9/2.0 upgrade had pretty similar changes to Python 3. For example, in Ruby 1.8.7, 'hello'[1] returned 101, whereas now it returns 'e', and String#each doesn't even exist anymore. Similarly, string encodings became significant in both Ruby and Python's breaking changes. It seemed to me like the Ruby ecosystem just didn't drag its feet as much as Python's (probably largely because Rails had enough pull to drag the Ruby ecosystem along with it, and Rails enthusiastically supported Ruby 2).
Re:JavaScript Isn't Scheme (2013) by mxyzptlk on Wednesday April 25, 2018 @10:40PM (#16928381)
Matz didn't change puts. It seems trivial, but I suspect making print a statement again would do a lot to speed up the Python3 adoption rate.
Re:JavaScript Isn't Scheme (2013) by maoistinquisitr on Wednesday April 25, 2018 @08:10PM (#16927654)
Python and JS are both equally awful. The sad reality is that Perl 5 still remains the only viable scripting language aside from scheme (lol) with sane scoping and lexical closures.
Re:JavaScript Isn't Scheme (2013) by lizmat on Thursday April 26, 2018 @04:03AM (#16929876)
I think you will find that Perl 6 is even more sane in that respect.