Skip to main content

A Very Thin Line (ALA discussion response)

I definitely see your point, and, in most aspects, I agree with you wholeheartedly. Yes, it's frustrating, that support for standards is not yet where we would like it to be. Yes, it's ironic, that sometimes it takes a hack to make things work as they are supposed to, and it's just infuriating, that nobody, but a little group of enthusiasts, seems to realize the importance of standard-based web design.
Yes, they are enthusiasts, may be hobbyists, purists, sometimes even called zealots and diehards, but look at what they actually do: they create, and explore, take things apart, and put them back together, share their ideas and experience, and feed on each other techniques, tricks, and hacks. All that for what? For the sake of the obscure idea of making the web a better place. And guess what? It's happening, may be, slower, than desired, but it's happening.
There will always be web designers, whose tool of choice is FrontPage. There will always be graphic artists, who don't know, how to draw a human figure.
They are not important, regardless of how successful or productive they are. They do not set the bar. These enthusiasts do.
People will go to their sites to challenge, entertain, or puzzle themselves; often - to steal ideas, scripts, and hacks.
And this is how the web evolves; and not only web - everything works in a very similar way in our world.
Where would the whole huge pop music world, if they would not be able to feed on the strange, exotic and disturbingly weird legacy of avant-garde jazz, alternative rock, folk, and neoclassical experiments of the beginning of the last century? Chances are, nowhere.
Those are the rules of evolution...

Popular posts from this blog

WordPress: How to add custom fonts to a twenty seventeen child theme.

Quick help to those who have tried to find some help and failed (as I have so I have to write the code myself). Assuming that you have your virgin child theme configured and activated: here is a function which goes into the functions.php file (of your configured and activated child theme): function childtheme_twentyseventeen_fonts_url() { $replace_original_font = true; // unless you really like Libre Franklin if ($replace_original_font !== true) { $hyph = '-custom-'; } else { $hyph = '-'; }; $font_families = array( //add your Google fonts and weights (400 and 700 are defaults for normal and bold) here: 'Oswald:200,400,700', 'Lato:200,400,700', ); $query_args = array( 'family' => urlencode( implode( '|', $font_families ) ), 'subset' => urlencode( 'latin,latin-ext' ), ); $fonts_url = add_query_arg( $query_args, 'https://fonts.googleapis.com/css' ); wp_enqueue_style( 'twentyseventeen' ....

How to Make a Website Everyone Has

On The Endless Wonders Of Internet Explorer

May be somebody will stumble upon this post and save some time for him/herself. Apparently—it only become apparent after several hours of trial, cursing and error, as it usually goes with IE—, Internet Explorer (up to version 7) throws a runtime error, if you try to modify innerHTML of the dynamically created element under certain conditions. The conditions, as it always go with IE, are significantly lacking consistent logic. For starters, if you assign innerHTML to the element before you insert it into a DOM tree, the error may not come up at all, but will surface later, when you try to modify it. So far it looks like the error mostly comes up, if you change innerHTML of the block element inserted into inline element (which is not kosher in standard-compliant HTML, so it makes sense), and some nested block elements (like DIVs inside Ps—why is that considered wrong, too?—for instance). So, if one really-really need to insert a division into a paragraph, and w...