Live data from Hacker News

From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience

shopify.engineering

91–100 of 109 posts

Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience

#91
post #87

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.

We’ve been using Go since 2013. We recently started using Rust, but it’s mainly eating away at Go’s usage rather than Ruby’s. Ruby continues to be our first-choice language for most problems.

Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience

#93
post #72

Earlier 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.

It's not that bad - it's more of a meme than anything else as long as your sensible. Personally I dislike how Golang handles local packages. I'd rather use Typescript than Haskell in production!

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…

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 part of the dev cycle, producing binaries for distribution, and it's introduced just enough friction that people no longer make the little tweaks that used to be dead simple. Say what you will about loosey-goosey dynamic languages, but they work superbly for things like CLI tools.

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…

[deleted]

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…

Is golang really that easy to get started with?

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…

Ruby is a powerful language and its frameworks try to magically solve a lot of boring problems for you. I see “fewer … inclined to contribute” and I think they did or could learn the language but aren’t eager to spend so much more time on handwritten grunt work. (At least that’s my own attitude.)

Re: From Ruby to Node: Overhauling Shopify’s CLI for a better developer experience

#99
post #72

Earlier 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.

[dead]

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…

I haven't used Bazel for CLI apps and may have significantly underestimated how much other complexity they have around their deployment processes. That said, it's also very possible and common to make Node apps a pain to work on and distribute, too.
Post reply on HN