3 ms·
Reporting quite a similar experience as Daniel Whitenack spoke about, in his GopherCon talk about Go for Data Science: https://www.youtube.com/watch?v=D5tDubyX
by samuell 10y ago
Reporting quite a similar experience as Daniel Whitenack spoke about, in his GopherCon talk about Go for Data Science:
https://www.youtube.com/watch?v=D5tDubyXLrQ https://www.youtube.com/watch?v=D5tDubyXLrQ
See also his answers to some follow-up questions:
http://www.datadan.io/common-go-for-data-science-questions/ http://www.datadan.io/common-go-for-data-science-questions/
... and his O'Reilly article on the topic:
https://www.oreilly.com/ideas/data-science-gophers https://www.oreilly.com/ideas/data-science-gophers
- willtim 10y agoHow could Go possibly be anything but a inappropriate choice? For numerics and working with data, Go would be about as expressive as Fortran or C, but slower. I took a quick look at Gonum, it's highly imperative and monomorphic just like Fortran. It makes me sad that these efforts could be spent improving the ecosystems of Haskell/OCaml/F#/Scala. These languages are far more expressive than Go and offer far more type-safety, all with the succinctness of Python