Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by masklinn on Thursday January 12, 2023 @04:21PM
(#34360405)
> Like someone at the top decided, now lets pretend it's a good decision.
It might not even be a top thing, if they migrated internal eng from Ruby to node internally I would not be surprised if this was dev-driven either
Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by kenhwang on Thursday January 12, 2023 @06:44PM
(#34361950)
Interesting how Shopify went from the most pro-ruby company to what looks like unreasonably rapid divestment from it. Wonder what's going on.
Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by ewalk153 on Thursday January 12, 2023 @07:29PM
(#34362365)
Ruby is still the primary backend language at Shopify. Node is popular amongst partners.
Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by organsnyder on Thursday January 12, 2023 @07:31PM
(#34362381)
Besides this article, what gives you that impression?
Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by scruple on Thursday January 12, 2023 @09:52PM
(#34363411)
I seem to recall reading recently that Go was showing up in their org. May be mistaken or misremembering.
Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by burke on Thursday January 12, 2023 @11:07PM
(#34363837)
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...
by scruple on Saturday January 14, 2023 @01:30PM
(#34382631)
Thanks for the clarification, I appreciate it!
Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by reillyse on Thursday January 12, 2023 @05:13PM
(#34361000)
That’s how I read the article too. We wanted to move from ruby to node. They even admit that the most well know language is ruby in their org. Seems like a pretty serious waste of resources to me.
Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by ljm on Thursday January 12, 2023 @07:11PM
(#34362203)
This might be the first article I've read where Node's module resolution algo is touted as a benefit.
Just how complex is your command line app if you need to have multiple transitive versions of the same library?
Coming from the same company that is so heavily invested in Ruby that they contributed to a new JIT for it (YJIT), built a static type checking layer (sorbet) for it, and built a module system that prevents you sharing code between those modules (packwerk), etc.
Unrelated but it is reminding me of my attempt to integrate with Zapier. Zapier doesn't document an API anywhere, you have to use its 'CLI app'. The CLI app of course just calls undocumented HTTP APIs behind the scenes.
Re:From Ruby to Node: Overhauling Shopify’s CLI for a Better...
by faitswulff on Friday January 13, 2023 @09:53PM
(#34376927)
Minor note, Sorbet was written at Stripe.
As you mentioned, if they're not OK with CLI, they could refactor in Ruby. The whole "embracing functional programming" and MVC architecture (i think Rails when i hear MVC) as reasons to go to Node and not Ruby is nuts.
If they were worried about dependencies, they'd us Rust or Go as they mentioned.