News for hackers. Stuff that matters.
Re:Go 1.3 Linker Overhaul by stcredzero on Thursday November 28, 2013 @10:30AM (#6814900)
So they opted to handle the easy problem.

Also the problem with the lowest cost/benefit for them. Also the problem with the highest benefit. One calls this a "no-brainer."

Re:Go 1.3 Linker Overhaul by danieldk on Thursday November 28, 2013 @10:59AM (#6815055)
...or selling a shortcoming as a feature. What if someone picks up pcc[1] and claims it is better than the competition because it makes C compilation lightning-fast?

Of course, Go is a language that is more amendable for quick compilations. But it would be more interesting to see a solution that provides good optimizations and improves programmer productivity. Go doesn't really have an answer to that (except: use gcc-go), while the competition has (e.g. JIT compilers).

[1] http://pcc.ludd.ltu.se/pcc_history/

Re:Go 1.3 Linker Overhaul by stcredzero on Thursday November 28, 2013 @01:42PM (#6815846)
...or selling a shortcoming as a feature.

If you want to be nitpicky, it's not that Go is selling a shortcoming as a feature. It's more that it simply doesn't have that feature.

Go also has a number of other features pcc doesn't.