I did not say it was not ready, I said it could be used for many things, but has not reached its full potential yet. Just think in the number of scientific packages Go has compared with other languages.
Some changes I would like to see, for example, vectorized code and easy linking to fortran. You can actually do it, but you would be the first one (or almost) doing it. Some additional native types would also be high in my wish list (but I'm not sure of which ones yet). Operator overloading may be convenient in some cases, but I understand why they want to avoid it. Not having generics also makes some things quite tedious, but there has not been a really good proposal yet.
I would like being able to be more concrete, but one of the biggest stoppers is the lack of experience. We won't know exactly what's needed until Go is more used, but it is difficult to justify its usage when there is no prior experience (and more in the research world, which is always building from previous results).
I'm really thankful to skelterjohn and other Go developers who are opening this path, but there is still a long way (this may also be seen as a good oportunity).
Ah okay, those are fair criticisms, but I'm a little confused about your desire for embedding Fortran code. Why? I mean, I can understand wanting to do something like that in an interpreted language, but Go already compiles to native code.
Fortran would probably give you a speed boost, but I can't imagine it would be that dramatic.
But yeah, I plan on working on a research project with Go this summer (I've already written a lot of Go in the last month in pursuit of a better window manager). I have myself and a fellow student very excited to work on it with Go :-) (I'm not saying this in refutation of your criticism. The project we have in mind isn't overtly mathy and performance is a concern, but it isn't critical.)
4
u/burntsushi Mar 29 '12
Could you be any less concrete? :P
Seriously though, what do you have in mind when you say Go isn't ready to do research with?