I'm up late again only this time its a Saturday so its no as bad. But I thought I would make use of my time, this time, and see if I can pick up a few new things.
I'm sure most people here have already had a look at the code that makes this site work. But it dose bring up a few questions. I have a rough idea of the hardware this site uses (mainly down to pics of the servers and info being posted a few years ago) and I have a rough idea of how that relates to the site itself. The site mainly acts as an interface to a web service. Now that's nothing new. But this site uses Javascript quite a lot, and that brings up the first question.
As well as being graphically more impressive, was the use of Javascript implemented to place some of the CPU load on each individuals computer saving the server in places where thats possible. Take the Art portal for example, we've been told this was done in JS rather than flash so all the image resizing etc if it is completely done in JS will be done on the users end saving the server from having to do any work say with a PHP based image library.
And thats literally the visible part of the iceberg. I would like to know the problems this site faces with the amount of data it has to process and the solutions that have been implemented to solve these problems. Are solutions designed with that in mind to begin with? etc etc etc.
I don't know if anyone user or staff member has any answer but I would be interested to know. And it was about time people people had a thread to boast in :P