Markov HN Go comments

gistfile1.txt

<dgryski@kaepora[HNgo] \ʕ◔ϖ◔ʔ/ > for i in $(seq 10); do ./markov <hngo.txt; echo; done |fmt
There have been spawned at vaguely the same fate in science. Java has
better garbage collectors, including a maximum of 10 ms pause should not
apear in a lot of effort in the content has to consider adding proper
macros to the language that you're using (if one at that AIUI. there's
lots of i/o, and there was no option to have removed their page isn't
"slow" or anything, but who cares? Your argument seems to hate the idea
of what happened) and the more rigid syntax for the core language is safe
(that goes for 3 probably. 2 and

There have been supported in some cases and not a pure Go implementation
is still very simple. Frameworks are complicated -- but it still really
bothers me. Perhaps there's a lot of is under NDA. lol... Just built
1.4.2 (or whatever latest 1.4 was) last night. Wow still no generics by
basing the resource creation and management on JSON and a blog article. I
believe we'll be getting them eventually. HKTs aren't even experienced
in the description of the Bell Labs gurus somewhere around the issue. The
question is an awesome point. I feel that it takes the cpu to

There have been able to formally verify a language is to help you
learn. Also, regarding pointers: They're really not that high at all. Go
has its own word now? "Cray cray" and by now ancient history. Yes,
you are half way through and slog through the lens of "the language
won't change" etc recently. So it's like PHP where I partially finish
the code multiple times anyway then it should be! And you had come from
a long story short, once I started writing Go for me has been sped up,
using a simple c-style enum. What the ...

There have been plenty of other tools. The go-team not only are you
talking about? Are we talking about was more about practical purity and
simplicity over complexity even at the implementation is considered. If
you have to think about allocations! Nope. The point was not deliberately
designed that way, because it extends interface of IEnumerable<T>,
which is how type names are all widely used). E.g. if you were writing
Java. Go uses shared-memory concurrency (as opposed to the printing
package. surprisingly powerful :) What is the compiler code you interact
with. Today, it's not a question on Go's performance

There have been several others). Rust isn't harder than conventional
GC languages. Yes, there is a lot of stuff. Yeah I know, we can
ignore unused dependencies very early just by walking an AST node. And
directives similarly to exceptions and end functions in time 35 years
and C extensively. I think history has absolutely shown that exceptions
are for in Java. In Java this would be considered in that it would do
with generics, if you import a package before processing the current
approach simple enough so that there are situations where a little more
efficient than a derivative

There have been paid by Mozilla at some point, given that literally the
very terms Tim Bray tried. Why weren't they "biased" in HIS results? Isn't
he a member of "everyone"? (c) "not everyone uses Google. But who knows
what the parent comment, Rust is a marketing fluff piece from Google. "I
still haven't written much Go if you have many functions per type or
only one component in the reference counter falls apart. Curious, how
"real time" can a large memory usage or resource handling? Any need for
generics will disappear if the disclaimer helps you, I'd like to

There have been watching from the official Git repository, because this
was one of the 'Benchmark Game' benches, typically by quite a bit of go,
but it does have two major production deployments (OpenDNS and Skylight)
and we've heard rumors of a language that didn't make it easier for Java
programmers were perfectly happy to write synchronous code, letting the
OS on this subject than you realize. > Sarcasm for users of Rust compared
to mastering C++ or getting C right without dangerous bugs. I agree with
them. That's pretty sweet, I'll remember that you're using Go for my next

There have been spawned at vaguely the same problem if you are
correct. Since a conventional database server is the very least, it
supports generics and templates, so powerful that they can label a GOTO as
well. Yeah, it's been a very subjective balancing act. I find your comment
quite odd, as a private joke about the hierarchy at a distance until the
perception changes. Since you know that what you think about safety. The
difference is it's sweet spot. The TensorFlow project in a language geek,
I write Go code conform to the startup's success, and a 5 year

There have been learned about FP making life easier. Set operations (map,
filter, reduce) are insanely common, yet doing them that are part of the
NSA and other high profile companies using technologies from 1995. What
? Of all the cool features of the wins of Servo layout have come from
a crappily-typed PHP background. but if you care to implement; it can
do in Bash). Start using Go They still use it for some projects and I
agree with you. A zip code is unambiguous. IF has a mountain of legacy
cruft which makes absolutely no such thing as

There have been found long ago about assembly languages and I do think
it comes to writing languages with faster compilers. I look only for
myself, I was saying the "good enough" attitude is usually only ask for
them in the real issues, I fear that go offers for such non-in-built
solutions when starting I can't remember anyone ever needs. If you are
calling will throw an exception. The only real significant difference
between simple and easy. Go is any kind of simple we are faster:
http://benchmarksgame.alioth.debian.org/u32/rust.php You _hate_ the
Benchmarks Game, but there were warnings everywhere: "don't use multiple