Anything that takes power by USB, even a Raspberry Pi.
From a more practical standpoint, handheld game consoles. I regularly power my 3DS XL from a USB battery pack (you can buy USB to 3DS cables), and I believe the Vita uses USB natively.
OP could have worded it more clearly, but was correct in that USB 3.0 cables do not work on USB 2.0 phones. They are not backwards compatible. You're using a USB 3.0 cable with a USB 3.0 phone.
You said "plugged in to a USB 2.0 slot charging my phone", and since there aren't any phones with full-sized USB ports, that means the phone's USB 2.0 slot must be micro, and a USB 3.0 micro cable can't be used on a phone with a USB 2.0 micro port.
There are not any phones on the market that have full-sized USB sockets, so a "USB 3.0 cable" that connects to a phone must be using a micro connector (there is no mini variant of USB 3).
It's possible that the only reason that Lightning made it into phones was because they wanted to get rid of the 30-pin connector, but USB-C was still a few years away. Or that USB-C was too big, since USB-C sockets are a bunch thicker than Lightning sockets and when Lightning was introduced, Apple probably had a decent idea how thick their upcoming iPhone and iPad products were going to be.
No, you don't. Micro USB 3 connectors are stupid wide (we're talking as wide as a full-sized USB connector), and are not compatible with micro USB 2 ports.
The reverse is sort of true (you can plug a micro 2 cable into a micro 3 port), but since the ports are such different sizes, many consumers probably wouldn't figure that out.
Assuming you're coming from Europe, you're going to have other issues, since there's more than just a voltage difference. There's also a frequency difference, with Europe using 50Hz and North America using 60Hz. Things like a kettle probably don't care, though.
North American homes use a split-phase system which means they have both 120v and 240v. Typically high-power appliances use the 240v, such as dryers, large air conditioners, ovens, etc.
Isn't the whole point of stuff like SolarCity that you have no up-front cost (because you lease the system) and a negative monthly cost (because the monthly lease is cheaper than the cost of the electricity you saved)?
Why does the government need to give people free solar panels when it costs them zero dollars to get a full solar setup from SolarCity?
You're overstating the capabilities of Windows 3.0 (Multi-tasking? Not with most apps) and understanding the capabilities of System 6 and 7 (Hierarchical filesystem? Yeah, but with much longer filenames). Windows 3.x was a usability nightmare, but it didn't really matter, because MacOS didn't see any real improvements for a full decade after that, letting Microsoft catch up and then surpass Apple in the operating system game.
Windows was such a huge pain back in those days, while MacOS (which wasn't really called that at the time) blew it out of the water, particularly when it came to multitasking.
Of course, MacOS sat still for years, lacking protected memory or pre-emptive multitasking until they scrapped the whole thing and replaced it with NeXTSTEP to produce OS X, so Windows eventually caught up and then surpassed it. I had enough issues with Win95/98 and the DOS legacy to say that Windows probably didn't catch up (with a consumer OS) until Win2K, which surpassed MacOS, and that ruled the roost for a few years. OS X didn't come out until over a year later, and the early versions of that were super rough.
But once they all evolved to a certain point, I think that the operating system mattered a lot less. They all got good enough that the users don't have to care about the low-level features, and there are utilities to tweak them any way you like, so it's really just down to personal preference at this point. You're going to run most of the same software no matter what OS you pick, and operating systems are increasingly just "the software that runs your web browser".
Wanting a feature phone makes about as much sense as wanting an old wooden phone with a separate earpiece and the cone that you have to shout into. Technology doesn't stand still, and most feature phones are going to have poor reception since they won't support any of the newer networks. For example, Bell Canada's network is HSPA+, and does not support 2G GSM at all.
With smartphones available for forty to fifty bucks (like the Lumia 530), feature phones just don't make sense.
Notice and notice has only been in effect a few months. Bell and Rogers both stopped throttling in 2012 (although Bell announced they'd stop in very late 2011).
Neither Bell nor Rogers have throttled anything for years. Both abandoned their practices voluntarily after regulatory pressure, and more recent regulation (the ITMP framework) essentially forbids throttling as Bell and Rogers had originally implemented it.
Bell Canada shows a 70% reduction, and Rogers shows a 15% reduction... and yet they are comparable ISPs of similar size who share the majority of their territory.
But that's the thing: in most home theatre setups, you're never even exposed to the UI of your television. It stays locked on one input permanently (the input from your AV receiver), you're not adjusting settings after the initial setup, you're not using it to change channels or volume or mute... The interfaces that you're going to interact with will be from your TV service box, your game consoles, your streaming box, etc.
So what is the TV other than a passive display to display the output of other devices?
But they couldn't have differentiated themselves. The television market is highly competitive, with intense pressure driving manufacturers to minimum margins. For Apple to justify a price premium, they would have needed some sort of compelling features to differentiate it from every other television, and it seems that they weren't confident that they could do that.
Many of the things that differentiate them with other products (excellent build quality/fit and finish and the benefits of their vertical integration) don't really apply to a TV. You don't tend to notice build quality on something like a TV that you never really handle directly, and there isn't a huge amount to be gained in terms of vertical integration with a television versus connecting an external device by HDMI.
We limit our scrums to 15 minutes per day. If it's taking longer than that, you're doing something wrong. Your teams are too big, or your sprints are too long, or you're going into too much detail on items, etc.
It supports some Linux devices running ARM, but in those cases it's pretty specific support. Like, ChromeOS supports Netflix, and that's Linux, and it's sometimes on ARM, but it's not a generic case.
Slashdot Mirror
DVI-D can carry HDMI with audio, so... no.
Anything that takes power by USB, even a Raspberry Pi.
From a more practical standpoint, handheld game consoles. I regularly power my 3DS XL from a USB battery pack (you can buy USB to 3DS cables), and I believe the Vita uses USB natively.
OP could have worded it more clearly, but was correct in that USB 3.0 cables do not work on USB 2.0 phones. They are not backwards compatible. You're using a USB 3.0 cable with a USB 3.0 phone.
You said "plugged in to a USB 2.0 slot charging my phone", and since there aren't any phones with full-sized USB ports, that means the phone's USB 2.0 slot must be micro, and a USB 3.0 micro cable can't be used on a phone with a USB 2.0 micro port.
So your phone has a micro USB 3 connector on it, not a USB 2.0 port as your original post stated.
This doesn't change the fact that a micro USB 3 cable will not fit into a micro USB 2 port.
There are not any phones on the market that have full-sized USB sockets, so a "USB 3.0 cable" that connects to a phone must be using a micro connector (there is no mini variant of USB 3).
It's possible that the only reason that Lightning made it into phones was because they wanted to get rid of the 30-pin connector, but USB-C was still a few years away. Or that USB-C was too big, since USB-C sockets are a bunch thicker than Lightning sockets and when Lightning was introduced, Apple probably had a decent idea how thick their upcoming iPhone and iPad products were going to be.
No, you don't. Micro USB 3 connectors are stupid wide (we're talking as wide as a full-sized USB connector), and are not compatible with micro USB 2 ports.
The reverse is sort of true (you can plug a micro 2 cable into a micro 3 port), but since the ports are such different sizes, many consumers probably wouldn't figure that out.
Assuming you're coming from Europe, you're going to have other issues, since there's more than just a voltage difference. There's also a frequency difference, with Europe using 50Hz and North America using 60Hz. Things like a kettle probably don't care, though.
North American homes use a split-phase system which means they have both 120v and 240v. Typically high-power appliances use the 240v, such as dryers, large air conditioners, ovens, etc.
Isn't the whole point of stuff like SolarCity that you have no up-front cost (because you lease the system) and a negative monthly cost (because the monthly lease is cheaper than the cost of the electricity you saved)?
Why does the government need to give people free solar panels when it costs them zero dollars to get a full solar setup from SolarCity?
Smartphones don't need data plans. They work just fine on voice-only plans.
You're overstating the capabilities of Windows 3.0 (Multi-tasking? Not with most apps) and understanding the capabilities of System 6 and 7 (Hierarchical filesystem? Yeah, but with much longer filenames). Windows 3.x was a usability nightmare, but it didn't really matter, because MacOS didn't see any real improvements for a full decade after that, letting Microsoft catch up and then surpass Apple in the operating system game.
Windows was such a huge pain back in those days, while MacOS (which wasn't really called that at the time) blew it out of the water, particularly when it came to multitasking.
Of course, MacOS sat still for years, lacking protected memory or pre-emptive multitasking until they scrapped the whole thing and replaced it with NeXTSTEP to produce OS X, so Windows eventually caught up and then surpassed it. I had enough issues with Win95/98 and the DOS legacy to say that Windows probably didn't catch up (with a consumer OS) until Win2K, which surpassed MacOS, and that ruled the roost for a few years. OS X didn't come out until over a year later, and the early versions of that were super rough.
But once they all evolved to a certain point, I think that the operating system mattered a lot less. They all got good enough that the users don't have to care about the low-level features, and there are utilities to tweak them any way you like, so it's really just down to personal preference at this point. You're going to run most of the same software no matter what OS you pick, and operating systems are increasingly just "the software that runs your web browser".
Wanting a feature phone makes about as much sense as wanting an old wooden phone with a separate earpiece and the cone that you have to shout into. Technology doesn't stand still, and most feature phones are going to have poor reception since they won't support any of the newer networks. For example, Bell Canada's network is HSPA+, and does not support 2G GSM at all.
With smartphones available for forty to fifty bucks (like the Lumia 530), feature phones just don't make sense.
Notice and notice has only been in effect a few months. Bell and Rogers both stopped throttling in 2012 (although Bell announced they'd stop in very late 2011).
The solution doesn't work, because your first step takes you to the south pole, and it's impossible to travel west from the south pole.
Neither Bell nor Rogers have throttled anything for years. Both abandoned their practices voluntarily after regulatory pressure, and more recent regulation (the ITMP framework) essentially forbids throttling as Bell and Rogers had originally implemented it.
Bell Canada shows a 70% reduction, and Rogers shows a 15% reduction... and yet they are comparable ISPs of similar size who share the majority of their territory.
But that's the thing: in most home theatre setups, you're never even exposed to the UI of your television. It stays locked on one input permanently (the input from your AV receiver), you're not adjusting settings after the initial setup, you're not using it to change channels or volume or mute... The interfaces that you're going to interact with will be from your TV service box, your game consoles, your streaming box, etc.
So what is the TV other than a passive display to display the output of other devices?
But they couldn't have differentiated themselves. The television market is highly competitive, with intense pressure driving manufacturers to minimum margins. For Apple to justify a price premium, they would have needed some sort of compelling features to differentiate it from every other television, and it seems that they weren't confident that they could do that.
Many of the things that differentiate them with other products (excellent build quality/fit and finish and the benefits of their vertical integration) don't really apply to a TV. You don't tend to notice build quality on something like a TV that you never really handle directly, and there isn't a huge amount to be gained in terms of vertical integration with a television versus connecting an external device by HDMI.
Huh? We've been burdened with far more documentation work since we went agile than before we did... It's all formalized now.
We limit our scrums to 15 minutes per day. If it's taking longer than that, you're doing something wrong. Your teams are too big, or your sprints are too long, or you're going into too much detail on items, etc.
It supports some Linux devices running ARM, but in those cases it's pretty specific support. Like, ChromeOS supports Netflix, and that's Linux, and it's sometimes on ARM, but it's not a generic case.
Sorry, 2.2 or later.