Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue.js and Brunch: Webpack Alternative

vuejsdevelopers.com

Post reply on HN
Print view View original

11–20 of 113 posts

Re: Vue.js and Brunch: Webpack Alternative

#11

Post by shados »

alexlrobertson wrote: post #9
dingle_thunk wrote: post #2

Great ideas. It seems like this sort of 'sane defaults' functionality could easily be added to future versions of webpack, and that might really help with adoption... rather than this community endlessly switching tool chains.

I'm surprised we haven't seen config packages for webpack take off along the lines of the configs in the ESLint community. There's nothing stopping anyone from publishing an extensible base config.

I was under the impression that was the idea behind the new webpack cli (though I haven't tried it).

The main issue is generally that there isn't much of a consensus on toolchain. Are you using vanilla ES6 or TypeScript? If the former, are you sticking to the standard or using class properties and object spread? Are you also adding non-stage3 crap like bind operator and decorators?

For CSS, are you using styled components or Sass? Maybe you're using PostCSS? If so, with which plugins?

Are you doing codesplitting? If so, how? Are you using a DLL plugin for your vendor stuff? Oh, and how would you like to handle far future caching?

For a trivial app there probably can be a default, but unlike something like ESLint, any app that plans on living more than a little bit needs to answer all these questions and the answer is not obvious.

Generally you could stick with some defaults that represent a majority opinion, but right now its so close to 50/50, it's hard. Still could be done though.

Re: Vue.js and Brunch: Webpack Alternative

#13

Post by efdee »

timdorr wrote: post #4

Brunch has a good "vs Webpack" section in their docs: http://brunch.io/docs/why-brunch#brunch-vs-webpack Some of the big table stakes features that Brunch is missing are code splitting and handling of binary assets (allowing things like image inlining). It also doesn't have true hot module reloading, which is a pretty useful dev feature.

Code splitting seems like a major feature to miss out on. I assume/hope it will come to Brunch sooner rather than later.

Re: Vue.js and Brunch: Webpack Alternative

#14

Post by apocalyptic0n3 »

tkubacki wrote: post #12

When did Vue hype officially start ? It's funny to see how deeply HN crowd is driven by vouge.

Depends on what community you are part of. Vue received a lot of hype within the PHP community (especially the Laravel community) shortly after it launched. I want to say early 2015 is when it started there.

Re: Vue.js and Brunch: Webpack Alternative

#15

Post by aweiland »

hardwaresofton wrote: post #8

If you're looking for alternatives to Webpack, please also check out JSPM (a good short description might be "preprocessing system + package manager + systemjs"): https://jspm.io/ It takes a little more to get it to work with vue (the plugin that makes .vue files work is older and unsupported nowadays), but I use it just fine, with my template, styling and component files separated (I wrote a little thing: https://gi…

Rollup looks pretty good too. It's on my list to play with.

https://rollupjs.org/

Re: Vue.js and Brunch: Webpack Alternative

#16

Post by ziggzagg »

dingle_thunk wrote: post #2

Great ideas. It seems like this sort of 'sane defaults' functionality could easily be added to future versions of webpack, and that might really help with adoption... rather than this community endlessly switching tool chains.

I know this will get downvoted, but here I go anyway: Please stop reinventing the wheels. Just stick to one library/framework whatever crap they are. Why? Because your new shiny wheel will be as crap as the old one very soon.

I am myself refusing learning new tools in javascript. I think I have spent enough time learning enough of them. I have a selected set of them, and I turn down projects which fall out of that set. Less money, but better mental health.

Re: Vue.js and Brunch: Webpack Alternative

#17

Post by jaequery »

ziggzagg wrote: post #16
dingle_thunk wrote: post #2

Great ideas. It seems like this sort of 'sane defaults' functionality could easily be added to future versions of webpack, and that might really help with adoption... rather than this community endlessly switching tool chains.

I know this will get downvoted, but here I go anyway: Please stop reinventing the wheels. Just stick to one library/framework whatever crap they are. Why? Because your new shiny wheel will be as crap as the old one very soon. I am myself refusing learning new tools in javascript. I think I have spent enough time learning enough of them. I have a selected set of them, and I turn down projects which fall out of that se…

one thing i learned to accept with the web is just how fast a trend can change in this industry. after i invested time in knockout, then came angular. then once i invest in angular, then came react. then after investing time in react, then came vuejs. it seems to either be a systematic cycle of people wanting to always try new things or that the tools are infact getting better and better.

and once a group of pack starts going off in one direction, its just a matter of time before everyone is on it. for better or worse, it seems hard to stop this type of movement.

im not sure why this is tbh, because mastering your tools is a big part of becoming a 10x developer, where you are actually productively creating and not just looking up docs half the time.

perhaps this type of fad may be mainly driven by beginning or jr devs who are still undecided on what they want to learn and just go with what seems to be the next cool thing to learn.

but then again without this type of change, we might as well all be still coding in perl. it really sucks to throw away what you invested in for a year or more but its just something you have to accept as a dev and move on these days as a javascript developer.

Re: Vue.js and Brunch: Webpack Alternative

#18

Post by mintplant »

ziggzagg wrote: post #16
dingle_thunk wrote: post #2

Great ideas. It seems like this sort of 'sane defaults' functionality could easily be added to future versions of webpack, and that might really help with adoption... rather than this community endlessly switching tool chains.

I know this will get downvoted, but here I go anyway: Please stop reinventing the wheels. Just stick to one library/framework whatever crap they are. Why? Because your new shiny wheel will be as crap as the old one very soon. I am myself refusing learning new tools in javascript. I think I have spent enough time learning enough of them. I have a selected set of them, and I turn down projects which fall out of that se…

Webpack came out in 2012, Brunch in 2011. So clearly everyone should stop using Webpack and switch to Brunch, or they're guilty of reinventing wheels.

Re: Vue.js and Brunch: Webpack Alternative

#20

Post by jaequery »

tkubacki wrote: post #12

When did Vue hype officially start ? It's funny to see how deeply HN crowd is driven by vouge.

mainly its the react fatigue, thats finally tipping them over the edge to try something better. vue seems to have come in at the right time for that. and given the momentum, its possible that vue may supercede react at some point if this keeps up.
Post reply on HN