3 ms·

It's web focused? In 2015, your new language needs to have some web stuff built into the standard library or at least some foundation libraries. I don't know

It's web focused? In 2015, your new language needs to have some web stuff built into the standard library or at least some foundation libraries. I don't know that that makes it web focused though. Seems like there is a huge cultural gap or something, Go was initially built by real-deal C guys. There is a ton of overlap with them and like the plan-9 and suckless fans. If you're not doing hard-realtime or poking registers, it very very much looks like a language designed to fix the problems C has. Just about any of the standard UNIX tools could fairly easily be built in Go and probably be cleaner, maybe more bug free. When the go compiler and run-times are optimized up and the performance is there, it seems like you'd really need a compelling argument to not write those kinds of tools in Go instead of C. If you really dive in to the plan-9 and suckless stuff, how many of those programs legitimately have more than a couple data-structures? They are small, they do one thing, they try to do it well. There are a lot of "missing" things that they aren't urgent the replace because of that, like dynamic linking... What's really amazing is that it has been drawing the ruby, js and python guys in. And generics is a/"The Big" hangup? Why not just the fact that you actually have to compile it or that the compiled product has an OS and hardware requirement.

laumars 12y ago
>It's web focused? Web-focused is a poor choice of words on my part. But IIRC Google adopted the project as a means to speed up development and execution time for their web services back ends (if that's wrong then I'll happily welcome a correction). Either way, Go does have a presence in web development - not least of all by Google > What's really amazing is that it has been drawing the ruby, js and python guys in. And generics is a/"The Big" hangup? Why not just the fact that you actually have to compile it or that the compiled product has an OS and hardware requirement. Only the compiled binary is OS dependant, the code is just as portable as your exampled languages. And the only hardware requirement is the word size and architecture of the CPU - which for web development would nearly always be x86_64. Plus Go makes cross-compiling child's play - so there's no issues with compiling for another CPU architecture (if, for some reason, you're targeting ARM over x86) or for 32bit platforms, Windows, FreeBSD, OS X or Linux. I actually think the fact that Go needs compiling is a real strength of Go. Unit and regression testing of websites can be painful in JIT compiled, dynamic languages; where as go build catches a lot of developer "absent-mindedness" before the web application even reaches the testing phase. Obviously compiling isn't going to catch everything, but in my experience, it has massively streamlined the process of developing production ready code.

laumars 12y ago

>It's web focused? Web-focused is a poor choice of words on my part. But IIRC Google adopted the project as a means to speed up development and execution time for their web services back ends (if that's wrong then I'll happily welcome a correction). Either way, Go does have a presence in web development - not least of all by Google > What's really amazing is that it has been drawing the ruby, js and python guys in. And generics is a/"The Big" hangup? Why not just the fact that you actually have to compile it or that the compiled product has an OS and hardware requirement. Only the compiled binary is OS dependant, the code is just as portable as your exampled languages. And the only hardware requirement is the word size and architecture of the CPU - which for web development would nearly always be x86_64. Plus Go makes cross-compiling child's play - so there's no issues with compiling for another CPU architecture (if, for some reason, you're targeting ARM over x86) or for 32bit platforms, Windows, FreeBSD, OS X or Linux. I actually think the fact that Go needs compiling is a real strength of Go. Unit and regression testing of websites can be painful in JIT compiled, dynamic languages; where as go build catches a lot of developer "absent-mindedness" before the web application even reaches the testing phase. Obviously compiling isn't going to catch everything, but in my experience, it has massively streamlined the process of developing production ready code.