3 ms·
> It is amazing that it took them this long to realize they were entirely wrong about how dependencies should be distributed. It didn't take "this long"; the G
by chimeracoder 8y ago
> It is amazing that it took them this long to realize they were entirely wrong about how dependencies should be distributed.
It didn't take "this long"; the Go team openly admitted the need for a better approach at the very first GopherCon back in 2014, nearly five years ago. (That was not the first time, either).
It takes time to do all that work.
- spullara 8y agoIf you realize something is wrong a couple years in and it takes 5+ years to fix it, then that seems like a long time to me.
- geodel 8y agoIn between community developed many solutions when official solution was lacking. So it's not like people were twiddling their thumbs for 5 years. Also check how long Java took to get official module solution. Work on that started in 2008 and solution was delivered in 2017.
- pjmlp 8y agoIn Java's case, lets not forget the work started before Oracle's acquisition and there were the political wars from the OSGi field as well.
- spullara 8y agoHah. They don't have one now. The de facto solution is Maven. Java itself doesn't actually have a module system like the one discussed for Go. It is merely a access control system rather than a dependency system. To be clear, I give the Java people shit about it all the time and was on the original Java module system JSR that was supposed to deliver it. In the end, the Sun people yanked the dependency part and shipped a module system that is really only useful to the JDK.