Go 1.3 Linker Improvements 
So on most real world applications, you shave perhaps a second or two off compilation and linking times.<p>That's great, but... why does Go still have such an abysmal regexp package that is an <i>order of magnitude slower</i> than C and C++?[1]<p>Why does encoding/json still rely on reflection, making it slow compared to other approaches?[2]<p>In other words, I guess I feel like there are areas with more bang for the buck.  The changes in 1.3 are great (100% precise garbage collection!), but I'm hoping improvements to regexp and encoding/json are somewhere on the roadmap as well.<p>[1] <a href="http://benchmarksgame.alioth.debian.org/u64q/performance.php?test=regexdna&sort=elapsed" rel="nofollow">http://benchmarksgame.alioth.debian.org/u64q/performance.php...</a><p>[2] <a href="https://journal.paul.querna.org/articles/2014/03/31/ffjson-faster-json-in-go/" rel="nofollow">https://journal.paul.querna.org/articles/2014/03/31/ffjson-f...</a>