HN user

ezalor

11 karma
Posts0
Comments29
View on HN
No posts found.

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}.

[dead] 16 years ago

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.

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!