5,085 karma · joined March 11, 2009
a) The CSS file should be inline.
b) The images should be done away with entirely by including them as a data uri.
c) For IE6-7 (data uris not supported) the fallback image should be sprited.
d) For bonus points (if you want HN to be served nearly instantly, globally) splurge for an application caching CDN provider like Akamai.
It feels dirty not to cache it, but if you look at a download waterfall and see how much time it takes to send that separate http request (while blocking the display of the page) it is well worth it.
The rest of the tips seem to be really sleazy, but are pretty surreptitious. However, wouldn't this be extremely obvious to both parties and be so blatantly unethical to end the recruiter's career?
Maybe people are buying pre-jailbroken phones for carrier reasons?
The times we are charged tend to be for burst traffic when something gets picked up on Digg or Reddit. Recently, one of our blog posts was featured on Digg, Reddit, Slashdot, etc. at the same time and Google dutifully served up a couple hundred thousand visits over the course of a few days. They charged us about a nickel! Granted everything is nicely cached so we were not doing much heavy processing.
It definitely depends on your web app. If you can cache it, App Engine is essentially free. If you are doing something CPU intensive for every visitor, it's going to be expensive.
URLFetch API - We’ve expanded the number of ports you can access with the URLFetch API. You can now access ports 80-90, 440-450, and 1024-65535.
Some screenshots that were auto-shared will have sensitive info in them and there will be a massive privacy backlash.
I am playing it at 30 FPS on my MacBook Pro right now. ;)
You can run your App Engine apps pretty much anywhere.
Doubling the characters to 10 would pretty much completely solve the problem. It would take many, many years to find a single image. Far below the threshold where Amazon S3 would ban you.
Google Checkout, on the other hand, is relatively weak (doesn't support bank accounts, is slower, more false positives, weaker API, etc.).
I'm not sure which is more mindboggling... Spending 66% of their bandwidth and 50% of their CPU on serving these trivially cacheable pages or the fact that they didn't correct the problem when they were serving more than 5%.
I already explained why I cannot give you an example of a AAA HTML5 website (Internet Explorer doesn't support it).
If you'd like to discuss the technical aspects of HTML5, feel free to email me at jeff@wolfire.com - I am going to stop checking this thread.