News for hackers. Stuff that matters.
Re:Go 1.3 Linker Overhaul by girvo on Thursday November 28, 2013 @06:31AM (#6814119)
1) Cause the creators of the language decided to. Don't like it, feel free to fork it.
Re:Go 1.3 Linker Overhaul by coldtea on Thursday November 28, 2013 @09:48AM (#6814703)
>Cause the creators of the language decided to

Which is an no-op answer. That can be the answer for any kind of engineering decision, including the most idiotic ones.

We're concerned with what's best here, not merely with what has been decided.

>Don't like it, feel free to fork it

Another BS non answer.

Re:Go 1.3 Linker Overhaul by girvo on Thursday November 28, 2013 @10:06AM (#6814766)
The language authors obviously disagree with it being an "idiotic" engineering choice. Your choices of tradeoffs don't match theirs, and engineering is never as simple as "I'm right, you're wrong", as you well know.

Yeah I was being facetious with my original reply, and frankly I get your point, I was pointing out however that you _can_ fork it to make it work the way you'd prefer. If you truly don't want to (or can't) do that, then open a ticket or send something to a mailing list.

If this really matters to you, do something about it that can make an actual difference.

Re:Go 1.3 Linker Overhaul by chimeracoder on Thursday November 28, 2013 @11:21AM (#6815145)
> Don't like it, feel free to fork it.

Or use gccgo, which piggybacks off of the many optimizations that have been used in the gcc collection[0] over the years.

When discussing compilation of Go, people here often seem to forget that two first-class compilers exist for the language.

[0] Yes, I am aware that this is like saying "ATM machine"