4 ms·

I don't understand going from Ruby to JS. Go or Rust sure, but Node for CLI? What is gained by doing that lateral move?

aliqot 4y ago
Developers who'll work right out of school, is my guess. Rails is great for the people who used it during that generation, and still is, I'm told. JS offers cheaper and more plentiful talent, and doesn't require as big of a mind shift as rust. If they become more JS centric, given the overlap in JS and Rust ideology, I could absolutely see them involving Rust soon after.
- kenhwang 4y ago
  If that's true that a company as big and established as Shopify can't afford to attract, onboard, and train ruby devs, it really feels like the beginning of the end for ruby.
  - aliqot 4y ago
    Ruby will be fine, this is more of an impact on Rails as the centerpiece for getting-to-MVP fastest. It once was the case, and might still be in some capacity, but everyone with that expertise is on years 10-15 in their career and don't come so cheap because they've put in the work to earn more and are well within their rights to say they aren't going to work all nighters.
    - AlchemistCamp 4y ago
      I wouldn’t say that at all. I know several successful indiehacker types who started in the past five years and have had success with Rails. Several of them started with JS first, but Ruby is still growing on an absolute basis, despite having a smaller portion of the market as a whole than it did a decade ago. I suspect a part of this is that startups that use Rails (or Phoenix or Laravel) don’t need as many devs as startups doing a mix and match of many libraries instead of a full stack web framework.
  - chillfox 4y ago
    I don't think this has anything to do with what they can afford at all. More like someone in leadership thinks Node is cool and collected a bunch of unvalidated reasons to support it.
wiseowise 4y ago
Tooling is much better, for starters. And they plan to use TS, not JS, did you even read the article?
- mperham 4y ago
  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.
  - eddsh1994 4y ago
    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!
  - wiseowise 4y ago
    [dead]
andrejguran 4y ago
it's in the article: "Hydrogen developers expect the npm install command to resolve all the dependencies that they need to work on a project. With Ruby as a dependency, that mental model breaks and they can easily run into issues where the CLI refuses to run because of additional steps needed."
- lamontcg 4y ago
  If the bulk of their cli users are already node users/devs then that actually makes perfect sense.

Developers who'll work right out of school, is my guess. Rails is great for the people who used it during that generation, and still is, I'm told. JS offers cheaper and more plentiful talent, and doesn't require as big of a mind shift as rust. If they become more JS centric, given the overlap in JS and Rust ideology, I could absolutely see them involving Rust soon after.

kenhwang 4y ago
If that's true that a company as big and established as Shopify can't afford to attract, onboard, and train ruby devs, it really feels like the beginning of the end for ruby.
- aliqot 4y ago
  Ruby will be fine, this is more of an impact on Rails as the centerpiece for getting-to-MVP fastest. It once was the case, and might still be in some capacity, but everyone with that expertise is on years 10-15 in their career and don't come so cheap because they've put in the work to earn more and are well within their rights to say they aren't going to work all nighters.
  - AlchemistCamp 4y ago
    I wouldn’t say that at all. I know several successful indiehacker types who started in the past five years and have had success with Rails. Several of them started with JS first, but Ruby is still growing on an absolute basis, despite having a smaller portion of the market as a whole than it did a decade ago. I suspect a part of this is that startups that use Rails (or Phoenix or Laravel) don’t need as many devs as startups doing a mix and match of many libraries instead of a full stack web framework.
- chillfox 4y ago
  I don't think this has anything to do with what they can afford at all. More like someone in leadership thinks Node is cool and collected a bunch of unvalidated reasons to support it.

wiseowise 4y ago

Tooling is much better, for starters. And they plan to use TS, not JS, did you even read the article?

mperham 4y ago
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.
- eddsh1994 4y ago
  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!
- wiseowise 4y ago
  [dead]

andrejguran 4y ago

it's in the article: "Hydrogen developers expect the npm install command to resolve all the dependencies that they need to work on a project. With Ruby as a dependency, that mental model breaks and they can easily run into issues where the CLI refuses to run because of additional steps needed."

lamontcg 4y ago
If the bulk of their cli users are already node users/devs then that actually makes perfect sense.