Many janet installs out there are broken or only partially correct, simplifying the setup might help improve this.
To quote @bakpakin :

Really just making the installation easier would be a good start. One major issue is that non standard, broken installs are pretty common - the easiest way to make that not possible is to have just one binary - Janet

Any approach bringing a tighter integration with the runtime and package management should reduce possible misconfigurations and make it simpler for people to get started with janet.

There are still a few open questions like:

• should the package manager be part of janet (in a single binary) or installed as janet script with the default installation?
• should all components of jpm be kept as is or are there some paint points that could be addressed with such a migration
• how to maintain backwards compatibility with current projects?