So they finally gave up?
“This change deletes the C implementations of the Go compiler and assembler”
51–60 of 137 posts
Re: “This change deletes the C implementations of the Go compiler and assembler”
#52Wow, github doesn't handle big diffs well. Some sort of automatic pagination would really help.
I would make the case the "big" diffs are a problem. Unless there's a really good reason (and bad dependency management is not a good reason) then commits should be smaller and more logically related.
Re: “This change deletes the C implementations of the Go compiler and assembler”
#53Earlier quoted context omitted.
Also, one is marked as having exactly double the number of comments and points as the other.
Not for me anymore: http://imgur.com/XM8xmEp
When the double point/reply relationship ended, the comments sections also diverged. This is how it looked while the comments were still identical: http://tinypic.com/r/vn2u0i/8
Re: “This change deletes the C implementations of the Go compiler and assembler”
#54One does wonder if the register re-naming from their abstract (but misleading) names to their proper machine names (e.g., from "SP" to "R13") wasn't at all a reaction to the (in)famous polemic on the golang build chain.[1] [1] http://dtrace.org/blogs/wesolows/2014/12/29/golang-is-trash/
That's a classic of the "too rude and opinionated to salvage anything reasonable" genre right there.
Re: “This change deletes the C implementations of the Go compiler and assembler”
#55Earlier quoted context omitted.
It's the smart quotes.
Ha. It's always the smart quotes. They've caused me so many headaches over the years it's amazing to me that they are still actively supported and implemented in any software. What value do they even bring? #DeathToSmartQuotes
> It's always the smart quotes. #DeathToSmartQuotes
This is pure kogir bait (he is your passionate co-positionist), but as far as we can tell, it wasn't the smart quotes.
Re: “This change deletes the C implementations of the Go compiler and assembler”
#56Wow, github doesn't handle big diffs well. Some sort of automatic pagination would really help.
I would make the case the "big" diffs are a problem. Unless there's a really good reason (and bad dependency management is not a good reason) then commits should be smaller and more logically related.
While I agree that a big diff isn't a good idea, I disagree with the notion that one should develop in such a way that makes Github (or whatever VCS you're using) work right.
I don't think working within the capabilities of the VCS you're using should ever be a priority for a software development effort; rather I think the VCS's priority should be to allow for their use within most contexts of software development. (the other way around)
Re: “This change deletes the C implementations of the Go compiler and assembler”
#57Wow, github doesn't handle big diffs well. Some sort of automatic pagination would really help.
I would make the case the "big" diffs are a problem. Unless there's a really good reason (and bad dependency management is not a good reason) then commits should be smaller and more logically related.
" This change deletes the C implementations of the Go compiler and assembler from the master branch." is logically related as it could be. Everybody has a different interpretation of it, I guess.
Re: “This change deletes the C implementations of the Go compiler and assembler”
#58Earlier quoted context omitted.
Ha. It's always the smart quotes. They've caused me so many headaches over the years it's amazing to me that they are still actively supported and implemented in any software. What value do they even bring? #DeathToSmartQuotes
Smart quotes tend to cause a lot of problems... especially since they don't just convert to a standard quote in Unicode, etc... [1] [1] http://en.wikipedia.org/wiki/Quotation_mark#Curved_quotes_an...
User content posted from a word processor directly into a textarea field = much suffering.
Re: “This change deletes the C implementations of the Go compiler and assembler”
#59Wow, github doesn't handle big diffs well. Some sort of automatic pagination would really help.
GitHub does cut it off beyond a certain point, but that cutoff point should be much, much earlier.
Re: “This change deletes the C implementations of the Go compiler and assembler”
#60congrats gophers! That's a big step for the language.