Run — Development tooling: ✔ Fixed

Thanks, @panphora, for your feedback! 🙂 Run introduces a new way to create and use tools, and there is nothing comparable on the market. One of the nice features of Run is that it can automatically install the tools used in a project. It can be compared with "devDependencies" in a package.json file, but Run is much broader because not restricted to the JavaScript environment. Another way to manage a development environment is to use something like Vagrant (or Docker, at a lower level), but I find it pretty cumbersome; Run's approach is much more simple. Another critical problem I'm trying to solve is the composability and usability of the tools. Because current tools are built on old foundations (Unix-like systems, Bash, etc.), they are difficult to combine (to make a builder for example), and their interface is not quite user-friendly. Run, with the concept of "resource", adds an object-oriented interface to the tools, making everything a lot easier. Finally, Run just got born, and it's not immediately usable by end developers. It's something that allows a new generation of tools to be created. So, we have to wait for a bit before seeing concrete things emerge and starting to figure out the actual value.

In July 2016, I founded 1Place Inc., a small (I am presently the only member) Japanese company with a huge ambition. The initial plan had nothing to do with Run, and before starting the actual work, I took great care in choosing my development tools. Unfortunately, nothing was satisfying, and I felt like that something was going wrong. Whether it was installation or configuration, the developer experience was not good. Then, I dug, dug, and dug to finally come up with the idea of Run (the resource runtime), and Resdir (the resource directory). It was so exciting that I put aside my initial plan to make this thing a reality. That is how Run was born. 🐣