3 Matching Annotations
- Sep 2021
Webpacker used to configure Webpack indirectly, which lead to a complicated secondary configuration process. This was done in order to provide default configurations for the most popular frameworks, but ended up creating more complexity than it cured. So now Webpacker delegates all configuration directly to Webpack's default configuration setup.
more trouble than it's worth
- creating more complexity than it cured
- doing more harm than good
- Why can't this be easier/simpler? Why does it have to be so hard/complicated?
- more trouble than it's worth
- changed their mind/opinion
- too complicated
- newer/better ways of doing things
- removing feature that is more trouble than it's worth (not worth the effort to continue to maintain / fix bugs caused by keeping it)
- too hard/complicated/non-trivial
- Feb 2021
compose(Add, x: x, y: 3)
How is this better than simply:
Add.run(x: x, y: 3)
I guess if we did that we would also have to remember to handle merging errors from that outcome into self...
Why is all this interaction code better? Two reasons: One, you can reuse the FindAccount interaction in other places, like your API controller or a Resque task. And two, if you want to change how accounts are found, you only have to change one place.
Pretty weak arguments though...
- We could just as easily used a plain object or module to extract this for easy reuse and having it in only one place (avoiding duplication).