Sick of Ruby, dynamic typing, side effects, and object-orientation (2014)

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by jodrellblank on Wednesday November 08, 2017 @03:10AM (#15650563)

Ah, yes, that's the crux of it. We'd love it if the world would just stop changing so we can relax and stop learning. Well, too bad!

Something about this smells.

What is it.

Is it the way "we would love it if it stopped changing" but it's us who is changing it?

Is it that the changes are reinventing the wheel? Churn because frothy churn is easier and more profitable than meticulous, solid, long-lasting foundations?

Or is it that we still haven't managed to orient the programming industry around 'finished' software such that if we ever 'finish' software we immediately stop being employed, so we have a pathological need for software to continually need to be rewritten, at the level the average programmer can rewrite?

[ Parent | on HN ]

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by sillysaurus3 on Wednesday November 08, 2017 @03:25AM (#15650616)

It doesn't matter if I agree with you in principle. If you don't play the game, your career will dry up. The world won't care.

[ Parent | on HN ]

Re:Sick of Ruby, dynamic typing, side effects, and object-or... by jodrellblank on Wednesday November 08, 2017 @03:26PM (#15656610)

From your other posts, your main problem was that you didn't want to / couldn't move to where jobs were, not that low level gamedev code is no longer being written - VR and AR are testifying to that.

How is this client side rewrite every few months fundamentally different from the broken window fallacy? as in, unsustainable because it adds no value overall?

[ Parent | on HN ]