News for hackers. Stuff that matters.
Re:The Cost of JavaScript by megaman22 on Wednesday November 15, 2017 @03:53PM (#15707644)
> No fighting with headers, include paths, linker options, make files , cmake files, scons files, etc

Instead you get to fight with often poorly-versioned bower/npm dependency hell, and gulp/grunt/webpack config errors with inscrutable messages.

> having to fight the dev tools on each platform which seem to change every 5 years such that all old samples fail.

Such stability! If anything in javascript still works five months later, I count my lucky stars.

Re:The Cost of JavaScript by jeeberz on Wednesday November 15, 2017 @04:04PM (#15707768)
I hear you but since I've been using yarn to lock all package versions I haven't had any issues.

https://yarnpkg.com/lang/en/docs/yarn-lock/

JS development without yarn is complete madness.

Re:The Cost of JavaScript by merb on Wednesday November 15, 2017 @05:26PM (#15708481)
which means that you do not use a npm proxy.
Re:The Cost of JavaScript by aprdm on Wednesday November 15, 2017 @08:58PM (#15709747)
You can just build a RPM package with your dependencies and another with the dist result.

We have something like that,

node_modules for some project goes to a rpm called $project_name-devel

and the result goes to $project_name

Is not really that complicated and then we don't rely on anything outside of our control (e.g: github, npm)

We never had an issue with this workflow. Our dependencies (the devel package) changes maybe once every two months if so?