The Nokia is a bit of a niche market though - the ipod has the benefit of being able to be used by your average joe for a zillion things, largely due to the app store. It's also cheaper, and has a faster CPU.
Also... as most library sites don't use flash, this is very unlikely to be an issue.
Gotta say the cheapest iPod touch is probably going to be a good bet here, particularly as it's a wifi-only device; you don't have to buy a whole cellphone at the same time.
...I would be pretty worried about now. That looks like the kind of deal that could see Google offering free, ad-supported ebooks. Admittedly this has a far larger scope than just the kindle et al, but it could certainly have some major consequences in that area.
It's not a bug. == is supposed to be used for weakly-typed comparisons, and === for strongly-typed ones. If you care about type, just use === and everything will be fine - that's *exactly* what the operator is there for!!
Those operators are not used enough in modern times to justify dedicated characters in my opinion. They should be library function calls.
Sheesh, when was the last time you did any serious PHP dev? Haven't you ever noticed how the whole bloody thing is *completely* crammed full of bitwise operations designed to make development more efficient? Have you never had to maintain code, or written code, that uses the same approach?
As an example, let's compare PHP's implementation of curl_setopt() and error_reporting(). With error_reporting(), you just pass it a pile of stuff with bitwise:
error_reporting(E_ALL & ~E_NOTICE);
The above code will switch on all error reporting options *except* E_NOTICE. To do the same thing without the use of bitwise operators results in something like curl_setopt(). Every single option needs to be individually set, and you end up with a huge long list of calls to curl_setopt() for something that should be a one-liner.
To clarify this point, here's what error_reporting() would have to look like to achieve the same thing as the above example if bitwise operators were removed:
That, in a nutshell, is a perfect example of just why bitwise operators are still very much a valid language function! There are also many other uses which I won't get into here, but needless to say they're far from dead. I use them many, many times per day in the course of my work, and I doubt there are many (if any) serious PHP developers who wouldn't agree with my opinion on this.
Unless it's a generic vulnerability in the TCP spec, in which case almost every implementation of it would be vulnerable - including all those Linux machines.
Linux is not some magical shield, it takes responsible use to keep it secure.
$80/month for 10m down, 2m up. Cable internet with a 20GB cap. This is the best commonly available residential connection in New Zealand, and even then it's only in two cities (Wellington & Christchurch)...
Rockbox now has a native USB stack, although it's disabled by default - you'll need to compile a custom build to enable this ( with USE_ROCKBOX_USB and USE_HIGH_SPEED). For the most part, it works impressively well.
That's exactly what sony did - their reader runs Linux, and is very easily hackable. Don't know what the kindle uses though - my guess is also Linux, but a lot more locked-down.
...Could take the display and turn it into something else like "a dirt cheap e-book reader."
Not possible without dismantling the panel. What you need to remember about this screen is that it doesn't have the control matrix laid out in a grid (with each line 1px wide) like an ebook reader does. Instead, the matrix is composed of discrete sections. These sections cannot be changed without physically dismantling the screen and replacing the active layer, which can't easily be done without destroying the screen.
And lets not forget that you would need to make javascript fast on IE. Good luck with that...
Mozilla is doing just that - they're in the process of developing an IE plugin to port the entire firefox javascript engine over into the IE environment. It should run on at least IE 6+.
Slashdot Mirror
The Nokia is a bit of a niche market though - the ipod has the benefit of being able to be used by your average joe for a zillion things, largely due to the app store. It's also cheaper, and has a faster CPU. Also... as most library sites don't use flash, this is very unlikely to be an issue.
Gotta say the cheapest iPod touch is probably going to be a good bet here, particularly as it's a wifi-only device; you don't have to buy a whole cellphone at the same time.
Which I think they probably are, noting that 64bit flash was available on the Linux platform before any of the others.
That's a bloody inefficient computer!
Epic correctional fail. kWh was correct.
I'm sure some writer has thought of this at some point.
Peter F. Hamilton has thought of this, and written about several different ways of implementing the concept.
It gives you a key insight into their insurance liability and the liklihood of your needing to replace them a few months down the track ;-).
Probably because the BOFH was leasing them as secondlife grid units each night...
You see, non-virtualised instances are like kittens with replacable nametags.
No. With youtube, you agree to their using your copyrighted content by uploading it. You gave them consent.
With the google books thing, they just took it.
...I would be pretty worried about now. That looks like the kind of deal that could see Google offering free, ad-supported ebooks. Admittedly this has a far larger scope than just the kindle et al, but it could certainly have some major consequences in that area.
Is this the New Zealand National Library archival scrape we're talking about here?
It's not a bug. == is supposed to be used for weakly-typed comparisons, and === for strongly-typed ones. If you care about type, just use === and everything will be fine - that's *exactly* what the operator is there for!!
Those operators are not used enough in modern times to justify dedicated characters in my opinion. They should be library function calls.
Sheesh, when was the last time you did any serious PHP dev? Haven't you ever noticed how the whole bloody thing is *completely* crammed full of bitwise operations designed to make development more efficient? Have you never had to maintain code, or written code, that uses the same approach?
As an example, let's compare PHP's implementation of curl_setopt() and error_reporting(). With error_reporting(), you just pass it a pile of stuff with bitwise:
error_reporting(E_ALL & ~E_NOTICE);
The above code will switch on all error reporting options *except* E_NOTICE. To do the same thing without the use of bitwise operators results in something like curl_setopt(). Every single option needs to be individually set, and you end up with a huge long list of calls to curl_setopt() for something that should be a one-liner.
To clarify this point, here's what error_reporting() would have to look like to achieve the same thing as the above example if bitwise operators were removed:
error_reporting(E_ERROR, true);
error_reporting(E_WARNING, true);
error_reporting(E_PARSE, true);
error_reporting(E_NOTICE, false);
error_reporting(E_CORE_ERROR, true);
error_reporting(E_CORE_WARNING, true);
error_reporting(E_COMPILE_ERROR, true);
error_reporting(E_COMPILE_WARNING, true);
error_reporting(E_USER_ERROR, true);
error_reporting(E_USER_WARNING, true);
error_reporting(E_USER_NOTICE, false);
error_reporting(E_RECOVERABLE_ERROR, true);
That, in a nutshell, is a perfect example of just why bitwise operators are still very much a valid language function! There are also many other uses which I won't get into here, but needless to say they're far from dead. I use them many, many times per day in the course of my work, and I doubt there are many (if any) serious PHP developers who wouldn't agree with my opinion on this.
step 5: ??? step 6: profit!!!
Unless it's a generic vulnerability in the TCP spec, in which case almost every implementation of it would be vulnerable - including all those Linux machines. Linux is not some magical shield, it takes responsible use to keep it secure.
Coral Cache (just in case): http://debeveiligingsupdate.nl.nyud.net/audio/bevupd_0003.mp3
$80/month for 10m down, 2m up. Cable internet with a 20GB cap. This is the best commonly available residential connection in New Zealand, and even then it's only in two cities (Wellington & Christchurch)...
Rockbox has all of this.
You will need to download the source, and compile it with USE_ROCKBOX_USB and USE_HIGH_SPEED defined.
Rockbox now has a native USB stack, although it's disabled by default - you'll need to compile a custom build to enable this ( with USE_ROCKBOX_USB and USE_HIGH_SPEED). For the most part, it works impressively well.
That's exactly what sony did - their reader runs Linux, and is very easily hackable. Don't know what the kindle uses though - my guess is also Linux, but a lot more locked-down.
...Could take the display and turn it into something else like "a dirt cheap e-book reader."
Not possible without dismantling the panel. What you need to remember about this screen is that it doesn't have the control matrix laid out in a grid (with each line 1px wide) like an ebook reader does. Instead, the matrix is composed of discrete sections. These sections cannot be changed without physically dismantling the screen and replacing the active layer, which can't easily be done without destroying the screen.
And lets not forget that you would need to make javascript fast on IE. Good luck with that...
Mozilla is doing just that - they're in the process of developing an IE plugin to port the entire firefox javascript engine over into the IE environment. It should run on at least IE 6+.
That attack was via flash, not javascript.
I have some mixed filling about that.
Congratulations, you are now officially a sandwich!