2 ms·

I know Apple has to deal with a lot of legacy code and wants to avoid conflicts. Their architecture is very good but I believe it could still be better (at leas

by kaelig 13y ago

I know Apple has to deal with a lot of legacy code and wants to avoid conflicts. Their architecture is very good but I believe it could still be better (at least they stopped using IDs in their CSS). Nesting (especially this deep) is usually a bad idea. Have you heard of BEM? This methodology helps building reusable modules without polluting the global scope.

arrrg 13y ago
It’s not only about legacy code. Apple’s website layout (especially on all the important product pages, certainly also some overview pages in the store) is all highly custom, much more like a magazine than a website. That’s on purpose. That stuff is supposed to look different. Making the stuff reusable wouldn’t even make sense. (Though I do not want to claim that what Apple is doing here is a good way to go about things.)