3 ms·

Yo dawg, I heard you like configuration so I put Babel config in your Webpack config in your Vue3-CLI config so you can configure while you configure. In all s

Yo dawg, I heard you like configuration so I put Babel config in your Webpack config in your Vue3-CLI config so you can configure while you configure. In all seriousness, I'm not seeing how yet another build system with a plugin architecture changes anything for frontend development. I'm also not seeing what this extra layer offers over using Webpack directly.

k__ 8y ago
Pssht, don't tell them :D
antonkm 8y ago
I came here to post something similar. The re-re-re-invention of the wheel is getting tiring. I'm having a hard time as seeing this as progress.
zmmmmm 8y ago
Yes. A lot depends on how well transparent this dynamic construction of the webpack config is and whether you can really customize it or not. I've spent a bit of time having to fiddle with very specific options in my VueJS webpack config and as fiddly as that is, the ability to directly edit them at least makes it possible to do just about anything I need. Trying to debug why a config you can't see is not working, being unable to take simple examples from the manual or Stack overflow and directly put them into my config ... sounds like it could end in a nightmare. But, jury's out, so far the Vue developers have managed to make good decisions about most of these things, so they've earned at least a little benefit of the doubt.
alexkavon 8y ago
Welcome to DJS (Department of JavaScript), please take a number, stand in the line to your right, and migrate your code to the next coolest framework.
- h4b4n3r0 8y ago
  Phtt. Migrate? That's crazy talk. Rewrite! On a more serious note: that's why I exited frontend dev 15 years ago and never looked back. I now do hard-ass C and C++, and once I write something it runs for many years with no changes, and dependencies are often a decade old or more.
wvh 8y ago
People should learn their tools and systems, but I think it is very important to make it as easy as possible for people to get started with your framework, language or system. Nothing kills interest as quickly as not even being able to get started on something; to get people up and running is probably the single most important thing if you want your project to get any significant amount of users. I struggled a few months to get a decent working structure for multiple environments working when I had to do a largish front-end project (out of my comfort zone and not really a big fan of Javascript), so I think tools like vue-cli are a good idea: set up a sensible base structure, and work on from there if you have both experience and time. Showing an idiomatic architectural layout might also help people to move more quickly from basic "Hello, World!" examples to larger, non-trivial applications, which in my experience is a problem for most programming languages.

k__ 8y ago

Pssht, don't tell them :D

antonkm 8y ago

I came here to post something similar. The re-re-re-invention of the wheel is getting tiring. I'm having a hard time as seeing this as progress.

zmmmmm 8y ago

Yes. A lot depends on how well transparent this dynamic construction of the webpack config is and whether you can really customize it or not. I've spent a bit of time having to fiddle with very specific options in my VueJS webpack config and as fiddly as that is, the ability to directly edit them at least makes it possible to do just about anything I need. Trying to debug why a config you can't see is not working, being unable to take simple examples from the manual or Stack overflow and directly put them into my config ... sounds like it could end in a nightmare. But, jury's out, so far the Vue developers have managed to make good decisions about most of these things, so they've earned at least a little benefit of the doubt.

alexkavon 8y ago

Welcome to DJS (Department of JavaScript), please take a number, stand in the line to your right, and migrate your code to the next coolest framework.

h4b4n3r0 8y ago
Phtt. Migrate? That's crazy talk. Rewrite! On a more serious note: that's why I exited frontend dev 15 years ago and never looked back. I now do hard-ass C and C++, and once I write something it runs for many years with no changes, and dependencies are often a decade old or more.

wvh 8y ago

People should learn their tools and systems, but I think it is very important to make it as easy as possible for people to get started with your framework, language or system. Nothing kills interest as quickly as not even being able to get started on something; to get people up and running is probably the single most important thing if you want your project to get any significant amount of users. I struggled a few months to get a decent working structure for multiple environments working when I had to do a largish front-end project (out of my comfort zone and not really a big fan of Javascript), so I think tools like vue-cli are a good idea: set up a sensible base structure, and work on from there if you have both experience and time. Showing an idiomatic architectural layout might also help people to move more quickly from basic "Hello, World!" examples to larger, non-trivial applications, which in my experience is a problem for most programming languages.