I've felt exactly that while testing Vite (https://github.com/vitejs/vite https://github.com/vitejs/vite) this morning from Evan You, author of VueJS. Standard

I've felt exactly that while testing Vite (https://github.com/vitejs/vite https://github.com/vitejs/vite) this morning from Evan You, author of VueJS. Standard install, nothing to configure, instant hot reload + modern code and tooling yet no perceivable latency for anything. It felt like suddenly I could enjoy front end dev. So I get the appeal of Deno. But I know this ability to put arbitrary URLs as dependancies in the code are going to be terribly missused and abused. I can see all the tutorials that will start including them, the bad architecture decisions that will spread them accross all files, the interns that will use localhost there, the typo and domain squatting or black SEO, the rise of people just telling you to put an URL from their site (the same that tell you to curl that bash script), the split from npm, the hardship of scanning/mapping/updating dependancies, the mismatch betwen running and installing bitting you, the undebuggable tickets because of proxies/antivirus/firewalls, the cloud hosting potential for failures, some twisted scenario leading to a DoS... I know it will cause horrible technical debt down the road. My spider dev sense is tickling and I'm not going to touch this tech for 5 years, until I either see my prediction unfold, and be completly disproved by its success (but I doubt it, I've been really good in the last 10 years at spotting bad technical choices). There is a reason we have been using separation of concerns since the down of time. Declaring dependencies, installing them and importing them are 3 different concerns. They should not mix.