News for hackers. Stuff that matters.
Re:Oracle and the fall of Java EE by shadowmint on Friday July 08, 2016 @10:55AM (#12055958)
I think the issue here is the hostility of the go community historically to pretty much any kind of criticism on pretty much any front.

(want generics? too bad! don't like the syntax for [thing]? too bad! want a framework? you're doing it wrong! want to test without using actual sending network traffic? BAM! 50 downvotes on SO for 'poor question'. Got some feedback and post it to golang nuts? HA! Prepare to be shouted out)

...but slowly we're seeing things move to a more moderate and mature state now where people are actually solving problems (like vendoring and SetDeadline()), rather than just pretending everything is ok, and building really good things with it, like go-kit.

It's just go growing up and being used seriously by people; but to be fair to the parent post, if you've used go in the past, I can see why you might have some opinions about it not being run by grown ups.

Worth having another look though. These days, it's pretty good.

Re:Oracle and the fall of Java EE by geodel on Friday July 08, 2016 @11:45AM (#12056312)
How did it become good? Has generics been added? or syntax changed? or framework comes bundled with Go? Seems all example you gave are some libraries being written which shouldn't be big deal.
Re:Oracle and the fall of Java EE by shadowmint on Friday July 08, 2016 @12:06PM (#12056500)
I'm talking about the community, which has tangibly improved.

There are also technical improvements (as I mentioned) and frameworks (as I mentioned). What more do you want?

Generics? No. You still can't have those.

Different syntax? No. You still can't have that.

...but maybe, now, if you go and talk to people about it, they won't flip the table about it, and you can have a conversation about it with folks on the gopher slack where everyone is reasonable and thoughtful both about legitimate concerns and future directions for change.

In my oppinion, that's a big deal...

Re:Oracle and the fall of Java EE by pkaye on Friday July 08, 2016 @12:16PM (#12056614)
Can you tell me what is the issue with SetDeadline()?
Re:Oracle and the fall of Java EE by shadowmint on Friday July 08, 2016 @09:00PM (#12059596)
There's no issue with deadlines; I'm talking about people using deadlines instead of just hanging forever in go routines, and how contexts have been merged in stdlib in 1.7 (https://blog.cloudflare.com/the-complete-guide-to-golang-net...)
Re:Oracle and the fall of Java EE by justinlardinois on Friday July 08, 2016 @03:01PM (#12057862)
Sounds like the Python community.
Re:Oracle and the fall of Java EE by coldtea on Friday July 08, 2016 @09:14PM (#12059623)
Not even close.