4 ms·

Have you never heard of Node.js where they got the idea from

giancarlostoro 2mo ago
They were made roughly around the same time to be fair, but Go's standard library was richer at the time I thought? Even so, JavaScript hate it or love it (I both hate and love it) is massive by virtue of being the primary scripting language for front-end web. I am fully aware of its backend capabilities, but Go gave us: C-like syntax, natively compiled, and a rich OOTB standard library that Google uses in production. Even YouTube adopted Go early on and made Vitess which was a "middle-man" for MySQL which helped YouTube with their back-end starting in 2010, it would help with query routing and sharding, connection pooling, query safety and even optimizing queries before they got to MySQL, as well as row-level caching. Honestly I'm not trying to downplay Node, I respect Node for what it was and is, but Go punched above its weight early on too. I think the industry was starved for a back-end language that was simple, compiled natively (removing a lot of environmental setup overhead) and was production ready out of the box.
- purplemoonx 2mo ago
  Node.js came way before Go. If you fact-check with AI, it will say "Go was invented in 2009" but anyone who has been around knows it's more like ~2013. Node.js was 90% of the inspiration for Go to exist in the first place. Swift also would have never came about if it wasn't for people doing iOS way better in JavaScript. SwiftUI is basically React conceptually
  - giancarlostoro 2mo ago
    Technically 2007, but Go 1.0 was in 2009 when the Windows compiler was finally released, Go from 2007 till 2009 was Linux / Unix first. I don't recall when Mac came, but I would not be surprised if very quickly given that GCC worked just fine on Mac at the time. The Go community made Go work on Windows leading up to 2009, the core maintainers of Go did not make the Windows build themselves, they didn't care about Windows being a target. I say this to emphasize how quickly popular it became that it built up a community that wanted it to build for Windows, and they did. 2013 is when the rest of the world was starting to catch on to Go I suppose, Docker came out in 2013, but I distinctly remember learning Go on Windows in 2009 and building web apps, without any third party packages.
    - purplemoonx 2mo ago
      Haha, try 2013. You were not around then ;) Go 1.0 was released in 2013 (I don't even think the "official date" of March 28, 2012 is correct, or at least, nobody had heard of it). Apple doing Swift and Google doing Go was basically in response to Node.js > but I distinctly remember learning Go on Windows in 2009 and building web apps Very highly doubt it
      - giancarlostoro 2mo ago
        I mixed up when Go had its first release for windows and 1.0 but that somehow means I wasn't around for that? Thanks for knowing about my life more than I do somehow? My memory is not what it used to be but that doesn't invalidate my personal experiences in 2009. I started college in 2011 and I was telling the professors about it before it was popular, Vitess was in 2010, used in production by YouTube. JavaScript predates NodeJS even so. I did use Linux in 2009 so I could be misremembering when it was ported, after all this was over a decade and some change ago. Edit: https://go.dev/blog/1year https://go.dev/blog/1year My overall argument still stands, in production at YouTube by 2010, by 2013 we already had Docker in the works, when you say it "just came out" but many people were eyeballing Go and waiting for it to be fully on Windows. So 2010 they were talking about the Windows port, guess I blended the years a bit, everything before my college years is all smashed together for me.
        purplemoonx 2mo ago
        In 2010 I was doing Flash/AS3 (professionally) and Wordpress sites, but yeah, maybe. I don't doubt it has a searchable history back to 2010.
        giancarlostoro 2mo ago
        Anyway, my memory is pretty bad, the early 2010s are a blurb and sometimes I mix up 2009 with the early 2010s. I love JavaScript and hate it, because I know how quirky it is and can be, I'm glad something like Go and Node came along, we were all stuck with Java or C# (which arguably became a lot better in recent years). Now we've got many more options.

They were made roughly around the same time to be fair, but Go's standard library was richer at the time I thought? Even so, JavaScript hate it or love it (I both hate and love it) is massive by virtue of being the primary scripting language for front-end web. I am fully aware of its backend capabilities, but Go gave us: C-like syntax, natively compiled, and a rich OOTB standard library that Google uses in production. Even YouTube adopted Go early on and made Vitess which was a "middle-man" for MySQL which helped YouTube with their back-end starting in 2010, it would help with query routing and sharding, connection pooling, query safety and even optimizing queries before they got to MySQL, as well as row-level caching. Honestly I'm not trying to downplay Node, I respect Node for what it was and is, but Go punched above its weight early on too. I think the industry was starved for a back-end language that was simple, compiled natively (removing a lot of environmental setup overhead) and was production ready out of the box.

purplemoonx 2mo ago
Node.js came way before Go. If you fact-check with AI, it will say "Go was invented in 2009" but anyone who has been around knows it's more like ~2013. Node.js was 90% of the inspiration for Go to exist in the first place. Swift also would have never came about if it wasn't for people doing iOS way better in JavaScript. SwiftUI is basically React conceptually
- giancarlostoro 2mo ago
  Technically 2007, but Go 1.0 was in 2009 when the Windows compiler was finally released, Go from 2007 till 2009 was Linux / Unix first. I don't recall when Mac came, but I would not be surprised if very quickly given that GCC worked just fine on Mac at the time. The Go community made Go work on Windows leading up to 2009, the core maintainers of Go did not make the Windows build themselves, they didn't care about Windows being a target. I say this to emphasize how quickly popular it became that it built up a community that wanted it to build for Windows, and they did. 2013 is when the rest of the world was starting to catch on to Go I suppose, Docker came out in 2013, but I distinctly remember learning Go on Windows in 2009 and building web apps, without any third party packages.
  - purplemoonx 2mo ago
    Haha, try 2013. You were not around then ;) Go 1.0 was released in 2013 (I don't even think the "official date" of March 28, 2012 is correct, or at least, nobody had heard of it). Apple doing Swift and Google doing Go was basically in response to Node.js > but I distinctly remember learning Go on Windows in 2009 and building web apps Very highly doubt it
    - giancarlostoro 2mo ago
      I mixed up when Go had its first release for windows and 1.0 but that somehow means I wasn't around for that? Thanks for knowing about my life more than I do somehow? My memory is not what it used to be but that doesn't invalidate my personal experiences in 2009. I started college in 2011 and I was telling the professors about it before it was popular, Vitess was in 2010, used in production by YouTube. JavaScript predates NodeJS even so. I did use Linux in 2009 so I could be misremembering when it was ported, after all this was over a decade and some change ago. Edit: https://go.dev/blog/1year https://go.dev/blog/1year My overall argument still stands, in production at YouTube by 2010, by 2013 we already had Docker in the works, when you say it "just came out" but many people were eyeballing Go and waiting for it to be fully on Windows. So 2010 they were talking about the Windows port, guess I blended the years a bit, everything before my college years is all smashed together for me.
      - purplemoonx 2mo ago
        In 2010 I was doing Flash/AS3 (professionally) and Wordpress sites, but yeah, maybe. I don't doubt it has a searchable history back to 2010.
        giancarlostoro 2mo ago
        Anyway, my memory is pretty bad, the early 2010s are a blurb and sometimes I mix up 2009 with the early 2010s. I love JavaScript and hate it, because I know how quirky it is and can be, I'm glad something like Go and Node came along, we were all stuck with Java or C# (which arguably became a lot better in recent years). Now we've got many more options.