Warning to YC applicants: We're going to restart HN tonight
So if you're editing your YC application in the application form (which I wouldn't recommend anyway), click regularly on the Save button at the bottom of the page.
We restart HN every 5 or 6 days, or it gets slow (memory leaks). Usually we do it at night and don't say anything about it, but since people might be editing YC applications, I thought I'd better issue a warning.
I haven't said when we're going to restart it, because I don't know. It shouldn't matter anyway; just don't depend on it.
72 comments
[ 4.6 ms ] story [ 218 ms ] threadI check HN couple of times a day and I have not felt any performance difference.
Just "hey, guys, we're gonna flick the lights on and off sometime tonight; just a heads up in case you're working on something."
Never change, HN.
Edit: I find it adorable that you all think HN is a hard site to run. Good luck breaking 200 qps.
It is a hard site to run due to its audience. Realize that this site gets poked around by hundreds of hackers. All trying to learn or break the system. Trying to not get your ass handed to you with a commonly language/framework is hard enough. I can't fathom how they do it with an experimental language and libraries. Though they are Lisp hackers. If anyone can do it, its a Lisper...
I suspect that the HN software does much more important but less obvious things which meet YC's goals than those you mention. I also suspect it does those things well.
As for page expirations, well, they aren't a deal breaker for me.
If I was PG I would test YC founder's time/frequency spent on HN against the success of their startups. I would use that data in evaluating new applicants. This test might ferret out founders with a procrastination problem.
I might also try discovering possible throw away HN accounts created by founder's applying under their official HN identity. That could really ferret out some assholes not technically competent enough to cover their tracks and dumb enough not to think this possibility through.
Also, PG's essays are one of the great success stories of content marketing.
That's how I found this community, and although I probably will never apply to YC, the enthusiasm for it's backed startups have rubbed off on me. I wouldn't have been an early AirBNB or Dropbox user if not for those essays.
Do you have the code on github or somewhere?
There may be all kinds of other reasons to update the code, but that comes down to available time, experimentation, and enthusiasm, not productivity.
This is more or less what Apache and IIS do with child processes or long running threads. It's a production proven approach.
Based on the last time I touched it, I suspect it's a managed memory leak, though. The vast majority of Racket is in racket/base or mzscheme.
FWIW: Use Ditto if you don't want to lose the previous buffer content.
Three simple (pragmatic) reasons:
1. Most of the time I forget.
2. Sometimes I'm writing multiple comments in HN and elsewhere simultaneously. And, sometimes I write quite long, carefully thought out comment on a forum I visit frequently, complete with images and all that (the forum runs phpBB and doesn't have a 'save draft' button). We need to change the web server before we can move to a better forum engine (vanilla, perhaps) and it's a small forum and doesn't worth the effort until we move the forum to another server later this year.
3. I usually use Safari betas (on OS X), and they're not famous for being stable and while the whole app rarely crashes, after they've moved to WebKit 2.0, occasionally something goes wrong and it has to refresh all open tabs and flush anything that's been in the text fields. So, even if I do #1, the danger is still there.
:)
You'll want to preserve a copy of your application for future reference anyway.
When HN gets busy, that is also helpful for posting comments. Sometimes even when I type one of my shorter comments, by the time the comment is done and I select "reply," the response is "unknown link," a sign of a time-out condition. (I probably type slower than many programmers.) Fortunately, my browser preserves my form submission if I encounter that condition, so then I copy the whole comment and try again. Anything long that takes looking things up I compose in my text editor, and then paste in all at once (as for another reply I posted today).
Because competence wasn't worth it a few hundred restarts ago and isn't worth it now.
thanks for the info.
I mean... c'mon
<table width=100% cellpadding=6 cellspacing=0> <tr><td bgcolor=#ffff88> <table width=100% cellpadding=0 cellspacing=0> <tr><td bgcolor=#ffff88>
Personally I'd love it if the HTML template of HN would be a bit more semantic. I've had at least four false starts where I was like "yeah I'm gonna build this piece of userscript JS so I can more easily <check replies to my comments or whatever>" only to hit a brick wall when I am reminded how awful it is to parse, even with today's advanced DOM querying features. Fortunately there are those with more perseverance, so I am thankful to at least get to use someone's bookmarklet that adds comment-folding to HN :)
Oh, and as for "editing your YC application in the application form" ...I wouldn't recommend it, either. Use something that doesn't require an internet connection, and save often. [Don't forget to actually fill out and submit your application, though. =]
AFAIK HN doesn't use continuations, but closures.
Something along the lines of(imitation of arc challenge in flask):
https://gist.github.com/3998745