Hm, you might be right, but I think that people who have access to someone to guide them are in a different position than folks trying to make sense of it on th

Hm, you might be right, but I think that people who have access to someone to guide them are in a different position than folks trying to make sense of it on their own. The subset of terminal commands needed for interacting with NPM is minimal, but I'd bet it would be a lot more daunting for someone trying to make sense of the universe of meta-react-stuff and unsure what stuff's important and what stuff isn't. When I was 12 I decided I wanted to learn how to program, and I failed miserably because I didn't know where to start and very much picked the wrong place (I bought a massive reference manual for C from a bookstore). So I'm particularly sensitive to the fact that people have finite motivation and patience, and are sometimes trying to figure this out haphazardly (and so a friendly UI actually is important, because it'll stand out as something familiar in a sea of black terminal screenshots). The idealistic future I imagine is that Guppy provides built-in support for a bunch of common tasks (I definitely don't want it to include a whole Git client, for example, but maybe a limited subset would be helpful), and direction for the stuff it doesn't bundle (like choosing an IDE, debugging, whatever). The larger philosophy is that tools designed for professionals will always be more complex than they need to be for beginners, and there should be a stepping stone. But yeah, I am receptive to the idea that maybe this is the wrong approach. Maybe Codesandbox and online IDEs make more sense?