Skip to main content

Did Somebody Else, Too, Noticed...

...the surprising level of "doneness" of the top 20 songs, submitted for the American Idol Songwriter Competition is, indeed, just a sign of how well-equipped and prepared all the aspiring songwriters in this country are? I, naturally, expect the work of the professional to be of a better quality, than that of an amateur, but what was that crap about "...you don't have to be a singer, we are going to judge the song, not the performance..." and "...simple rendition with a basic accompaniment is fine...". Yea, right. Just listen to all 20 BORING songs, presented for the America to vote upon.
Another thing which surprised me, was how strangely familiar all of the songs were. I had to force myself to give a couple of them a rating of 7, and that was just because they didn't sound like something I just heard. The rest - in my honestest opinion - deserved no better than 3s and 4s.
Sad.

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...