Bad UX for starting projects
Opened this issue · 2 comments
Let's say I want to create a go project. If I already had the go compiler (etc) installed, I could do a go init followed by garn init. But if I don't, I first have to make a base project with go in an env, then enter that env, then go init, then change the project to a go project (if you did it any earlier, everything would fail since it wasn't a go project).
(This is, mutatis mutandis, true of other stacks too.)
Not sure what the solution is. Maybe making the environment of e.g. a go project succeed even if we can't parse the go project?
It's not a solution to this specific problem, but at least a mitigation: We should have a collection of working examples of garnished projects for different tech-stacks. Either as a cookbook on the website or as a collection of repos on github. So people could either just clone those or at least look up exactly how to set a go project up. (Again, not really a specific solution to this problem, but makes it less bad.)
+1 for working examples. Maybe similar to Realworld Apps or TodoMVC. Maybe, one could even work to show how garn behaves in each setting of TodoMVC and Realworld App.