4 ms·
Lets call them zealots since they're mostly not really trolls. CSS zealots are a lot like TDD zealots. Both CSS and TDD have huge, huge benefits that you shou
by dasil003 18y ago
Lets call them zealots since they're mostly not really trolls.
CSS zealots are a lot like TDD zealots. Both CSS and TDD have huge, huge benefits that you shouldn't write off before you actually take the time to learn them. The problem is the zealots talk about them as panaceas and ignore the fact that there is no one methodology that separates the pros from the amateurs. Instead they use their expertise in one tiny niche to prove to themselves how their work is so much better than the majority of similar work due to a few arbitrary criteria. Then they form small self-congratulatory communities to pat themselves on the back about how brilliant they are and how much everyone else could learn from them.
These are the people who you find trolling your blog. Usually they aren't even particular skilled at what they do, which is why they cling to dogma and feel the need to attack other people.
But let me be clear. I haven't layed out a website using tables since 2001 (and I used tables for 5 years before that), once you develop your mental model of CSS (and browser deficiencies) there are actually only a few edge cases where tables are easier. CSS can actually solve 90% of web design challenges more elegantly than tables. CSS makes it easier for designers to and developers to work together (I am both). There are many techniques which are only available in CSS. All future technical developments in web design will be in the realm of CSS.
So it really is worth the time to slug it out with CSS and figure out what's what. That said, web design coding (ie. HTML/CSS) is just one tiny piece of a huge potential set of web development skills. Why does google put CSS inline? Because their design considerations are driven by 100 things that are so far over CSS Zealots heads they can't even fathom it: scalability, latency, back-end HTML generation, js compiled from other languages, etc.
- deleted 18y ago[deleted]
- iamelgringo 18y agoRE: Why does google put CSS inline? Because their design considerations are driven by 100 things that are so far over CSS Zealots heads they can't even fathom it: scalability, latency, back-end HTML generation, js compiled from other languages, etc. From: http://www.fastcompany.com/magazine/100/beauty-of-simplicity.html http://www.fastcompany.com/magazine/100/beauty-of-simplicity... But the original [Google] home-page design was dumb luck. In 1998, founders Sergey Brin and Larry Page were consumed with writing code for their engine. Brin just wanted to hack together something to send queries to the back end, where the cool technology resided. Google didn't have a Web master, and Brin didn't do HTML. So he designed as little as he could get away with.
- markup 18y agoWhat does the design of google back in 1998 have to do with the inline CSS argument?
- iamelgringo 18y agoI have a big hunch that design decisions at 75% of Alexa's top 20 sites aren't really based on CSS idealogical purity, scalability, algorithmic complexity or back-end html generation issues. I think those decisions are based on plain and simple expediency and frustration. Much like my decision to go ahead and use tables. I think that's what guided Google's decision in 1998, and I still think that's what guides their decisions now.
- markup 18y agoWhat guided Google's decision back in '98 was to deliver the most kickass search engine ever, the sooner the better (I guess). From that point to now it's a matter of perfectioning every single aspect of their creature, to ensure a great UX (therfore fidelization). What makes a great UX? A clean UI, a fast service and possibly no hiccups (to make it very short). The UI has changed a lot from 98 to now (check out web.archive.org) and so did their HTML code. A single line HTML page is obviously a conscious decision and so is the inline CSS. I don't know you, so I have no idea on your experience in this field, but when you get to deal with I'm not saying huge, but decent amount of users you simply have to deal with scalability under every single aspect. If you don't, chances are you end up delivering a crappy service OR you spend WAY more money (bandwidth, cpu power, etc) than you actually need to. EDIT: google is obviously more than html and css, and if you really want to have an idea on how they are paranoid with performances you should check out their google app engine documentation.
- dasil003 18y agoYou're projecting your own personal issues onto large organizations. The primary factor motivating any design over time is inertia. When were these sites started? What was the state of the art then? Who were the people that laid the groundwork for the site? Google is unique in that A) they can hire top experts in any technology they want, and B) their homepage is extremely minimalistic and easy to change. So to suggest that Google does things out of frustration is just incredibly naive. You didn't seem to get the point of my original post very well. Allow me to paraphrase a little more bluntly: * You don't need to be a designer to do awesome things and succeed on the web. * If you are a web designer and you don't know CSS inside and out, then you are a hack whose skills are already obsolete and sure to become moreso quickly.
- initself 18y agoI think the author's point was if you analyze the content of the major websites out there, you'll find that because there is obviously "no one methodology", those who are zealous should now be called "trolls". Enough is enough.
- dasil003 18y agoA troll is someone who is intentionally baiting a flamewar. I don't really think it makes sense to call people who voice strong opinions trolls.
- notphilatall 18y agoLearning CSS and taking the time to do it right has other benefits also: Redesign is faster since there are fewer elements to manipulate; 98% of (newbie) cross-browser issues arise from excessive markup that's ignored by FF and interpreted correctly in IE; fewer elements also means less "mystery meat" when you start seeing IE vs. FF alignment issues.