3 ms·
Actually, the 'go' tool is one of the things I rather dislike in Go so far. It's good to have to tool that does everything for you, but I'd like to at least be
by yorhel 15y ago
Actually, the 'go' tool is one of the things I rather dislike in Go so far. It's good to have to tool that does everything for you, but I'd like to at least be able to structure my directories in the way I want. For mixed-language projects you won't get rid of Makefiles either way, and they're really not that bad with the right include files or Makefile generation tools.
Using URLs to identify external libraries also isn't something I'm very fond of. Both because you'd have more boilerplate to type when using them, and suddenly the library is fixed to a certain internet location and VCS.
Meh, I can go on ranting about other things I dislike about Go, but it wouldn't solve anything. I'll just keep monitoring the developments from the sideline and see how things evolve over time.
- 4ad 15y agoThe URLs are not really fixed, there's a feature which I am not sure if it's documented yet that allows for an indirection between a shorter import path and the real import path, so you could change the VCS or the real location.