242 karma · joined January 9, 2015
Writing a recursive descent parser is actually quite intuitive. It's the solution that you'd eventually arrive at if given the problem of parsing some specific context free language.
GLR, GLL and PwD are solutions to parsing non-cfg (i.e. grammars that have more than one parse-tree) in optimal time.
A JIT is not a performance feature per-se, either. It can be used for runtime code-optimization and -specialization which can improve performance. Some JVM implementations try and do this as well as they can automatically. The stuff they optimize, though, is exactly the kind of indirection that doesn't exist in Go in the first place.
The optimizations `javac` does are one of the few things that allows Java code to run at a competitive speed. And they're mostly trading space for performance, hence the unusually large memory footprint of Java applications.
It's usually thursday or friday evening that my team will pop some beers and talk conceptuals. In those informal discussions information just flows, sentiments are shared and fruitful decisions are reached.
Winning and losing battles implies that battles exist. That's bad enough for me.
I wonder why Douglas Crockford, a brilliant man, still works there (other than obviously well compensated time).
Pooh-pooh.
https://en.wikipedia.org/wiki/Pooh-pooh
Also, ad hominem.
It was also a quick refresher on how god damn ugly bash's syntax is.
Congrats to the whole team!
> Covariant: Given two types A and B, A covariant B if B is a A. In other word, A covariant B if B is a prefix of A.
Taken from here: https://github.com/google/badwolf/blob/master/docs/temporal_...
Co(ntra)variance only makes sense if you define a subtype relation first. And I think that's what you wanted to define here.
After skimming through the docs I think what you want is: A is a subtype of B if B's path is a prefix of A's.
They don't use contenteditable in the traditional way:
> Trix sidesteps these inconsistencies by treating contenteditable as an I/O device: when input makes its way to the editor, Trix converts that input into an editing operation on its internal document model, then re-renders that document back into the editor.
I find this a fine solution.
You know what really grinds our gears, though? People who don't read documentation.
If you don't read documentation, you'll get a negative vibe. Because your question is literally sitting at the top of the FAQ. It's been asked 2^1024 times before. WHY WON'T YOU READ THE DOCS?
He's not paid for the mileage spent on the way to pick up someone, only after they get in.
Suggestion: Make an S3-uploader package with _internal_ connection pooling, upload queueing and concurrency handling.
Obviously swiss people are not born smarter than the rest of the world, but the education standard is quite okay and even though populism exists (as everywhere), Switzerland is doing better than any of it's neighbors right now, thanks to the decisions that the people have made.
The child-slavery thing is a black stain in our history, and we're aware. You can stop throwing rocks down from your glass house now.
On the internet layer, IP packets can still be traced from origin to client. I'm probably not involved enough to formulate an educated opinion, however.
He's arguing that viewing public information over HTTPS is no more private than doing so without encryption.
Sure, insofar as an entire response consists only of public information, this is a tautology, isn't it?
x * tanh(y)
you get the graph for:
x * (exp(y)-exp(‑y))/(exp(y)+exp(‑y)).
[Edit: asterisks on HN are hard]