Go + Services = One Goliath Project

Re:Go + Services = One Goliath Project by zozbot234 on Saturday December 21, 2019 @06:29PM (#21853956)

What's a "rapid development" language? I know about RAD, but that was a buzzword that was only ever used to push terrible languages like Visual Basic, and somewhat less terrible ones like Embarcadero Delphi.

[ Parent | on HN ]

Re:Go + Services = One Goliath Project by cle on Saturday December 21, 2019 @06:49PM (#21854055)

Dynamic languages (so you can hack together stuff and quickly bypass any roadblocks), with REPLs (quick feedback and avoiding writing tests), and low cognitive overhead (so new folks can ramp up quickly).

Some example languages that come to mind here: Python, Ruby, JavaScript, Clojure, Groovy.

Go actually comes close here, even though it doesn't have a REPL and isn't very dynamic, because of its focus on minimizing cognitive overhead and getting the job done with minimal fuss.

Other languages carry a lot of community baggage. Java is one of the worst IMO...if you try to hire Java programmers, it's going to take a lot of effort and risk to find and reject applicants who've read too many design pattern books, are architecture astronauts, or come from an enterprise-y background. The signal-to-noise ratio is just really poor.

[ Parent | on HN ]

Re:Go + Services = One Goliath Project by AtlasBarfed on Monday December 23, 2019 @11:07PM (#21869774)

Rubys devs said the same thing about Java when Rails first came out.

Now look at Ruby, its stack is gigantic and cumbersome.

I guess Go will try to resist that, but over time Go will become burdened with a huge stack of outmoded software.

[ Parent | on HN ]