Warning: mktime() [
function.mktime]: 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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
41
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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
50
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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
52
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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
54
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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
55
Warning: mktime() [
function.mktime]: 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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
41
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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
50
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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
52
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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
54
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 'America/New_York' for 'EDT/-4.0/DST' instead in
/data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line
55
posted on
Warning: mktime() [function.mktime]: 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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 41
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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 50
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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 52
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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 54
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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 55
27 July 2009 at
Warning: mktime() [function.mktime]: 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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 41
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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 50
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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 52
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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 54
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 'America/New_York' for 'EDT/-4.0/DST' instead in /data/4/0/1/57/327709/user/333901/htdocs/blog/wp-includes/functions.php on line 55
3:13 pm
Remember watching science-fiction movies and thinking that the super-smart robots could probably become a reality some time in the far-off future? Well according to a recent New York Times article, the “far-off future” may be sooner than we thought.
A group of computer scientists is currently debating whether research should be controlled to avoid the fast-approaching possibility of robots becoming as intelligent as humans. They are worried that further technological advances could destroy jobs, cause serious social disturbances, and even have dangerous consequences. One of the researchers’ big concerns stems from the fact that robots that can kill autonomously either already exist or soon will. If criminals get control over artificial intelligence systems, there is no way of knowing how far they’ll be able to go.
But the same research that has led to these potentially dangerous robots has also led to many positive developments, including significant progress in the medical field. So what happens when restrictions on research prevent both the bad and the good results?
Filed under: Technology
Leave a Reply