Re:The Mid-Career Crisis of the Perl Programmer
by goostavos on Monday March 10, 2014 @01:01PM
(#7374113)
You're right, everything is an object in Python. However, what I'm referring to is more on the application design side that you see in the enterprise Java community, rather than the implementation of the core types or builtins.
Re:The Mid-Career Crisis of the Perl Programmer
by midas007 on Tuesday March 11, 2014 @07:04AM
(#7378497)
Hopefully this offends everyone &| starts yet another pointless religious debate: Java was a reaction to C/C++ (language safety); Python was a reaction to Perl's messes; and Ruby is polished Perl. And bonus: Go was a reaction to Java and C++ compiles taking forever.
With production usage, each platform matures through attempts to learn from the past while not forgetting too much before that.
(Sadly, though most everything will be coded in javascript.)
Re:The Mid-Career Crisis of the Perl Programmer
by kbenson on Tuesday March 11, 2014 @12:11PM
(#7380168)
There's hope! With a sufficiently complex caching and verification system, we can deploy chunks of JS that implement interpreters in-browser, last a long time, and can possibly be pre-compiled into an optimized form.
If we really view JS as assembly for the web, I think there's an interesting future.
This sounds really weird to me considering that almost every noun is a class in Python, but that's not the case in Java (primitives are not classes and there's no easy to use meta-class construction).