3 ms·
I've tried learning Ember, React, and Vue and have tapped out pretty early. Now I'm learning how to build a site using only vanilla JS and doing everything from
by evandale 3y ago
I've tried learning Ember, React, and Vue and have tapped out pretty early. Now I'm learning how to build a site using only vanilla JS and doing everything from scratch unless I find a reason to switch it. I think I'm making decent progress.
I even wrote my own simple test framework that shoves the results on the bottom of a page. After adding a few features I decided to switch it to Jasmine.
One thing I'm noticing is how often you need npm which I find very annoying. How is a JS library or framework anything more than a single JS file that you have to include in your page? Why is everything npm this and yarn that? Jasmine has standalone install instructions that are easy to find but I can't say the same about Jest.
- gochi 3y agoI'm confused by this, why do you think npm is needed? It just acts a central repo, you're free to self host the JS file yourself or pump it through a CDN. Jest is a different story, it's not a single JS file and has many dependencies. Running it globally is an easy way to reduce the need to include it per project.
- sfn42 3y agoPeople use package managers because it lets us find everything in one place, install it and keep it up to date easily. I'd much rather do `npm i whatever` than having to hunt down a bunch of git repos and copying files over and when they're outdated having to do the same thing to update them etc.
- osullivj 3y agoDitto on Ember, React, Vue and Elm. Was a jQuery minimalist, nut now moved on to Haxe-HTML5. Yes, it compiles Haxe to JS. But the JS it generates maps back to the Haxe very simply, and it's straightforward to debug in Chromium dev tools. There a nice declarative XML system for widget layout. It's up to you to choose how much you do declaratively, and how much in .hx code.