News for hackers. Stuff that matters.
Re:Everyday hassles in Go by bojo on Tuesday December 30, 2014 @07:52AM (#8814359)
Go is the most boring language I have ever coded in, and that is why I love it. Sure, it doesn't have some fancy bells and whistles people seem to want, but when you can sit down and write something functional, portable, and readable fairly quickly, I'd say that is a huge win.
Re:Everyday hassles in Go by threeseed on Tuesday December 30, 2014 @09:42AM (#8814733)
You know you could replace "Go" with "Java 1.0" and your comment would still be accurate. Funny that.
Re:Everyday hassles in Go by NateDad on Tuesday December 30, 2014 @10:07AM (#8814850)
This is old and tired. Go has a ton of features java 1.0 didn't. Hell, go has features java 1.7 doesn't (possibly 1.8, but I'm not as familiar with it).
Re:Everyday hassles in Go by kasey_junk on Tuesday December 30, 2014 @10:44AM (#8815003)
Actually, it isn't the same argument as golang == java 1.0. It's java 1.0 had similar goals and made similar design choices that golang is making (and had similar responses from developers). In many ways this rings true. Java 1.0 and Golang do share many of the same goals.

A couple of areas where it really falls down though are that Java 1.0 lacked the emphasis on tooling which is golangs greatest strength and added a goal of "write once/run anywhere" which at the time seemed very important but now adds a lot of baggage.

Re:Everyday hassles in Go by NateDad on Tuesday December 30, 2014 @11:24AM (#8815200)
Kudos. That is perhaps the best reasoning I have ever seen for this comparison. I agree totally, though I don't think most people who make the comparison are thinking along the same lines. I think they generally just mean "compiled, GC, no generics".
Re:Everyday hassles in Go by nine_k on Tuesday December 30, 2014 @08:08AM (#8814401)
"Functional"? I suppose you meant "procedural" :)
Re:Everyday hassles in Go by seunosewa on Tuesday December 30, 2014 @08:18AM (#8814446)
Something that works.