3 ms·

It's not React itself that consumes time. On the contrary, React reduces the time it takes to develop UIs. Sometimes drastically. What sucks is everything that

It's not React itself that consumes time. On the contrary, React reduces the time it takes to develop UIs. Sometimes drastically. What sucks is everything that surrounds React, or all other SPA frameworks for that matter. For instance, every time I end up having to deal with Webpack et al, I want to put a gun in my mouth and pull the trigger.

ehnto 10y ago
Managing tooling and dependencies is the worst part of modern front end work. I don't see why we have to weave such a complex dependency tree and asset pipeline. Every project does it differently too, so you end up relearning the same tool with a different name and in different configurations. Too bad if the previous developer didn't commit the dependency manager manifests or task runner file too, you can't reverse engineer an asset pipeline if all that's left is CSS and raw JS. If anything goes wrong, you end up chasing issues through half a dozen abstractions you had never heard of. I can't keep all of this plus my actual project requirements in my head. Let me write some darn code already!
- thewhitetulip 10y ago
  Yes, especially the notorious npm which is hell bent on installing the entire Internet when I do npm install. God knows what and why it installs the things it does
  - eatonphil 10y ago
    Facebook's yarn [0] is a drop-in replacement for 'npm install' that significantly improves install times. Really makes me wonder what npm install is doing. [0] https://github.com/yarnpkg/yarn https://github.com/yarnpkg/yarn
    - dictum 10y ago
      > Really makes me wonder what npm install is doing Pattern matching. For every dependency listed in package.json, npm install downloads and tests every JSON payload publicly available on the Internet until it finds one that produces the desired npm package.
    - raarts 10y ago
      I don't think parent was complaining about install times.

ehnto 10y ago

Managing tooling and dependencies is the worst part of modern front end work. I don't see why we have to weave such a complex dependency tree and asset pipeline. Every project does it differently too, so you end up relearning the same tool with a different name and in different configurations. Too bad if the previous developer didn't commit the dependency manager manifests or task runner file too, you can't reverse engineer an asset pipeline if all that's left is CSS and raw JS. If anything goes wrong, you end up chasing issues through half a dozen abstractions you had never heard of. I can't keep all of this plus my actual project requirements in my head. Let me write some darn code already!

thewhitetulip 10y ago
Yes, especially the notorious npm which is hell bent on installing the entire Internet when I do npm install. God knows what and why it installs the things it does
- eatonphil 10y ago
  Facebook's yarn [0] is a drop-in replacement for 'npm install' that significantly improves install times. Really makes me wonder what npm install is doing. [0] https://github.com/yarnpkg/yarn https://github.com/yarnpkg/yarn
  - dictum 10y ago
    > Really makes me wonder what npm install is doing Pattern matching. For every dependency listed in package.json, npm install downloads and tests every JSON payload publicly available on the Internet until it finds one that produces the desired npm package.
  - raarts 10y ago
    I don't think parent was complaining about install times.