| > how often do you have to install that stuff? > how hard is it actually? > can you really not use, e.g. for react, the typical vite starter and it's done? I have to install that stuff everytime I'm starting a new project, switching to a new project, or creating a one-off script. It's hard when creating a new project where there's always at least one flag that needs to be found and set different from a previous project for some random reason, every single time. It's hard when switching to a new project, because you have to figure out which version of node you're supposed to be running because each version runs the dependencies differently between different versions of node, and different computers. It might even silently work for you without being on the right version, meaning you continue working on it, then your commits don't work for yourself later or others now or later. This leads to one of two possibilities: 1. A longer job either unwinding everything to figure out what the versions should have been the whole time. 2. A lot of trial and error with version numbers in the package and lock files trying to figure out which set of dependencies work for you, work for others, and don't break the current project. We also can't use the typical community templates because they always become unmaintained after 2 years or so. --------------------------- Why I like Deno: - Stupid easy installation (single binary) with included updater - Secure by default - TS out of the box (including in repl making one-off-scripts super easy to get started) - Settings are already correct by default. -- and if you ever need to touch settings for massive projects, they all sit in one file, so no more: tsconfig/package.json/package-lock/yarnlock/prettier/babel/eslintrc/webpack/etc... And since the settings are already sensible by default, you only need to provide overrides, not the entire files, so the end result for a complex project is usually small (example link: https://docs.deno.com/runtime/manual/getting_started/configu...) - Comes with builtin STD meaning I don't need to mess-around with dependencies - Builtin utilities are actually good so I don't need to mess-around with the rest of the ecosystem. No jest/vitest, no webpack/rollup, no eslint/prettier/biome (but you can keep using your editor versions just fine). - Since it came after the require -> import transition, basically everything you're going to be doing is already using the more sensible es modules. |