The Node ecosystem still has tooling problems

Re:The Node ecosystem still has tooling problems by inopinatus on Sunday July 31, 2022 @06:16AM (#32294565)

This isn’t merely about tools. They’re one piece of a much larger puzzle. The fragmented chaos of the Node ecosystem arising from that aforementioned ephemerality ensures that eighteen months is roughly the duration before bitrot of dependencies is corrosive enough to have folks talking about rewrites. In four decades driving keyboards in various capacities, I’ve never seen any language experience dependency rot in production apps so rapidly as JavaScript and its offspring.

Aside: any shop operating under the assumption that devops is a function you assign to someone, has already failed devops 101.

[ Parent | on HN ]

Re:The Node ecosystem still has tooling problems by engmgrmgr on Wednesday August 03, 2022 @12:01AM (#32327524)

I genuinely don’t believe you’re coming at this from a business stakeholder POV, which is fair for HN. But if you have to advocate for a devops org outside of some massive global scale or as a small % of revenue, you’re doing something wrong.

Unfortunately a proven playbook for struggling devops teams is to just fire all the devops and infra folks, which seems to help with platform stability, recruiting, and velocity year over year.

[ Parent | on HN ]

Re:The Node ecosystem still has tooling problems by inopinatus on Wednesday August 03, 2022 @08:41AM (#32330908)

Your opening assumption is false. I start and run businesses.

Any reference to “devops team” is also automatically failing at devops. It’s not a job, a task, or a team. I don’t spare much time for folks encumbered by a silo mindset. It’s the antithesis of a service/product-team approach, and (to the actual point) does nothing to oppose the myopia I’m accusing the JS ecosystem of.

[ Parent | on HN ]