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
29 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
4:26 pm
Since Apple reported its first ever quarterly drop in iPod sales earlier this month, the future of the revolutionary music player has become uncertain. However, the company said it expected the decline and created the more advanced iPhone and iPod touch in order to prepare for it. So although the iPod name will live on, the iPod we all know and love will soon be gone.
A recent BusinessWeek article made some predictions about how Apple will change its lineup in the wake of the drop in sales. Apple will:
Get rid of the hard drive-based iPod classic
Focus on high-capacity models that use flash memory (it’s cheaper and more efficient)
Release a new iPod touch with more features, such as a microphone, a camera with video-capability, and a GPS system 
Apple will most likely release a revised product line in September, as it has done in the past few years, and will probably include a new nano and touch. But in the next few years, expect to see familiar models like the iPod classic and nano be discontinued and replaced by more advanced, iPhone-like styles. Despite the great success of the older iPod models, the days of simple, single-function music players are winding down. People want more versatile devices that allow them to do everything at once; luckily Apple has the tools to create this all-encompassing device.
Filed under: Technology
Leave a Reply