Live data from Hacker News

Show HN: Jetpack – Webpack made more convenient

github.com

21–30 of 79 posts

Re: Show HN: Jetpack – Webpack made more convenient

#21

Haven't looked deeper in it, but why does it happen all the time that people think they can fix complexity by adding another layer of complexity too it?

Perhaps because David J. Wheeler said "We can solve any problem by introducing an extra level of indirection."

Except too many levels of indirection...

Re: Show HN: Jetpack – Webpack made more convenient

#22

Earlier quoted context omitted.

Perhaps because David J. Wheeler said "We can solve any problem by introducing an extra level of indirection."

Except too many levels of indirection...

Just wrap it in an IndirectionManager and instantiate that via an IndirectionManagerFactory and you're good to go. :)

Re: Show HN: Jetpack – Webpack made more convenient

#23

Haven't looked deeper in it, but why does it happen all the time that people think they can fix complexity by adding another layer of complexity too it?

How else would you fix complexity if you don't want to reimplement something non-trivial? I guess its always a tradeoff: a more complex (or bigger, at any rate) implementation vs a slimmer/easier to use interface.

Re: Show HN: Jetpack – Webpack made more convenient

#24

Haven't looked deeper in it, but why does it happen all the time that people think they can fix complexity by adding another layer of complexity too it?

I'm not entirely sure but I see this pop up a lot with webpack. Webpack is not inherently difficult to configure, it just requires you to read the documentation. All these solutions are doing is adding what they feel are sane defaults to the webpack experience. I don't see how this would appeal to someone who knows webpack well. In my opinion these solutions are just intended for a minority of new developers. For anyone else they could roll out their own faster than they could learn how to use abstraction layers built around someone else's.

Re: Show HN: Jetpack – Webpack made more convenient

#25

Earlier quoted context omitted.

Perhaps because David J. Wheeler said "We can solve any problem by introducing an extra level of indirection."

Except too many levels of indirection...

I guess that threshold is different for everybody, who's to say what works best in a certain situation?

Re: Show HN: Jetpack – Webpack made more convenient

#26
post #22

Earlier quoted context omitted.

Except too many levels of indirection...

Just wrap it in an IndirectionManager and instantiate that via an IndirectionManagerFactory and you're good to go. :)

You forget the IndirectionPolicy interface...

Re: Show HN: Jetpack – Webpack made more convenient

#28

Hey just fyi in case you don't know, jetpack[1] is the name of a very well known wordpress plugin by Automatic. Might cause some confusion. [1] https://wordpress.org/plugins/jetpack/

Yes, my first thought was this post was WP related. (and then I actually read the link. ;) )

Re: Show HN: Jetpack – Webpack made more convenient

#29

Haven't looked deeper in it, but why does it happen all the time that people think they can fix complexity by adding another layer of complexity too it?

Generell agree with the sentiment and also the specific case here. One thing to note though is that a lot of the complexity of setting up Webpack correctly for a standard user is the very high and contradicting amount of SO/Google advice. This is caused by the (relatively) long history of Webpack and the major version jumps. A layer on top doesn't carry this baggage so may indeed reduce complexity.

Re: Show HN: Jetpack – Webpack made more convenient

#30
post #24

Haven't looked deeper in it, but why does it happen all the time that people think they can fix complexity by adding another layer of complexity too it?

I'm not entirely sure but I see this pop up a lot with webpack. Webpack is not inherently difficult to configure, it just requires you to read the documentation. All these solutions are doing is adding what they feel are sane defaults to the webpack experience. I don't see how this would appeal to someone who knows webpack well. In my opinion these solutions are just intended for a minority of new developers. For any…

On the other side, comments like yours also pop up with the same frequency. 'Just read the documentation', which sits at 50+ pages, does not make for a good developer experience. Projects like this are a symptom of the pain developers, new and old, feel when faced with a mountain of complexity just to get a module system and ES6 working on any small project.
Post reply on HN