3 ms·
In my experience preemptive fixes are akin to procrastination when there's no empirical evidence to necessitate the change.
by andrewtj 18y ago
In my experience preemptive fixes are akin to procrastination when there's no empirical evidence to necessitate the change.
- michaelneale 18y agothat's an awesome quote - can I borrow it ??
- andrewtj 18y agosure
- run4yourlives 18y agoThat assumes that there's extra work in coding to standard. In fact, it's quicker to do so.
- tomjen 18y agoReally - adding a doctag is faster than not adding it? That seems incorrect to me.
- andreyf 18y agoI think gp is talking about the long-run. That is, getting things to render right on all browsers, on all devices, printed, etc. Have you ever tried printing a thread? It's bearable, not certainly but pretty.
- run4yourlives 18y agoThat's like saying you don't indent your code blocks because hitting tab is slower than not hitting tab. The point being that there is a lot more to development than keystrokes. But let's user your argument anyway: what's faster: <div id="content">content</div> or <table id="content"><tr><td>content</td></tr></table> Now, lets say I want to move the table text from left to right alignment. While you're mucking around in your code, I pull up the css file and add a line.
- kwamenum86 18y agoWe have web standards to prevent browser bugs. Ironically sticking to standards 100 percent of the time often causes buggy visual display in some browsers. Standards are supposed to make things easier but the browsers have been pretty slow in complying. That does not mean that standards are not a good idea. The lack of empirical evidence is due to that non-compliance. The same browser sometimes allows non-compliant code and chokes on valid code. This is a coordination game (just like driving on the right side of the road). If everyone complies (developers, browsers, etc.) things work. If enough don't, everything breaks.