Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 107

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 109

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 111

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 112

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 107

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 109

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 111

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 112

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Poor review with heartwarming community response

Whoa, been quite a long time since I’ve blogged last time now and the longer it’s been, I’ve felt that I’ve needed to come up with something of more interest to blog about once I finally do some blogging again… ;)

Well, I read this poor review of Mandriva Linux 2010 (the only poor review I’ve seen so far actually), which I got a bit provoked about, not that much because I’m taking things personal, but it’s rather more about stupid people pisses me off! ;p

The reviewer seemed to only actually try review the One edition and then trailed off making up his own irrelevant and ignorant FUD conclusions about the Powerpack version which he didn’t tested, about how we seemed to be more interested
in pushing proprietary software (despite he later made some ignorat complains about the trouble from lack of this in the Free edition later on), then on and on.
With such amazingly borderline retarded and biased ranted I just had to write a longer comment on the article myself (which is something I seldom do), and in the process I was very happy to see that others shared my annoyance and awareness of ignorance as well- Pretty much all comments flamed the article, most of them based on very nice insight and knowledge about the distribution and it’s strengths, especially in comparision with others, this also from many people who weren’t even using Mandriva!

I found it really nice to see that we seem to finally gain a more favorable impression and also really our users finally growing aware of our strenghts and all.

I really hope to see this being a growing trend with a community hopefully finally starting to really be growing again for real! :)

Oh btw. Happy new year to all of you, even those of you who doesn’t deserve it or that I just don’t like. ;p

    • wobo

    • Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

      Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 107

      Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 109

      Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 111

      Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 112
      December 30th, 2009

    Such bad reviews are often the result of authors who do not know anything about Mandriva Linux and do not take their time to look for infos. Sometimes such authors also have their own opinion about how a Linux distribution should be. As nice as all theose comments are, the damage done (as Jackson Browne would say).

    To avoid this Mandriva users should write their own reviews and offer them to sites who publish reviews, to online magazines and the print media. If such a review is straight, pointing at the strong AND the weak points and does not sound like a fan-boy’s praise, many editors will accept such reviews. They bring a benefit for the reader, the media, for the author and for the distribution. It’s a win:win for all.

    After reading such a bad review about Mandriva 2008.1 another community member and I had this idea and offered it to the chief editor of the German print magazine LinuxUser. Since then he keeps asking for a new review whenever a new release is out. The current review shows 5 pages including screenshots and is not only published in the print edition but also in the online edition.
    And we even get paid! :)

    Now, how about it – start nagging your magazine’s editors!

  1. No trackbacks yet.