5 ms·
His basic point seems to be "use the right tool for the right job", which I think we all can agree with. I've been programming stuff in Go for about half a year
by jfaucett 14y ago
His basic point seems to be "use the right tool for the right job", which I think we all can agree with. I've been programming stuff in Go for about half a year now and I'd have to agree with the author - building a website in Go doesn't make much sense, for many of the same reasons building a website in c or java (for me the java process is too slow) doesn't make much sense. On the other hand, the concurrency model is excellent and for services, background processing, doing all kinds of intensive serverside lifting - i.e. traditional java application areas - Go, in my opinion, beats out java and is an excellent tool for the job.
- kkowalczyk 14y agoMy experience is the opposite. I build websites in Go. I find it about as easy as building in Python. Web programming is mostly about filling html templates with data and Go's built-in html template is excellent (on par with Django templates). Comparing Go to C for web dev is ridiculous - no sane person would write the whole thing in C. Even compared to Java Go wins by a huge margin when it comes to speed of development and conciseness of resulting code. I haven't used use Ruby but writing web services in Go I'm as productive as I was in Python (using App Engine or Tornado).
- salimmadjd 14y agoI'd be interested reading further on this. Can I encourage you to post a blog about it.
- stcredzero 14y agoWhat frameworks do you use for this?