paulsamways

6 ms·

1.
by paulsamways 13y ago
See http://research.google.com/pubs/pub38125.html
2.
by paulsamways 13y ago
So the key part of the update I was referring to was the following: Because of course that's not how it really works. Instead, it makes a local copy of that external library. And if you have a local copy, you can edit it. And mean
3.
by paulsamways 13y ago
I know how it works :) I'm not new to Go. BUT, what you are describing is exactly how the Haunt guys used Go and consequently the issues they have run into. Please re-read the update from Rick and read my comments again, you should then und
4.
by paulsamways 13y ago
> No need to fork, it puts a copy of those libraries under ./src, so you always have a sealed (hermetic) referentially complete copy. While that is true, it doesn't solve the problem with distributed teams. The library path MUST be poi
5.
by paulsamways 13y ago
> and put import ("github.com/go-gl/opengl/gl") directly into your code. Viola! Thus hilarity ensues. Of course it does! All they had to do is fork the project (which they have) and reference that it instead. Viola, problem solved!
6.
A case of mistaken encoding(paulsamways.com)
2 points by paulsamways 13y ago|0 comments
7.
by paulsamways 14y ago
Won't disagree with you there! Though sometimes going outside your comfort zone can be a good thing.
8.
by paulsamways 14y ago
More people should be doing this. You don't even have to move out of tech yourself, find a position in a company where tech is only ancillary, not the core focus. You'd be surprised just how many real problems are out there waiting to be so