3 ms·
>gives me a scary black box feeling, like if it really wanted to it could stop working and I would be unable to fix it This was verbatim my thinking when evalu
by unclebucknasty 9y ago
>gives me a scary black box feeling, like if it really wanted to it could stop working and I would be unable to fix it
This was verbatim my thinking when evaluating Vue 2 a while back. Its reliance on Webpack or Browserify for optimal use really gave me pause. I could just see myself losing days trying to figure out which bit got flipped to stop its working.
Vue 2 was new at the time as well, so I wasn't sure about adoption, ecosystem, and/or the maintainers' committment. Looking back, I would've rolled the dice. But, all of this to say glad I'm not alone in that black boxes give me pause in a world where everyone seems to rush headlong into the next big thing, ceding ever more control.
- CharlesW 9y ago> Its reliance on Webpack or Browserify for optimal use really gave me pause. Mind elaborating on what you mean by "for optimal use"? For example, I use Brunch with Vue 2 and it seems to work fine.
- LukeShu 9y agoThere is no complete stand-alone Vue SFC compiler; every SFC compiler is written as a plugin for a specific bundler. The 3 official implementations are the Webpack, Browserify, and Rollup plugins. There's no significant code-sharing between them (and I'm sure there are no subtle differences that will bite you), and the Browserify and Rollup plugins can lag months behind the Webpack one--they still don't support functional SFCs, which were added in Vue 2.5.0 back in October. So, how does vue-brunch work? It declares the Browserify plugin as a dependency, and wraps it.
- unclebucknasty 9y agoExactly this. And Rollup wasn't available (or at least well-publicized) when I was evaluating about a year ago.