4 ms·
> No fighting with headers, include paths, linker options, make files , cmake files, scons files, etc Instead you get to fight with often poorly-versioned bowe
by megaman22 9y ago
> 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.
- jeeberz 9y agoI 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/ https://yarnpkg.com/lang/en/docs/yarn-lock/ JS development without yarn is complete madness.
- merb 9y agowhich means that you do not use a npm proxy.
- aprdm 9y agoYou 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?