Live data from Hacker News

I am a fast webpage

varvy.com

51–60 of 292 posts

Re: I am a fast webpage

#52

Just to point out, there's no particular reason to host a page like this on a VPS at all. You could just throw it on S3. Even better, you could put it behind a CDN like Cloudfront and the total cost would be a dollar or two a month, not $25+ and it would be significantly faster.

Or even better, Surge.sh. - A very happy customer.

Been using Surge.sh recently and it's super awesome, but I'm not sure I'd use it for production. Care to elaborate?

Re: I am a fast webpage

#55
post #33

Earlier quoted context omitted.

> Is this image inlining thing something new? No, it's been around since forever. Just not used terribly often. > Am I reading it correctly that the images are encoded in base64 and delivered as html? Surely this is a bad idea... no? It depends. Making a new request to fetch the image always has overhead. Whether that overhead is bigger or smaller than the overhead of base64-encoding the image depends on: • file size…

Completely offtopic, but how do you type •? I like it.

I personally type it with a unicode keyboard input (ex: Japanese in my case) 

ex: "・"

Re: I am a fast webpage

#57
post #33

Earlier quoted context omitted.

> Is this image inlining thing something new? No, it's been around since forever. Just not used terribly often. > Am I reading it correctly that the images are encoded in base64 and delivered as html? Surely this is a bad idea... no? It depends. Making a new request to fetch the image always has overhead. Whether that overhead is bigger or smaller than the overhead of base64-encoding the image depends on: • file size…

Completely offtopic, but how do you type •? I like it.

It's system dependent.

On windows you can do alt+numpad 2022

On whatever is handling input for this XFCE system, control+shift+U 2022+Enter types it.

Re: I am a fast webpage

#59

Just to point out, there's no particular reason to host a page like this on a VPS at all. You could just throw it on S3. Even better, you could put it behind a CDN like Cloudfront and the total cost would be a dollar or two a month, not $25+ and it would be significantly faster.

> You could just throw it on S3. Even better, you could put it behind a CDN like Cloudfront and the total cost would be a dollar or two a month, not $25+ and it would be significantly faster. I apologize for quibbling (really, I do! but I'm an infrastructure guy! This is my bag!). Yes, host it on S3, but ALWAYS put a CDN in front of S3 with long cache times (even just Cloudfront works). S3 can sporadically take hundr…

You could also host it on App Engine for free and automatically use Google's CDN.
Post reply on HN