4 ms·
And this is why I gave a try to VueJS in the first place. It can be deployed with npm, or a simple script tag. It still does today, making prototypes easy to w
by BiteCode_dev 4y ago
And this is why I gave a try to VueJS in the first place. It can be deployed with npm, or a simple script tag.
It still does today, making prototypes easy to write, training very simple, and yet, it plays well with the more complex ecosystem.
Now of course, VueJS has Vite, which makes all the complexity of Webpack goes away, removes the slowness of compilation and has sane defaults.
Still, npm remains. I'm now used to it, but I understand that if you come from another language, it's not attractive.
It's funny to me that most people consider JS packaging better than Python packaging.
Both are troublesome, just for different reasons. E.G: using different versions of node is much harder, espacially on windows, or for the same project, than different versions of python. And installing compiled extensions is a way better experience in Python than in any other high level language. On the other hand, node_module is easier to use than the average venv.
- zelphirkalt 4y ago> And this is why I gave a try to VueJS in the first place. It can be deployed with npm, or a simple script tag. This is exactly, what I noticed positively about VueJS and advertised as a good feature for integrating this specific "web component" framework into a project. You can add it as simply as one used to add jQuery to any project. However, others thought of including script tag as "not proper" (even though I told them, that in the end it would all be a script tag anyway ...) and it was decided to use another framework, which is way more complicated to integrate in any statically rendered / server side rendered and template based website. Simply putting VueJS in a script tag is not a problem. One can cache it easily and one can use noscript tags at places in any page templates. All is fine.