Earlier quoted context omitted.
Besides this article, what gives you that impression?
I seem to recall reading recently that Go was showing up in their org. May be mistaken or misremembering.
From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
91–100 of 109 posts
Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#92Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#93Earlier quoted context omitted.
Tooling is much better, for starters. And they plan to use TS, not JS, did you even read the article?
Let me get this straight: you believe that Node's tooling is better than Golang's tooling? The entire Node ecosystem is commonly described as a dumpster fire.
Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#94I don't know why they switched, but I haven't used ruby on rails that much.
Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#95> ”Go and Rust allow distributing a static binary, but at the cost of fewer people at Shopify being inclined to contribute due to the lack of familiarity with the language.” If learning a language as simple as Golang is a real barrier for Shopify engineers, then I’d say they need to reevaluate their hiring processes. Especially given that they’re talking about CLI apps as opposed to something like distributed systems…
Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#96> ”Go and Rust allow distributing a static binary, but at the cost of fewer people at Shopify being inclined to contribute due to the lack of familiarity with the language.” If learning a language as simple as Golang is a real barrier for Shopify engineers, then I’d say they need to reevaluate their hiring processes. Especially given that they’re talking about CLI apps as opposed to something like distributed systems…
I work somewhere with plenty smart engineers, and plenty of in-house golang expertise. I've seen several small internal tools rewritten from Python to Go, and contributions by the wider team totally dropped off. It used to be absolutely trivial for anyone to make changes, and the "deployment" of such scripts was basically "get the code reviewed and merge it." Now there's a whole Bazel song and dance, compilation as p…
Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#97> ”Go and Rust allow distributing a static binary, but at the cost of fewer people at Shopify being inclined to contribute due to the lack of familiarity with the language.” If learning a language as simple as Golang is a real barrier for Shopify engineers, then I’d say they need to reevaluate their hiring processes. Especially given that they’re talking about CLI apps as opposed to something like distributed systems…
Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#98> ”Go and Rust allow distributing a static binary, but at the cost of fewer people at Shopify being inclined to contribute due to the lack of familiarity with the language.” If learning a language as simple as Golang is a real barrier for Shopify engineers, then I’d say they need to reevaluate their hiring processes. Especially given that they’re talking about CLI apps as opposed to something like distributed systems…
Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#99Earlier quoted context omitted.
Tooling is much better, for starters. And they plan to use TS, not JS, did you even read the article?
Let me get this straight: you believe that Node's tooling is better than Golang's tooling? The entire Node ecosystem is commonly described as a dumpster fire.
Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience
#100> ”Go and Rust allow distributing a static binary, but at the cost of fewer people at Shopify being inclined to contribute due to the lack of familiarity with the language.” If learning a language as simple as Golang is a real barrier for Shopify engineers, then I’d say they need to reevaluate their hiring processes. Especially given that they’re talking about CLI apps as opposed to something like distributed systems…
I work somewhere with plenty smart engineers, and plenty of in-house golang expertise. I've seen several small internal tools rewritten from Python to Go, and contributions by the wider team totally dropped off. It used to be absolutely trivial for anyone to make changes, and the "deployment" of such scripts was basically "get the code reviewed and merge it." Now there's a whole Bazel song and dance, compilation as p…