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
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.
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
This is a strange and ahistorical take. Go was heavily discussed in 2009 after it was first announced by Google. It didn't go four years between public announcement in 2009 and people finally learning of it in 2013.
Major themes of discussion in 2009: Does it have generics and if not, why not? How does it compare to Erlang? And why did they reuse the name from this language Go! we all just heard about five minutes ago? https://news.ycombinator.com/item?id=936544 - from the day after the language was publicly revealed.
The first two topics (generics and how it compares to Erlang) are still discussed today, though the former is now mostly complaining that it has generics instead of complaining that it doesn't have generics.
Go was absolutely not mainstream in 200 fucking 9. When Flash dominated the web and everyone did Wordpress for websites. Nobody (at large) did Go before they did Node.
You are pointing to extremely early design discussions you absolute twat. Get real. Anyone who was active in their career in ~2013 knows that's exactly when Go came out.
I am from San Francisco and lived here my whole life - and it wasn't the epicenter of tech then (2013) but Mountain View sure as fuck was, and it's like 45m away and I would fucking know if Go was written in 2009 and it wasn't.
You're a liar. Go away
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:
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.
I don't doubt it has a searchable history back to 2010.
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.