Live data from Hacker News

As much Stack Overflow as possible in 4096 bytes

danlec.com

41–50 of 77 posts

Re: As much Stack Overflow as possible in 4096 bytes

#41
Maybe part of the story here is that gzip isn't the be-all-end-all of compression. A lot of the changes were made to appease the compression algorithm; seems like the algorithm could change to handle the input.

A specialized compression protocol for the web?

Re: As much Stack Overflow as possible in 4096 bytes

#43

I'd love to see a general list of techniques you use, as best practices.

There's a short list at the end of the post about Trello4k: http://danlec.com/blog/trello-in-4096-bytes

Thanks. How much of that could we do during the original design phase?

Re: As much Stack Overflow as possible in 4096 bytes

#44
post #6

Very impressive. I wish extreme performance goals and requirements would become a new trend. I think we have come to accept a certain level of sluggishness in web apps. I hate it. I wrote a tire search app a few years back and made it work extremely fast given the task at hand. But I did not go to the level that this guy did. http://tiredb.com

I agree. I've been using Ghostery recently to see the external libraries that are loaded on various sites and it's ridiculous. Some sites are loading more than 50 extern scripts.

Re: As much Stack Overflow as possible in 4096 bytes

#45
post #9
post #6

Very impressive. I wish extreme performance goals and requirements would become a new trend. I think we have come to accept a certain level of sluggishness in web apps. I hate it. I wrote a tire search app a few years back and made it work extremely fast given the task at hand. But I did not go to the level that this guy did. http://tiredb.com

Now that we have blisteringly fast computers, it's worth it to browse old websites and see what "snappy" looks like. http://info.cern.ch/hypertext/WWW/TheProject.html If we could cram more modern functionality into say...twice or three times the performance of the above, I think the web would be a better place. Instead the web is a couple orders of magnitude slower.

I absolutely love TBL's initial documents. They're utterly semantic markup. Which means that you can apply a minimal amount of CSS to have them appear in a pleasant-to-read format. Let's see if I can find that pastebin .... Here: http://pastebin.com/7sGiHBwF

But, yeah. If webpages would just revert to what TBL had created (yes, I'll allow for images and minimal other frippery) things would be so much more manageable.

Re: As much Stack Overflow as possible in 4096 bytes

#49
post #48

funny, his compressor must do a better job than mine: $ curl -s http://danlec.com/st4k | wc 14 80 4096 $ curl -s http://danlec.com/st4k | gzip -cd | wc 17 311 11547 $ curl -s http://danlec.com/st4k | gzip -cd | gzip -c | wc 19 103 4098

Turn up the compression level:

    $ curl -s http://danlec.com/st4k | gzip -cd | gzip -9c | wc
         14      80    4096

Re: As much Stack Overflow as possible in 4096 bytes

#50
post #49
post #48

funny, his compressor must do a better job than mine: $ curl -s http://danlec.com/st4k | wc 14 80 4096 $ curl -s http://danlec.com/st4k | gzip -cd | wc 17 311 11547 $ curl -s http://danlec.com/st4k | gzip -cd | gzip -c | wc 19 103 4098

Turn up the compression level: $ curl -s http://danlec.com/st4k | gzip -cd | gzip -9c | wc 14 80 4096

Right. I feel silly for not trying that. Good spot.
Post reply on HN