Live data from Hacker News

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

shopify.engineering

1–10 of 109 posts

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

#5

Heroku did the same

more background info

https://blog.herokuapp.com/evolution-of-heroku-cli-2008-2017 Their version 6, started with Ruby, then go/node, then pure node.

https://github.com/heroku/cli "This is the next generation Node-based Heroku CLI. The goals of this project were to make plugins more flexible, remove Ruby as a runtime dependency, and make the CLI faster. [...] It has identical functionality to the old Ruby CLI."

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

#7
post #5

Heroku did the same

more background info https://blog.herokuapp.com/evolution-of-heroku-cli-2008-2017 Their version 6, started with Ruby, then go/node, then pure node. https://github.com/heroku/cli "This is the next generation Node-based Heroku CLI. The goals of this project were to make plugins more flexible, remove Ruby as a runtime dependency, and make the CLI faster. [...] It has identical functionality to the old Ruby CLI."

The original article has no relation to Heroku, that's why the downvote.

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

#9
I'm begging you, just use a language that compiles to a single binary. It can self update in place, be easily installed on developer machines and CI pipelines without requiring a whole additional toolchain in every container. Google, Heroku, AWS, Shopify all do and it's an awful developer experience.

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

#10
Good luck! I've found any cli with any kind of runtime dependency other than maybe sh eventually becomes difficult to run. I think they all tend to end up getting packaged with an isolated copy (node/ruby/python) of whatever runtime they need.
Post reply on HN