I like that Go don't allows unused import and variables.
If you're working with inexperienced programmers (and some experienced but bad programmers), you should be certain that they WILL let that code garbage there if the compiler allow it.
I love VueJS. I found it very easy, specially when you aren't building a SPA, but want something more powerful than jQuery without being overkill like React.
(I've tried Glide but it slowness and few bugs made me move to Govendor. Nothing personal, it just didn't work out that well for me.)
A few questions:
- Is the intention desincentive the use vendoring?
- Is the intention to make a single solution, and then deprecate existing tools (Glide, Govendor and like)?
- Do you have the intention to make a central registry for Go packages? Or the solution will use GitHub and like, as it does today? It would be not backward compatible, but the document don't make this clear.
I once tried to learn Angular, but failed miserably. The documentation is so awful and the framework is so bloated.
So I gave a chance to React and I liked it first, easier to learn, object-oriented, etc.
But now I found [VueJS](https://vuejs.org/), which is even simpler. You don't need to deal with the painful tooling of React (webpack and a huge number of files in a node_modules folder), it works out-of-the-box. Include the script tag and start coding, this is how things should work! The simpler, the better.