The chances of you dying by holding your breath are slim to none (and even then slim only in a handful of cases where holding the breath isn't the cause but rather the trigger to some other underlying serious condition). Even if you can somehow overcome the body's gasp reflex when deprived of oxygen while conscious, you'd pass out long before you died and your body would start breathing again at that point.
I must be working for the wrong companies - hell I've even worked for government departments in the health sector and accessibility still seems to be universally ignored (in fact, in that instance I made sure while I was on board that the site was fully WCAG compliant - I was the only one internally pushing for this and the second I left they did a new deployment which failed on almost every point, yet they still left up their "WCAG compliant" self-congratulatory page), or it'll be something as primitive as ensuring images have alt attributes, or if they're really progressive, that text can be resized. The fact that even government departments, which were meant to be a minimum of Level AA compliant when I worked for them, are still getting this so wrong years after the DDA and nobody has been brought to task over it shows that the likelihood of legislation making much of a dent is minimal - it's toothless legislations and the only way this will work is if it starts hitting the bottom line and sites start getting sued/fined enough to make them sit up and take notice.
That only makes sense if a single generation of teachers teach a single generation of kids, but I know that a lot of the teachers who taught me 20+ years ago are still teaching today, so it's either been a gradual slip or you're seriously suggesting a new generation of teachers can come in and wipe out everything that's gone before.
That's fine if you're saying "there is a blank space, fill in the blank". On the other hand, if you're presenting a parenthesis and just expecting them to know what they're meant to do, how is that any different to presenting an x and expecting them to know what to do? Unfortunately we don't know which approach they took - maybe the former and people are having difficulty with the concept of "=", or maybe the latter and whoever wrote the test is having difficulty with the concept of writing tests.
It's probably even worse than half introducing it - anyone who is already reasonably familiar with algebra (and I'm guessing that's a decent proportion of people here who ever dug around in code before they hit algebra in school) will find it counter intuitive, wondering how you assign value to a void. In other words it's confusing to the kids who are having trouble with maths, and it's confusing to the kids who are forging ahead on their own in maths.
Of course it matters if you're substituting a non-standard format for the question. For all we know () may mean execute the command to this point then continue to process, similar to writing: ( 4 + 3 + 2 = x ) + 2, in which case the answer would be 11. So all we can really deduce from this is that unclear instructions lead to vague conclusions - it would be interesting to at least see the test repeated in the standard format and see if that makes a difference, perhaps it wouldn't and people really are struggling with "=" but I'd be mildly surprised if that was the case.
And yet thestatistics suggest it's not a stereotype but that it's a fact. Of course, the figures tend to be for entire countries or regions, it's more than possible that you live in an area of the states with lower than average obesity or that the places you visited had higher than average obesity rates than the rest of those countries, but overall the world is generally getting fatter and North America still tops the scales.
Google have funded plenty of worthwhile IT projects (and even in the advertising realm they prevented us from being buried until a sea of flashy advertising banners every time we did a search - maybe you don't remember the early search portals).
Google's implementation allows you to open, write and send an email using voice commands, then use the same voice command software to do a web search or call a friend, a reasonably mature cross application voice recognition application. If I understand correctly, what your iPhone is doing isn't answering questions, it's just recognising a set command and reading back a string of text in response - it's trivial to do and the Android would be more than capable, however there are many music players for the device so whether anyone actually thought it a useful enough feature to incorporate into their player is another question.
Why not? It's not like voice navigation negates the ability to type an address if it doesn't recognise what you've said. Even if it only works 50% of the time it's still going to be a massive time saver. In practice I use this with my sat nav all the time and it's surprisingly accurate, even when driving at speed on a noisy motorway.
Actually the ketchup you buy seems sweeter than what comes in baked beans. In experimenting to find the right quantities to make barbecue baked beans I found a ratio of 3 parts HP brown to 1 part Heinz ketchup to be just right, as the sweetness of the ketchup takes the sharp edge off the brown. Add to the beans in quantities to taste:)
Not necessarily - in the UK if you order tea it pretty much always comes with milk unless you specify otherwise, so tea, Early Grey, black would be a perfectly cromulent order over here.
Yes, there are all kinds of reasons why it's useful to have the name - maybe it's for authentication, voice patterns change under different conditions, the computer can probably compensate for this to some degree but it's going to be far less processor intensive if it's doing so using a known word like the name (it can apply its stress algorithms to the finite list of names and find possible matches then filter on these for the other words in the sentence). Alternatively, maybe it's a redundant practice used as a failsafe in case an issue with the computer means reliance on an older communication channel that doesn't do on the fly voice recognition. Ultimately we know it's actually because it's less confusing to the audience, we know when they start a sentence that way they're talking to the computer and not to thin air, but that doesn't mean there aren't also valid reasons why it might be so.
What if they found during tests that there were too many instances where people had to say their own name (imagine if your name was also a common word like Brown or Green), or where people clambering into a Jefferies tube would accidentally tap activate their communicator and so they decided a two-stage activation was best, you can do either on it's own and the request times out unless you do the other within X seconds (still going to be an issue when you're asking for the green tool case while climbing into a Jefferies tube, but far less common).
The only difference worth noting is probably live wallpapers - most branded phones have them enabled by default. If you're really struggling for power, try a standard wallpaper and see if that helps. Aside from that I'd guess the differences in how the ROMs use the battery are minimal (it's more likely that people who have the know-how to root the phone are also more capable of micro-managing their power usage).
Ditto on the 36 hours with a HTC Desire (which I think is pretty close to Nexus in specs). The key for me is managing mobile data and gps (I always have wifi enabled as I use it throughout the day) and leaving bluetooth off. Doing this I can still use the phone for what I consider "heavy" usage and have it last until the next day, although in practice it means it's usually 40%+ charged at night when I plug it in. Another thing to note, some people suggest that once the battery is fully charged, it stops charging and thereafter loses charge because it doesn't detect the fall off and charge again - therefore if you plug it in to charge earlier in the evening, you might find you've already lost 10% in the morning, if this is the case just unplug it and pop it back on charge while you're getting ready and you'll probably squeeze a couple extra hours out of it.
Well people claim the batteries don't need conditioning, but that in many cases it takes a few charge/discharge cycles for the software to correctly display the charge level. I know in my case when I first got my Desire, I decided to completely discharge it - it was already pretty low after the day's use but it took over 2 hours of streaming HD Youtube video to kill it, I suspect the charge was actually much higher than what was being reported, and since then my reported charge always seems higher than it used to after similar levels of use (this might just be psychological I guess - maybe I was playing with the phone more in the first few days).
Considering we've gone from, what, 14.4k to approaching Gb speeds in the space of less than 20 years? I don't think it's unreasonable to build in some future redundancy - after all, the majority of the cost is going to be physically putting the cable in place, the cost to increase the capacity of said cable is likely to be close to incidental.
It seems he's only calling the leap from 100Mbps to 1Gbps implausible, rather than the plan to lay the 100Mbps infrastructure. I don't know what the cost differences are between 100Mbps and 1Gbps but I would have thought they'd be negligible compared to the cost of putting any infrastructure in place.
It also doesn't preclude them charging for it in the future (maybe a GoTY edition with some unique extras) or bundling it with some of their other releases and charging for the whole pack (a la Orange Box), or even using the popularity to sell the console ports. Plenty of ways to profit from an initial zero price (assuming you have a product that's worth more than zero, just giving stuff out for free obviously won't help if nobody wanted it - fortunately Valve seem to have a good hit to miss ratio).
The exploit didn't originate from outside, the exploit is a flaw in the OS - unless you just mean an exploit in the OS which was actively being targetted by users from outside (it's worth clarifying as there was a lot of assumption in the beginning that this was somehow Adobe's fault since it was the PDF renderer).
The chances of you dying by holding your breath are slim to none (and even then slim only in a handful of cases where holding the breath isn't the cause but rather the trigger to some other underlying serious condition). Even if you can somehow overcome the body's gasp reflex when deprived of oxygen while conscious, you'd pass out long before you died and your body would start breathing again at that point.
I must be working for the wrong companies - hell I've even worked for government departments in the health sector and accessibility still seems to be universally ignored (in fact, in that instance I made sure while I was on board that the site was fully WCAG compliant - I was the only one internally pushing for this and the second I left they did a new deployment which failed on almost every point, yet they still left up their "WCAG compliant" self-congratulatory page), or it'll be something as primitive as ensuring images have alt attributes, or if they're really progressive, that text can be resized. The fact that even government departments, which were meant to be a minimum of Level AA compliant when I worked for them, are still getting this so wrong years after the DDA and nobody has been brought to task over it shows that the likelihood of legislation making much of a dent is minimal - it's toothless legislations and the only way this will work is if it starts hitting the bottom line and sites start getting sued/fined enough to make them sit up and take notice.
That only makes sense if a single generation of teachers teach a single generation of kids, but I know that a lot of the teachers who taught me 20+ years ago are still teaching today, so it's either been a gradual slip or you're seriously suggesting a new generation of teachers can come in and wipe out everything that's gone before.
Well actually you are, but it doesn't = being incorrect either. ;-)
I got halfway through your comment but then this weird "=" symbol confused the hell out of me...
When I was taught it was always an underscore. It seems to me they're testing the teaching method and not the underlying knowledge.
That's fine if you're saying "there is a blank space, fill in the blank". On the other hand, if you're presenting a parenthesis and just expecting them to know what they're meant to do, how is that any different to presenting an x and expecting them to know what to do? Unfortunately we don't know which approach they took - maybe the former and people are having difficulty with the concept of "=", or maybe the latter and whoever wrote the test is having difficulty with the concept of writing tests.
It's probably even worse than half introducing it - anyone who is already reasonably familiar with algebra (and I'm guessing that's a decent proportion of people here who ever dug around in code before they hit algebra in school) will find it counter intuitive, wondering how you assign value to a void. In other words it's confusing to the kids who are having trouble with maths, and it's confusing to the kids who are forging ahead on their own in maths.
Of course it matters if you're substituting a non-standard format for the question. For all we know () may mean execute the command to this point then continue to process, similar to writing: ( 4 + 3 + 2 = x ) + 2, in which case the answer would be 11. So all we can really deduce from this is that unclear instructions lead to vague conclusions - it would be interesting to at least see the test repeated in the standard format and see if that makes a difference, perhaps it wouldn't and people really are struggling with "=" but I'd be mildly surprised if that was the case.
I've never heard the term "United Kingdomian" but plenty of people use the term "Brit" to indicate someone from the UK.
And yet the statistics suggest it's not a stereotype but that it's a fact. Of course, the figures tend to be for entire countries or regions, it's more than possible that you live in an area of the states with lower than average obesity or that the places you visited had higher than average obesity rates than the rest of those countries, but overall the world is generally getting fatter and North America still tops the scales.
Google have funded plenty of worthwhile IT projects (and even in the advertising realm they prevented us from being buried until a sea of flashy advertising banners every time we did a search - maybe you don't remember the early search portals).
Maybe, with a minor tweak, Simon?
Google's implementation allows you to open, write and send an email using voice commands, then use the same voice command software to do a web search or call a friend, a reasonably mature cross application voice recognition application. If I understand correctly, what your iPhone is doing isn't answering questions, it's just recognising a set command and reading back a string of text in response - it's trivial to do and the Android would be more than capable, however there are many music players for the device so whether anyone actually thought it a useful enough feature to incorporate into their player is another question.
Why not? It's not like voice navigation negates the ability to type an address if it doesn't recognise what you've said. Even if it only works 50% of the time it's still going to be a massive time saver. In practice I use this with my sat nav all the time and it's surprisingly accurate, even when driving at speed on a noisy motorway.
Actually the ketchup you buy seems sweeter than what comes in baked beans. In experimenting to find the right quantities to make barbecue baked beans I found a ratio of 3 parts HP brown to 1 part Heinz ketchup to be just right, as the sweetness of the ketchup takes the sharp edge off the brown. Add to the beans in quantities to taste :)
Not necessarily - in the UK if you order tea it pretty much always comes with milk unless you specify otherwise, so tea, Early Grey, black would be a perfectly cromulent order over here.
Yes, there are all kinds of reasons why it's useful to have the name - maybe it's for authentication, voice patterns change under different conditions, the computer can probably compensate for this to some degree but it's going to be far less processor intensive if it's doing so using a known word like the name (it can apply its stress algorithms to the finite list of names and find possible matches then filter on these for the other words in the sentence). Alternatively, maybe it's a redundant practice used as a failsafe in case an issue with the computer means reliance on an older communication channel that doesn't do on the fly voice recognition. Ultimately we know it's actually because it's less confusing to the audience, we know when they start a sentence that way they're talking to the computer and not to thin air, but that doesn't mean there aren't also valid reasons why it might be so.
What if they found during tests that there were too many instances where people had to say their own name (imagine if your name was also a common word like Brown or Green), or where people clambering into a Jefferies tube would accidentally tap activate their communicator and so they decided a two-stage activation was best, you can do either on it's own and the request times out unless you do the other within X seconds (still going to be an issue when you're asking for the green tool case while climbing into a Jefferies tube, but far less common).
The only difference worth noting is probably live wallpapers - most branded phones have them enabled by default. If you're really struggling for power, try a standard wallpaper and see if that helps. Aside from that I'd guess the differences in how the ROMs use the battery are minimal (it's more likely that people who have the know-how to root the phone are also more capable of micro-managing their power usage).
Ditto on the 36 hours with a HTC Desire (which I think is pretty close to Nexus in specs). The key for me is managing mobile data and gps (I always have wifi enabled as I use it throughout the day) and leaving bluetooth off. Doing this I can still use the phone for what I consider "heavy" usage and have it last until the next day, although in practice it means it's usually 40%+ charged at night when I plug it in. Another thing to note, some people suggest that once the battery is fully charged, it stops charging and thereafter loses charge because it doesn't detect the fall off and charge again - therefore if you plug it in to charge earlier in the evening, you might find you've already lost 10% in the morning, if this is the case just unplug it and pop it back on charge while you're getting ready and you'll probably squeeze a couple extra hours out of it.
Well people claim the batteries don't need conditioning, but that in many cases it takes a few charge/discharge cycles for the software to correctly display the charge level. I know in my case when I first got my Desire, I decided to completely discharge it - it was already pretty low after the day's use but it took over 2 hours of streaming HD Youtube video to kill it, I suspect the charge was actually much higher than what was being reported, and since then my reported charge always seems higher than it used to after similar levels of use (this might just be psychological I guess - maybe I was playing with the phone more in the first few days).
Considering we've gone from, what, 14.4k to approaching Gb speeds in the space of less than 20 years? I don't think it's unreasonable to build in some future redundancy - after all, the majority of the cost is going to be physically putting the cable in place, the cost to increase the capacity of said cable is likely to be close to incidental.
It seems he's only calling the leap from 100Mbps to 1Gbps implausible, rather than the plan to lay the 100Mbps infrastructure. I don't know what the cost differences are between 100Mbps and 1Gbps but I would have thought they'd be negligible compared to the cost of putting any infrastructure in place.
It also doesn't preclude them charging for it in the future (maybe a GoTY edition with some unique extras) or bundling it with some of their other releases and charging for the whole pack (a la Orange Box), or even using the popularity to sell the console ports. Plenty of ways to profit from an initial zero price (assuming you have a product that's worth more than zero, just giving stuff out for free obviously won't help if nobody wanted it - fortunately Valve seem to have a good hit to miss ratio).
The exploit didn't originate from outside, the exploit is a flaw in the OS - unless you just mean an exploit in the OS which was actively being targetted by users from outside (it's worth clarifying as there was a lot of assumption in the beginning that this was somehow Adobe's fault since it was the PDF renderer).