Why Go is doomed to succeed

Re:Why Go is doomed to succeed by gnuvince on Saturday June 13, 2015 @12:43PM (#9711568)

Not the parent, but I've read many comments here on HN from users who feel that if a language doesn't include an HTTP server in the standard library, it's not ready for production work. Ridiculous, of course, but that may be what the parent is referring to.

[ Parent | on HN ]

Re:Why Go is doomed to succeed by hyperpape on Saturday June 13, 2015 @12:52PM (#9711606)

Does Java meet the criterion you're describing here?

[ Parent | on HN ]

Re:Why Go is doomed to succeed by pjmlp on Sunday June 14, 2015 @04:27AM (#9714201)

You mean like this?

http://docs.oracle.com/javase/6/docs/jre/api/net/httpserver/...

[ Parent | on HN ]

Re:Why Go is doomed to succeed by coldtea on Saturday June 13, 2015 @12:59PM (#9711644)

JavaEE sure does.

[ Parent | on HN ]

Re:Why Go is doomed to succeed by hyperpape on Saturday June 13, 2015 @02:42PM (#9712090)

Certainly. I guess I'm not sure if I should call it the standard library or not (and if I should care whether I call it that).

[ Parent | on HN ]

Re:Why Go is doomed to succeed by pjmlp on Sunday June 14, 2015 @04:26AM (#9714197)

Java SE also does include one since Java 6, but people don't read documentation it seems.

http://docs.oracle.com/javase/6/docs/jre/api/net/httpserver/...

[ Parent | on HN ]

[deleted]

Re:Why Go is doomed to succeed by steveklabnik on Saturday June 13, 2015 @01:19PM (#9711725)

There's a funny story here about how Rails had to keep some patches around because Heroku users were accidentally using WEBrick in production because of defaults...

[ Parent | on HN ]