> Turn a fresh Ubuntu installation into a fully-configured, beautiful, and modern web development system by running a single command. That’s the one-line pitch

> Turn a fresh Ubuntu installation into a fully-configured, beautiful, and modern web development system by running a single command. That’s the one-line pitch for Omakub. Most webdev tools are written in JS (or at least used to be). Web browsers run JS just fine. Webdevs, then, should be striving to make sure that their JS-based tooling actually runs in the browser—instead of targeting the non-standard, ever-shifting, and unreliable APIs of NodeJS et al. There's not an especially good reason that you shouldn't be able to build 80% of the projects on GitHub that belong to this milieu by simply: 1. downloading a copy of the source code 2. opening README.html 3. following the instructions in the workspace on the resulting page that says "to build this project, drag and drop the project folder here" NPM/NodeJS programmers so desperately wanted to be taken seriously that they reimplemented wholesale all of the bad, fiddly things about toolchain installation, configuration, and maintenance that afflicts all other platforms/stacks that didn't have the it-just-sort-of-works-for-everyone strength that browsers have (and is largely the reason why so many webdevs choose to target browsers in order to reach end users in the first place). The perverse irony of this might be amusing if it didn't result in so many pointless excursions and wasted hours of human potential spent nursing the unfortunate status quo associated with `npm install`, yarn, etc.