enneff

79 ms·

901.
by enneff 12y ago
You mischaracterised my point. Go is hardly the baseline for language simplicity. We just made a different set of trade offs to the Rust team, and I believe Go is the simpler (not simplest) language.
902.
by enneff 12y ago
It was a two line "me too" when I posted that reply.
903.
by enneff 12y ago
Nearly zero content.
904.
by enneff 12y ago
This is an amazing comment.
905.
by enneff 12y ago
> That second-last example with errWriter destroys safety AFAICT It is possible to make mistakes. Go isn't the kind of language that forces you to be safe and do the right thing all the time. Like all languages, it makes tradeoffs.
906.
by enneff 12y ago
The point is not to use this exact pattern, but to write code to handle errors in a way that works in your context. If the error check is many lines away or in a different function, you should use a different approach.
907.
by enneff 12y ago
Not everything belongs in the compiler. Go's "vet" tool might be the place for something like this. But, honestly, I have been writing Go code for 5 years and I can count the number of times that "didn't check the e
908.
by enneff 12y ago
The corresponding loss to Rust's gain is language complexity.
909.
by enneff 12y ago
It should be pretty easy for distributions, since they'll already have packaged versions of Go 1.4.
910.
by enneff 12y ago
Ken Thompson wrote it. He's pretty good at C.
911.
by enneff 12y ago
Yep, exactly. We want to write our compiler in Go, now that the language and libraries are good and stable. It's a process we started more than a year ago: http://golang.org/s/go13compiler
912.
by enneff 12y ago
I wear good quality noise cancelling headphones with the music turned quite low. I feel like this is doing a lot to preserve my hearing.
913.
by enneff 12y ago
Note that by default tinyproxy logs all the URLs it accesses, which may not be what you want.
914.
by enneff 12y ago
Show me an example of me disrespectfully disparaging other people's work. I'll wait.
915.
by enneff 12y ago
I come from the background of working on the Go project for five years. He really doesn't see the trade offs we made when choosing to base the core Go implementation on the plan 9 tool chain, and seems oblivious to the work already don
916.
by enneff 12y ago
Don't get me wrong; there is a lot wrong with the computing world. I just don't think this surly rant does much to illuminate the issues. There's a lot wrong with his post on Go. It's not even worth reading.
917.
by enneff 12y ago
A big mistake for a newcomer to any field is to put too much stock into people's opinions, particularly those that are put disrespectfully. It's a common technique among the programming crowd to vocally disparage other people to m
918.
by enneff 12y ago
> And use that argument as almost the sole argument for any decision. One of these ways of thinking explains every decision very consistently, the other leaves one listing the exceptions That's not accurate. There are a lot of thing
919.
by enneff 12y ago
Once again, the c2 wiki brings the goods. A nice discussion of the reasons you do and do not want to do code generation. Thanks for the link.
920.
by enneff 12y ago
They are legitimate concerns, but your given example (re-ordering constants) could break other things silently in any case. There's always a line between risk and convenience. For some people Go is too conservative, and for others it i
921.
by enneff 12y ago
I said "use a more elaborate build system." That means, "more elaborate than the Go tool." So, no, you're not.
922.
by enneff 12y ago
To expand on why it's not like make: it doesn't do dependencies. Think of 'go generate' as a codified 'gen.sh'.
923.
by enneff 12y ago
You just want this feature to be more than it is. It's a small, simple thing. Don't overthink it. If you need a more elaborate build system, use one.
924.
by enneff 12y ago
Adam and Eve is a work of fiction.
925.
by enneff 12y ago
"Gerrand" :-)
926.
by enneff 12y ago
> I freely admit that I do not know the intimate details of Go development ... How much that is actually true is almost irrelevant until the perception changes. Since you freely admit your ignorance, can you please stop making uninformed
927.
by enneff 12y ago
> I see from another comment that this release first happened, and then, afterward, the release was pushed to its “official” Git repository. You misunderstand. The release was made from the official open source Mercurial repository, and
928.
by enneff 12y ago
Great suggestion, thank you!
929.
by enneff 12y ago
There is, but since we're only partway through migrating to git/github, the README still shows the old instructions. The new contribution instructions will appear here in the next few days: http://golang.org/doc&#x
930.
by enneff 12y ago
At least since the public release in November 2009.

More ›