So you mean you actually check your phone during meetings, instead of keeping it in your pocket and not letting it steal your attention? Wow. And if you have to check the LED on the phone, can't you just let the phone lie on the table so you can see its display light up, or simply keep it in your pocket and let the vibration do its intended job?
I can see this being a problem for deaf people, but if you're not deaf, what's so horribly problematic with the model all manufacturers have been using the past 15 years, repeating the relevant alarm sound (SMS etc.) once every minute until the user picks the phone up?
I wouldn't consider base64 or RAR "technologies" as such (really, what is it with Americans and considering -everything- a "technology"?). QR coding, data reformatting and data compression, however, are technologies, and I am willing to bet that at least the latter two as well as their histories will be present 30 years from today. These were just suggestions, though. My personal choice would be to keep the documents in their original plaintext format and simply store them somewhere SAFE, rather than trying to compress and/or obfuscate them.
Just to cover more alternatives. But, really, why make things unnecessarily complicated for yourself? If the papers are in your firebox anyway, why encrypt? If you insist, try encrypted RAR with parity, converted to base64 and printed as the resulting plaintext in a decently large print to make sure no smudging will cause trouble during OCR.
I consider the drivers for embedded products like these an integral part of the product; part of the product's quality as a whole. Why on earth would anyone consider differently? What would Android be without the drivers supplied by the vendors of the GPUs used in these SoCs? What would iOS be without ditto?
I never claimed Android was, nor do I see it as a "hokey joke". You're just upset that I pointed out that its UI is a drag, and trying to brush it off by rationalizing about GPU drivers doesn't help any of us customers.
I think the comparison of the two mobile operating systems on this basis is a lot fairer than claimed: my iOS device is an iPhone 4, which runs a Cortex-A8 (a lesser performer than the A9) clocked at about 800 MHz (about 65% of the Android stick's freq.), has 512 MB RAM compared to 1 GB of RAM in the Android stick, and a GPU which is also clocked slower - though I am not familiar with more detailed performance differences between the PowerVR and Mali400 GPUs.
Why do you insist on seeing things in terms of dollars? What I'm using has better specifications in terms of CPU speed, amount of RAM, and GPU power, than the $600 iOS device you are implying that I own. (What I own in terms of iOS actually cost less than $600 when I bought it some years ago, and it has less RAM than the MK808B).
I've been using Android on one for a while
on
Android On the Desktop
·
· Score: -1, Flamebait
I bought an MK808B "Android stick" a few months ago. It's a dual-core ARM A9 running by default at 1 GHz - up to 1.6 GHz technically, but they're not stable up there - which I have overclocked to 1.2 GHz without it crashing on me. It has 1GB of RAM and 8GB of flash memory shared between OS and user-installed apps etc. and comes with Bluetooth, 802.11 b/g/n, two USB ports and a microSD slot that can handle cards up to 32GB.
I run Android 4.2.2 on it, and while I'm at one hand amazed at how sluggish, jerky, freezing, ungainly and wonky Android is in many regards compared to iOS (which is the smoothest, snappiest mobile experience I've ever seen), I'm equally amazed and thoroughly pleased at how very versatile it is due to that "tiny" difference of allowing users somewhat free hands in using the internal storage for their own use. I keep it hooked up to my flat screen TV, and I use it for web browsing, for chatting on IRC and Jabber, for playing games, for watching YouTube, for video playback, for playing music, and even for torrenting - directly to a USB drive I keep next to it - and all of it on a tiny little device that consumes no more than 6 watts of energy when I push it to its limits.
If there's one point worth underlining with Android in contrast to iOS, it's that extra freedom the users get that allows Android to be so versatile. Wouldn't ever dream of running Android on my smartphone, though:)
Why this weird perspective that a "no meat" diet is out of the question? Why even think in terms of eating bugs and insects as a last resort instead of just... not?
We use the OpenBitTorrent tracker and the Transmission client to deploy and acquire virtual machine hard drive images among our developers. The obvious reason is that it's much faster for our developers to help eachother out with shoveling the data around rather than the developers having to get all the data from one and the same link (read: the main server).
Compare it to a person reading a novel, once, out loud, to a group of people, instead of reading it in private over and over to each and every attendee.
"but without all the mess" - as long as you don't count the mess that come with society's backbone starting to wobble. Our infrastructure's and societal functions' dependency on the Internet is grossly underestimated. This is a fact.
I've been using wifi instead of ethernet for about 7 years now. Almost all of the NICs/APs I've used have displayed this problem with time. It's as if the equipment somehow develops creeping signal attenuation. My guess is that it's something relating to capacitors gathering a slow overcharge of some sort, causing them to block current in a growing fashion - I seem to recall this being possible from my early days of electronics studies.
Anyhoo, I fix the problem by simply switching the equipment to another channel, say, 3-4 steps away, to make sure the frequency some of the components will be switching at will be notably different. So far it has worked with all equipment I've had this problem show up on. After a while the signal attenuation develops on the new channel as well, upon which I simply switch back to the one I used before. Rinse, repeat.
...an ethernet socket in my apartment. The maximum I can subscribe to is 1000/100 - yes, that's gigabit ethernet down - for 70 EUR/month. What I'm currently buying via the same socket is 25/10 mbit/s, which costs me about 24 EUR/month, which is just over $30. I get this through this building being connected to my municipal city network in which multiple operators can do business. This method is getting very common here in Sweden.
I'm not sure which year you are discussing in, but the situation of the article refers to how the available options stand TODAY, not as they stood in 2008 or 2007, when not even direct GPU transcoding was available in a functional form. If you have a 4 years old HD4xxx series GPU, you can run OpenCL 1.0/1.1 software on it. Period. I don't see the point of you mentioning super computer clusters running CUDA in this discussion. Are these clusters available to us for transcoding video on our GPUs? Not likely. Take a look at how much OpenCL software is available compared to how much CUDA software is available, and you will see which "camp" is the popular one. Hint: it's not CUDA.
I'm sorry, but you don't seem to have a clue as to what you are talking about. I don't understand why your response was upvoted, as it's highly fallacious - If a person is already sitting on a GPU modern enough to support the direct GPU-powered transcoding solutions offered by the manufacturer, then said GPU is also OpenCL-capable.
ATI's GPUs have been OpenCL 1.0 (and up) capable for 4 years now. OpenCL 1.0 opened up already on the HD4xxx series released in 2008. Nvidia was a bit behind as they were still dabbling with CUDA - which has never really taken off - and didn't offer OpenCL capability until two years ago, in early 2010.
Slashdot Mirror
So you mean you actually check your phone during meetings, instead of keeping it in your pocket and not letting it steal your attention? Wow. And if you have to check the LED on the phone, can't you just let the phone lie on the table so you can see its display light up, or simply keep it in your pocket and let the vibration do its intended job?
I can see this being a problem for deaf people, but if you're not deaf, what's so horribly problematic with the model all manufacturers have been using the past 15 years, repeating the relevant alarm sound (SMS etc.) once every minute until the user picks the phone up?
I'm not an anti-Apple dullard, believe me, but this thought must've stricken at least a few of the readers.
The English version should be seventeen words over three lines, holding five, seven and five words respectively.
Try either of these: http://dx.com/p/175870 http://dx.com/p/208694 and run http://code.google.com/p/rk3066-linux/ on it.
I haven't powered my Pi up once since I bought the simpler one with 1GB of RAM.
A plethora of solutions already do this, without the overhead of reinventing the wheel. Check out http://preyproject.com/
http://preyproject.com/
I wouldn't consider base64 or RAR "technologies" as such (really, what is it with Americans and considering -everything- a "technology"?). QR coding, data reformatting and data compression, however, are technologies, and I am willing to bet that at least the latter two as well as their histories will be present 30 years from today. These were just suggestions, though. My personal choice would be to keep the documents in their original plaintext format and simply store them somewhere SAFE, rather than trying to compress and/or obfuscate them.
Just to cover more alternatives. But, really, why make things unnecessarily complicated for yourself? If the papers are in your firebox anyway, why encrypt? If you insist, try encrypted RAR with parity, converted to base64 and printed as the resulting plaintext in a decently large print to make sure no smudging will cause trouble during OCR.
I consider the drivers for embedded products like these an integral part of the product; part of the product's quality as a whole. Why on earth would anyone consider differently? What would Android be without the drivers supplied by the vendors of the GPUs used in these SoCs? What would iOS be without ditto?
I never claimed Android was, nor do I see it as a "hokey joke". You're just upset that I pointed out that its UI is a drag, and trying to brush it off by rationalizing about GPU drivers doesn't help any of us customers.
I think the comparison of the two mobile operating systems on this basis is a lot fairer than claimed: my iOS device is an iPhone 4, which runs a Cortex-A8 (a lesser performer than the A9) clocked at about 800 MHz (about 65% of the Android stick's freq.), has 512 MB RAM compared to 1 GB of RAM in the Android stick, and a GPU which is also clocked slower - though I am not familiar with more detailed performance differences between the PowerVR and Mali400 GPUs.
Why do you insist on seeing things in terms of dollars? What I'm using has better specifications in terms of CPU speed, amount of RAM, and GPU power, than the $600 iOS device you are implying that I own. (What I own in terms of iOS actually cost less than $600 when I bought it some years ago, and it has less RAM than the MK808B).
I bought an MK808B "Android stick" a few months ago. It's a dual-core ARM A9 running by default at 1 GHz - up to 1.6 GHz technically, but they're not stable up there - which I have overclocked to 1.2 GHz without it crashing on me. It has 1GB of RAM and 8GB of flash memory shared between OS and user-installed apps etc. and comes with Bluetooth, 802.11 b/g/n, two USB ports and a microSD slot that can handle cards up to 32GB. I run Android 4.2.2 on it, and while I'm at one hand amazed at how sluggish, jerky, freezing, ungainly and wonky Android is in many regards compared to iOS (which is the smoothest, snappiest mobile experience I've ever seen), I'm equally amazed and thoroughly pleased at how very versatile it is due to that "tiny" difference of allowing users somewhat free hands in using the internal storage for their own use. I keep it hooked up to my flat screen TV, and I use it for web browsing, for chatting on IRC and Jabber, for playing games, for watching YouTube, for video playback, for playing music, and even for torrenting - directly to a USB drive I keep next to it - and all of it on a tiny little device that consumes no more than 6 watts of energy when I push it to its limits. If there's one point worth underlining with Android in contrast to iOS, it's that extra freedom the users get that allows Android to be so versatile. Wouldn't ever dream of running Android on my smartphone, though :)
...when people with a fundamentally flawed understanding of computer communication try their hands at digital cryptography.
Why this weird perspective that a "no meat" diet is out of the question? Why even think in terms of eating bugs and insects as a last resort instead of just... not?
Dunno. I think Chrome, Chromium, Safari and a few others could've been done in one throw of a stone.
We use the OpenBitTorrent tracker and the Transmission client to deploy and acquire virtual machine hard drive images among our developers. The obvious reason is that it's much faster for our developers to help eachother out with shoveling the data around rather than the developers having to get all the data from one and the same link (read: the main server). Compare it to a person reading a novel, once, out loud, to a group of people, instead of reading it in private over and over to each and every attendee.
"but without all the mess" - as long as you don't count the mess that come with society's backbone starting to wobble. Our infrastructure's and societal functions' dependency on the Internet is grossly underestimated. This is a fact.
Been there, too.
This is a very dangerous road Google is heading down on. Let's just see what happens.
I've been using wifi instead of ethernet for about 7 years now. Almost all of the NICs/APs I've used have displayed this problem with time. It's as if the equipment somehow develops creeping signal attenuation. My guess is that it's something relating to capacitors gathering a slow overcharge of some sort, causing them to block current in a growing fashion - I seem to recall this being possible from my early days of electronics studies.
Anyhoo, I fix the problem by simply switching the equipment to another channel, say, 3-4 steps away, to make sure the frequency some of the components will be switching at will be notably different. So far it has worked with all equipment I've had this problem show up on. After a while the signal attenuation develops on the new channel as well, upon which I simply switch back to the one I used before. Rinse, repeat.
...an ethernet socket in my apartment. The maximum I can subscribe to is 1000/100 - yes, that's gigabit ethernet down - for 70 EUR/month. What I'm currently buying via the same socket is 25/10 mbit/s, which costs me about 24 EUR/month, which is just over $30. I get this through this building being connected to my municipal city network in which multiple operators can do business. This method is getting very common here in Sweden.
I'm not sure which year you are discussing in, but the situation of the article refers to how the available options stand TODAY, not as they stood in 2008 or 2007, when not even direct GPU transcoding was available in a functional form. If you have a 4 years old HD4xxx series GPU, you can run OpenCL 1.0/1.1 software on it. Period. I don't see the point of you mentioning super computer clusters running CUDA in this discussion. Are these clusters available to us for transcoding video on our GPUs? Not likely. Take a look at how much OpenCL software is available compared to how much CUDA software is available, and you will see which "camp" is the popular one. Hint: it's not CUDA.
I'm sorry, but you don't seem to have a clue as to what you are talking about. I don't understand why your response was upvoted, as it's highly fallacious - If a person is already sitting on a GPU modern enough to support the direct GPU-powered transcoding solutions offered by the manufacturer, then said GPU is also OpenCL-capable.
ATI's GPUs have been OpenCL 1.0 (and up) capable for 4 years now. OpenCL 1.0 opened up already on the HD4xxx series released in 2008. Nvidia was a bit behind as they were still dabbling with CUDA - which has never really taken off - and didn't offer OpenCL capability until two years ago, in early 2010.
...since the results of OpenCL code is static across GPUs rather than being an arbitrary output.