News for hackers. Stuff that matters.
Re:Writing Web Applications in Go by eropple on Sunday March 03, 2013 @01:05PM (#5314573)
> I would not write a wiki app in it, but certainly the next Apache or Nginx replacement.

I wouldn't. Nondeterministic garbage collection in a web server like nginx (as opposed to an application web server like Jetty) makes me very nervous. The HTTP (or pick-your-other-TCP-protocol) lifecycle is well-understood enough that you should be able to handle your own memory management.

There are lots of things in Go I like, but for me they're coupled with questionable abstractions that make it difficult to rationalize over C++.

Re:Writing Web Applications in Go by meaty on Sunday March 03, 2013 @01:17PM (#5314612)
Actually Go GC is quite easy to control. If you know your butt from your elbow you can write code that doesn't GC at all.

I really don't have a problem with GC though. Its easier to optimise a GC than to fix memory and reference counting bugs. Memory management is not a problem I want to be dealing with after 60-odd years of computers being around.

Re:Writing Web Applications in Go by pcwalton on Sunday March 03, 2013 @01:37PM (#5314694)
Garbage collection is not the only way to achieve safe memory management.
Re:Writing Web Applications in Go by meaty on Sunday March 03, 2013 @02:41PM (#5314966)
Agreed but its the one way which requires little headspace when solving a problem.
Re:Writing Web Applications in Go by eropple on Sunday March 03, 2013 @10:24PM (#5316393)
I find RTTI to require fairly little cognitive load and I don't find resolving memory ownership to be particularly difficult.
Re:Writing Web Applications in Go by meaty on Tuesday March 05, 2013 @06:56AM (#5324004)
Yuck. RTTI is C++'s goto.
Re:Writing Web Applications in Go by eropple on Tuesday March 05, 2013 @10:40PM (#5329176)
Er, sorry. I didn't proof the past. Meant RAII. My bad.
Re:Writing Web Applications in Go by eropple on Sunday March 03, 2013 @05:54PM (#5315570)
> Its easier to optimise a GC than to fix memory and reference counting bugs.

I don't agree. If you are competent enough to be needing to write your own web server, memory management should be utterly trivial.

There are many use cases where you do not need to really balance bleeding performance against programmer conveniences. Something like "Apache or nginx" is without question one of them.

Re:Writing Web Applications in Go by meaty on Monday March 04, 2013 @11:06AM (#5318832)
Agree with Apache/nginx etc, but that is nowhere anyone needs to piddle around these days.
Re:Writing Web Applications in Go by eropple on Monday March 04, 2013 @11:30AM (#5318952)
Except that that's exactly what I was replying to: "Apache or Nginx replacement".