• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Did Amazon change something on their site? Browser keeps locking up

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Because it's irrelevant, in this case? My experiences are with >3GHz Haswell and Ivy Bridge quad cores.

Problem is coders have to stop assuming that everyone has a >3Ghz processor, and even then, why code stuff so that it uses all of it, they need to realize that people don't have a computer to run ONLY their program but to run many things at a time.

Not even sure how one even manages to make something so bloated, it seems to me, it's actually more work to make something super bloated than nice and light weight. The more bloat, the harder it is to maintain. Take something like a website for example, there's absolutely no reason to use 10,000+ lines of java script hosted across 10 different domains just to do something as simple as a hover image viewer or drop down menu. You can probably code that in a couple 100 lines, host it locally, and it will be MUCH faster and easier to maintain.
 
This could be a very specific problem. A site I work on locks up on something like Firefox 22 and 23 but only on 32-bit Windows. The problem goes away if I upgrade JQuery, but that breaks a bunch of stuff not worth fixing to support such a small subset of users.
 
Take something like a website for example, there's absolutely no reason to use 10,000+ lines of java script hosted across 10 different domains just to do something as simple as a hover image viewer or drop down menu. You can probably code that in a couple 100 lines, host it locally, and it will be MUCH faster and easier to maintain.
Bandwidth isn't free, so you get some files from CDNs, which saves bandwidth and CPU on the servers giving you the specific content you're looking at. There are negatives on your end, but it is, on the whole, a huge gain for them.They can also use canned libraries, instead of another NIH problem. Just like the RAD frameworks around 2000, it's going to blow up and then get streamlined, but we don't quite seem to be there, yet.
 
Back
Top