Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Quake 3 Source Code Review

fabiensanglard.net

Post reply on HN
Print view View original

11–14 of 14 posts

Re: Quake 3 Source Code Review

#11

Post by 38leinad »

AaronMT wrote: post #3

Feels like yesterday that we (or at least some of us) we're all in awe with the released 'Q3Test' published online in 1999.

i was downloading the test with my 33.6k modem. back then, in germany, flatrates where not yet common, so i did not want to fall in the trap and waste alot of money playing online. i remember that some phone provider was having a "free internet" day (you could dial in for free if you where able to get one of the limited spots) and i was up 5 in the morning before school to play a free round of quake 3 test... good times.

Re: Quake 3 Source Code Review

#12

Post by fabiensanglard »

hcles wrote: post #10
Muzza wrote: post #8

This might be OT, but that guy sure has some weird ideas about how to build a website. Why are the images lazy loaded? There are like ten small images per page. It also doesn't revert to img tags in the absence of Javascript. At one point on the first page he needs to show something with a fixed-width font. This also requires Javascript, when obviously CSS should do.

Most people will visit the page, scroll down a screen or two and leave it since they're not game programmers. So, just speculating, he's no stranger to bandwidth spikes so perhaps the approach employed significantly saves on bandwidth during these periods, ultimately whether it's a conscious attempt to save or just a webdev quirk I don't know.

You got it. I implemented lazy-loading for the precise case you described: Save bandwidth from people that don't want to read the full article.

I tested it on Chrome, FireFox and Safari: I did not find it annoying....but maybe it is because I tried to put myself in the shoes of someone ready slowly and I have a DSL bandwidth...

Re: Quake 3 Source Code Review

#13

Post by azsromej »

fabiensanglard wrote: post #12
hcles wrote: post #10

Earlier quoted context omitted.

Most people will visit the page, scroll down a screen or two and leave it since they're not game programmers. So, just speculating, he's no stranger to bandwidth spikes so perhaps the approach employed significantly saves on bandwidth during these periods, ultimately whether it's a conscious attempt to save or just a webdev quirk I don't know.

You got it. I implemented lazy-loading for the precise case you described: Save bandwidth from people that don't want to read the full article. I tested it on Chrome, FireFox and Safari: I did not find it annoying....but maybe it is because I tried to put myself in the shoes of someone ready slowly and I have a DSL bandwidth...

Thanks for publishing these code reviews; it's fun to load up the projects and jump from file to file on a guided tour
Post reply on HN