5 ms·

I find it interesting that many high profile "noders" have switched to Go (example [0]), but now its very creator? Wow! As someone who's switched from (C++/Jav

by simi_ 12y ago

I find it interesting that many high profile "noders" have switched to Go (example [0]), but now its very creator? Wow! As someone who's switched from (C++/Java to) node to (Python then) Go, I can understand where they're coming from though. 0: https://github.com/tj https://github.com/tj

lumpypua 12y ago
Where are they coming from? Javascript seems like the future, not Go (speaking as a python engineer).
- brianshaler 12y ago
  To me, they both sound like they are the future. They play different roles and have different strengths. A project like v8worker sounds exciting to me because we could use both in an application and get the best of both worlds.
- themartorana 12y ago
  This feels, apologies, slightly uninformed. JS obviously has a bright near-term future with so many engineers working on the runtime side, from Google, Mozilla, etc. But the speed at which Go has been picked up - especially by high-traffic, massively-concurrent systems and companies like Google (obviously), Cloudflare, 6Wunderkinder, BBC, bitbucket, Digital Ocean, Disqus, Dropbox, ngmoco:), Heroku, Shopify, Tumblr, Zynga... I realize a list doesn't a language make, (and these are just off the top of my head) but for each of these companies Go sits at the heart of the most mission-critical systems, often for extremely fast injection and analysis of huge data streams. (Funny enough, many come from a Python core, like Disqus and Dropbox, among others). I don't think Go's splash was as big as node's, but it's found its way in to more organizations than not.
  - jsprogrammer 12y ago
    My problem with Go is the seeming masses of boilerplate in all the Go code I've seen. With ES2015 (and beyond) I can write clean code with little syntactical boilerplate in a highly functional style that can run anywhere. The only thing really missing at this point is well integrated static type checking. I feel the code should be typed, but invisible, through type inference and propagation.
  - KMag 12y ago
    > I don't think Go's splash was as big as node's, but it's found its way in to more organizations than not. I'm having trouble understanding the second half of this statement. The two most clear readings are that over 50% of organizations use Go, or that over 50% of the organizations that have used Node now use Go (while still possibly also using Node). I doubt you intended either of these meanings. How am I misreading you? EDIT: do you perhaps mean that over 50% of the organizations that use Node and have experimented with Go have decided to move forward with more Go projects?
    - ChikkaChiChi 12y ago
      I think the statement themartorana is probably contextually inaccurate. That being said, there are plenty of stories coming out about how companies are evaluating Go and seeing performance increases in mission critical application; as opposed to stories of people ripping out pieces of Go and replacing it with something more optimal for their situation.
      - themartorana 12y ago
        ...is probably contextually inaccurate. Yup, those should have been two separate statements: 1. Node made a bigger initial splash than go 2. A large number of organizations that deal with high-volume, highly-concurrent data sets and API traffic are either in production with Go, or are experimenting with it. (All the companies I mentioned have Go in production)
- tim333 12y ago
  Quoting TJ Holowaychuk: "I’ve been fighting with Node.js long enough in production now that I don’t enjoy working with it anymore unfortunately" "In the past week I’ve rewritten a relatively large distributed system in Go, and it’s robust, performs better, it’s easier to maintain, and has better test coverage since synchronous code is generally nicer and simpler to work with." https://news.ycombinator.com/item?id=7987216 https://news.ycombinator.com/item?id=7987216
meowface 12y ago
It feels weird knowing I will never be 5% as productive as TJ is. (At least not without amphetamines or something.)
FractalNerve 12y ago
That's super interesting, I didn't know that he took a journey from C++ → Java → Python → Javascript → Go. But Why Go? [1] There are so many interesting programming languages, I'm curious why he chose go. And where do you have your information about high-profile Node.js users migrating to Go, if I may ask. I've not used the go language yet, but a school friend was a fan of it a few years (3?) ago and started learning it. He was positive with about it, but went on with life and uses php and nodejs mainly now. However can't wait for an ArchLinux PKGFILE :) -- [1] Faithless Feat Estelle - Why Go https://vimeo.com/20690331 https://vimeo.com/20690331

by simi_ 12y ago

lumpypua 12y ago

Where are they coming from? Javascript seems like the future, not Go (speaking as a python engineer).

brianshaler 12y ago
To me, they both sound like they are the future. They play different roles and have different strengths. A project like v8worker sounds exciting to me because we could use both in an application and get the best of both worlds.
themartorana 12y ago
This feels, apologies, slightly uninformed. JS obviously has a bright near-term future with so many engineers working on the runtime side, from Google, Mozilla, etc. But the speed at which Go has been picked up - especially by high-traffic, massively-concurrent systems and companies like Google (obviously), Cloudflare, 6Wunderkinder, BBC, bitbucket, Digital Ocean, Disqus, Dropbox, ngmoco:), Heroku, Shopify, Tumblr, Zynga... I realize a list doesn't a language make, (and these are just off the top of my head) but for each of these companies Go sits at the heart of the most mission-critical systems, often for extremely fast injection and analysis of huge data streams. (Funny enough, many come from a Python core, like Disqus and Dropbox, among others). I don't think Go's splash was as big as node's, but it's found its way in to more organizations than not.
- jsprogrammer 12y ago
  My problem with Go is the seeming masses of boilerplate in all the Go code I've seen. With ES2015 (and beyond) I can write clean code with little syntactical boilerplate in a highly functional style that can run anywhere. The only thing really missing at this point is well integrated static type checking. I feel the code should be typed, but invisible, through type inference and propagation.
- KMag 12y ago
  > I don't think Go's splash was as big as node's, but it's found its way in to more organizations than not. I'm having trouble understanding the second half of this statement. The two most clear readings are that over 50% of organizations use Go, or that over 50% of the organizations that have used Node now use Go (while still possibly also using Node). I doubt you intended either of these meanings. How am I misreading you? EDIT: do you perhaps mean that over 50% of the organizations that use Node and have experimented with Go have decided to move forward with more Go projects?
  - ChikkaChiChi 12y ago
    I think the statement themartorana is probably contextually inaccurate. That being said, there are plenty of stories coming out about how companies are evaluating Go and seeing performance increases in mission critical application; as opposed to stories of people ripping out pieces of Go and replacing it with something more optimal for their situation.
    - themartorana 12y ago
      ...is probably contextually inaccurate. Yup, those should have been two separate statements: 1. Node made a bigger initial splash than go 2. A large number of organizations that deal with high-volume, highly-concurrent data sets and API traffic are either in production with Go, or are experimenting with it. (All the companies I mentioned have Go in production)
tim333 12y ago
Quoting TJ Holowaychuk: "I’ve been fighting with Node.js long enough in production now that I don’t enjoy working with it anymore unfortunately" "In the past week I’ve rewritten a relatively large distributed system in Go, and it’s robust, performs better, it’s easier to maintain, and has better test coverage since synchronous code is generally nicer and simpler to work with." https://news.ycombinator.com/item?id=7987216 https://news.ycombinator.com/item?id=7987216

meowface 12y ago

It feels weird knowing I will never be 5% as productive as TJ is. (At least not without amphetamines or something.)

FractalNerve 12y ago

That's super interesting, I didn't know that he took a journey from C++ → Java → Python → Javascript → Go. But Why Go? [1] There are so many interesting programming languages, I'm curious why he chose go. And where do you have your information about high-profile Node.js users migrating to Go, if I may ask. I've not used the go language yet, but a school friend was a fan of it a few years (3?) ago and started learning it. He was positive with about it, but went on with life and uses php and nodejs mainly now. However can't wait for an ArchLinux PKGFILE :) -- [1] Faithless Feat Estelle - Why Go https://vimeo.com/20690331 https://vimeo.com/20690331