Program your next server in Go

Re:Program your next server in Go by robohamburger on Tuesday June 07, 2016 @07:15PM (#11858809)

Yeah I suppose at this point the graph falls apart since even the prospect of writing new perl code does not sound fun to me but I am sure could be fun to someone.

[ Parent | on HN ]

Re:Program your next server in Go by antod on Tuesday June 07, 2016 @08:04PM (#11859052)

Yeah, I wouldn't want to be writing new Perl either. It was actually Ruby's "optimized for developer happiness" mantra that triggered my comment.

Sometimes I mumble under my breath that Ruby is Perl for the 21st century - gleefully creative hackers leaving behind overly clever code for far less happy developers to deal with.

A culture of optimising the elegance of the API over the simplicity and maintenance of the implementation.

[ Parent | on HN ]

Re:Program your next server in Go by majewsky on Wednesday June 08, 2016 @05:52AM (#11861118)

I disagree. With practice, you can write very clean Perl code that's easy to follow along because all the modules play along nicely. Ruby OTOH has a culture of gems doing all kinds of mysterious black magic that make it difficult for a maintainer to figure out the data flow.

Source: Maintained a 300 kLOC Perl application for 3 years, now working with legacy and new Rails applications.

[ Parent | on HN ]