I think the danger that nobody talks about is when you need to do something that the tool author didn't consider: if no thought is given to that case then "zero-conf" isn't worth it.
Fighting a build tool you can't replace is frustrating
.
-
-
-
I think create-react-app nails the above. It starts with zero config but with one command all the magic goes away and there's a ton of guiding comments.
-
True, but at the cost of having to maintain that stack in perpetuity with the possibility of not having upstream updates. Neutrino is zero-initial-config but still provides an API for dropping into low level and keep full extensibility of the build
-
That's the right thing :)
-
I'm not sure there is a "right thing". All tools have trade-offs. Declaring one the "winner" only discourages innovation.
-
I'm giving my opinion about the right style for building these tools. I don't think you need to worry that me giving my opinion about it is going stifle alternatives to my point of view ;)
-
Agreed, opinions are good, and stating tradeoffs is important because every decision involves one. For Neutrino, that tradeoff is a little more verbose low level API which isn't a 1:1 mapping to a webpack config object, but we feel the tradeoff is justified
End of conversation
New conversation -
-
-
Bonjour! How did they rendezvous to that meaning?
- 1 more reply
New conversation -
-
-
"Sane defaults"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.