No need to be pedant dude.
HN user
ezalor
They can sue you for making this hypothesis publicly, please think of it (in your interest).
Seems not (re-read the guidelines).
If you look at Firefox memory consumption while browsing Twitter, you'll see the main culprit is, like always, DOM operations (repaint/reflow particularly). Solution: use Chrom{e|ium}.
Obvious difference: I expect not to get my HDD corrupted because I visited an arbitrary website, I understand it might be the case if I download AND run an arbitrary program.
Which kind?
This is not that exciting: a malicious XSS or CSRF and PAF! an attacker writes on the user filesystem!
I always think that Scala lacks a good, deep IDE, but this is a handy list. Thanks.
The handling of a <video> is outsourced to the OS.
This, obviously, is out of bounds.
So it's really just a time-limited solution, a temporary chance.
It's OK while it is sensible (after all, you will inform your friends you have published a new blog post or whatever) and not some heavy "please upvote" campaign.
You read my mind for "parity of a set". So Q.E.D.: parity is only applicable to reason about numbers (and infinity is not a number). See also surreal numbers.
Parity is a property of numbers and sets only. Or do you think infinity is a set?
update: no more the case: see http://news.ycombinator.com/item?id=2121727
The magic of the cloud! Imagine running that on Heroku (for instance): it would be costly (price) but possible.
A friend of mine opened a company (EURL) in 2 weeks and for about 300 euros. Honest. It'd be twice as expensive in, say, Estonia (I run a business there).
Totally. "If you want to make an apple pie from scratch, you first need to recreate the Universe" -- Sagan.
I always thought the purpose of Arc was to be cruft-free, "don't include it unless it is actually needed".
> That's not the bottleneck.
What is the main bottleneck of HN?
Yes, if by "caching" you mean and only mean "caching on RAM".
David Filo is the co-founder of Yahoo! if you don't know him.
Reverse-proxying via nginx would solve this problem and more: the arbitrary 30 second limit on form submission (hotspots sometimes are slow...), nginx could handle rate limiting & logging instead of srv.arc, etc. The Arc codebase would btw be smaller and cleaner (no policy/sanitization code, etc.).
Serving static content via Apache was a first step ;-)
Don't reinvent the wheel!
it doesn't actually communicate its message successfully at the most basic level.
As a marketer, I agree.
Whatever your traffic, if you build it, they will come.
thx bro!
Does the government count?
wat do you mean?