5 ms·
Doesn't this seem like a maintainability nightmare? I can see a small change in rendering that causes number portions of a website to break in difficult to diag
by orofino 14y ago
Doesn't this seem like a maintainability nightmare? I can see a small change in rendering that causes number portions of a website to break in difficult to diagnose ways.
Clicking any of the HTML/CSS links under any of the icons just doesn't absolutely nothing for me btw. Running: Chrome 25.0.1364.29 beta
- hayksaakian 14y agoBeta bug? I'm on crappy old chrome 18 (android) and it all works. Scrolling is slow however.
- laumars 14y agoI agree about the maintainability issue. I really hate this kind of use of CSS as it strikes me as abuse of coding standards. It's as if a bunch of intellegent developers decide to throw all sanity out the window and compare cock sizes using CSS as their ruler. Maybe I'm just old school, or maybe years writing native applications and fixing other peoples kludges has taught me disciplines that many of the younger web developers missed; but I'm a firm believer of the need to keep the different paradigms separate: * HTML: mark up for the content * CSS: design (though I tend to run 2 CSS files: 1 for layout and one for the motif/colour schemes) * img (et al): embedded objects such as images (if people really want to use vector graphics, then there's SVG). It's like how you wouldn't write a game and have the OpenGL wrappers in the same classes as computer AI; you'd modularise your project sanely. So why does such logic get thrown out the window when it comes to web development?