In addition to the other responses - every non-vaccinated person who contracts the disease increases the chance that said disease mutates into a form the vaccine can no longer protect against.
And one more: Not everyone who is vaccinated actually becomes immune. Vaccines are highly effective, but they're not 100%.
There are lots of reasons that herd immunity is really important.
Talk to a teenager now and they'll think Katy Perry or Taylor Swift are the best evar!
Pleasantly, I think this may be the generation to break that pattern. Oh, there's a lot of what you say, but I also know a lot of teenagers who listen to a wide variety of music. I think the difference is what you pointed out at the beginning of your post: We live in a golden age of music availability. Not only is basically everything recorded in the last 80 years or so easily available, but its trivial for kids today to carry huge amounts of music around with them, all the time.
My teenage kids, for example, have access to my Google Music All Access subscription, and they've built up huge, eclectic and highly dynamic playlists which are kept always synced to their phones/tablets, including everything you mentioned (Pearl Jam, Zeppelin, Queen, and Katy Perry). Not only that, they also use Pandora and stream Internet radio stations from all over the country, including local bands. And then there's YouTube, which provides everything above, plus lots of interesting covers. One of my sons is a huge Postmodern Jukebox fan, and it's as much for the 40s, etc. music styling as it is for the humor in the juxtaposition of the modern lyrics and old styles. Then there are all the new YouTube musicians, including the likes of Lindsey Stirling, Peter Hollens, the Piano Guys, many of whom would never have gotten airplay or visibility in the old music economy. And the kids love all of them.
Corporate taxes are really just a way to tax individual shareholders, employees and customers, but without any of them noticing that the money is coming out of their pockets. Taxes are necessary, but hidden taxes are evil. Taxes should be visible, so the taxpayers know what they're paying and can weigh it against the value they receive, to decide if they're getting good value for their money, and vote accordingly.
This particular proposal is a great example. Obama wants to go after this particular pool of money because to American taxpayers it appears to be "free" money. It doesn't cost them anything... or at least that's how it looks. I suppose to the extent that this is taxing foreign income generated by foreign workers producing goods and services for sale to foreign customers, it is "free". The only Americans who will be hurt are the Americans who are shareholders in the targeted companies, and there are also plenty of foreign shareholders. So to the extent the money is all foreign, it's taken from foreign taxpayers, which is, if anything, even more insidious.
We do need to maintain our infrastructure, and we should pay for it. But up front and in the open.
It takes an expert in "gas physics" to explain the ideal gas law to them? Didn't these lawyers have to take a basic physics or chemistry course in their undergrad coursework?
"No Android device I'm aware of uses flash for swap"
Then you're not paying attention. There are a number of mods to allow exactly this kind of operation, particularly on older hardware with "only" 1Gb ram.
MicroSD cards are cheap, so burning them out isn't a big deal.
Heh. Obviously I was talking about OEM devices, not user customizations. If you include custom configs you'll find just about everything.
Ah, I see what you're saying. In all of those cases, I'd say Google shifted to working on a component that integrates with other Google services. It does happen that the service-integrated component largely duplicates the features of an existing OSS component, plus adds a lot, but I don't think that's because of any move to close Android.
At this point there's really no need for Google to maintain generic apps for all of those things; there are plenty out there in every category you mentioned. I'm less sure that there are open source apps in all of those categories... but anyone who wants is free to pick up that ball. I suppose it would be nice if Google were to do it, but that's no longer necessary for the success of the platform.
I reiterate that the above represents only my personal opinions. Google pays me to write code, not define platform strategy (except in my narrow area) and certainly not to act as a proper corporate spokesperson. When I say stupid stuff it reflects on me.
It wouldn't be hard to do something nicer, but my Tasker profile is a pretty crude hack. Since I never connect anything that doesn't have its own volume control, I just have a profile that runs every minute and turns the volume up to max. So if anything turns the volume down, it quickly gets turned back up.
The volume thing annoys me, too. I fix it with a Tasker profile.
As for navigation, try using voice to start the navigation. It's zero-click. I don't know that the maps team intentionally increased the number of taps in the non-voice case, but I think it may actually be a good thing for safety if it encourages more people to use voice rather than taking attention to poke at their screen.
That said, I fully agree with the people that are seeing a slow move towards AOSP becoming more and more closed source.
From within Android, I see no such movement. In the short term security concerns have motivated the movement of more stuff into GMS, where it can be updated by Google. Eventually I think the larger update problem will be resolved and that movement will be reversed.
Google is quite happy to see CM and similar third party ROMs flourish
Flourish or tolerate? Honest question. I've seen entire ROMs stymied by small things Google could/should have done as just a decent vendor, regardless of the ROM in question. For instance, a couple years ago the Droid3 port fizzed because the then-Google-owned Motorola wouldn't talk to anybody about releasing specs to turn on the camera.
Flourish.
Your example just demonstrates that Google really did allow Motorola to operate as a separate OEM, not directly influenced by the Android team. It's also possible that Motorola didn't have the option of releasing the specs because of agreements with the camera manufacturer. (Note that I don't know anything about that specific incident, and hadn't even heard of it until you mentioned it. I do know that Google would like its Nexus devices to be much more open than they are, but can't get there without becoming a hardware manufacturer.)
If all life on earth was destroyed, there'd be one hell of a stable equilibrium, but probably not one many of us would like to occur.
If that were an even remotely-likely outcome, it would have happened. Life is extraordinarily good at surviving and evolving new equilibria.
Natural ecosystems can only be expected to be robust against perturbations they have faced regularly for a time, which usually doesn't include much of what humans do.
Meh, the history of life on this planet is one long series of massive, unexpected perturbations, ranging from ice ages so severe that the equatorial seas are covered with several meters of ice, to massive volcanic eruptions that block most global insolation for years, to massive meteor strikes. In addition, the ice core records show that the planet has undergone radical climate change (much faster and more extreme than what we're currently seeing) without any cause at all as far as we can detect, as recent as 60K years ago.
As long as we rely on nature to survive, we shouldn't scoff at the idea that our actions can have disastrous consequences on our own habitat.
Certainly. Equally, we shouldn't ignore the fact that doing nothing at all (assuming we could) will also have disastrous consequences on our own habitat. Earth changes all the time, in all sorts of ways. If we want stability we need to learn to actively engineer the planet.
Okay, but the issue you're complaining about (pocket muting or hanging up) should be impossible on proper hardware regardless of the screen lock status. So with that out of the way, you just disagree with the screen lock behavior. That's your prerogative, but I don't think it's clearly wrong.
Ah, okay. Thanks for the clarification. Yes, there are good reasons that stock Android doesn't use swap, and I can see that people who change that could cause themselves lots of problems:-)
AFAIK, the only MS app Google has blocked was Microsoft's YouTube app, which violated the YouTube terms of service.
Yeah.. well, those "terms of service" was that they required Microsoft to implement their Youtube app in HTML5, while neither the iOS or Android Youtube app had such a requirement and was not implemented in HTML5.
As I recall it was about not making it easy for users to download copies of videos. I could be wrong.
The proximity sensor should make that impossible. Normally the proximity sensor detects when the phone is close you your head and turns off the touchscreen so you don't hang up or mute or whatever with your cheek. It should work equally well in a pocket... no need to muck about with locking. If your Android phone didn't do this, that's the fault of the hardware, not the OS.
Additionally, I personally would argue that from a OMG UNIX has conquered the world perspective that Android == Linux as little as Mac OS X == NetBSD since all the parts that people care about are derivative or proprietary.
That isn't true of Android. Sure, if you're writing in Java the *nix-ness is all abstracted away behind the JVM, but if you choose to write native code, you find yourself right back in Linux-land. There are some oddities, of course, like the assignment of UIDs to apps, rather than users. And starting with Lollipop, SELinux is used to block app native code access to many parts of the system (e.g. you can't go looking around in/proc to find out what else is running). But it's definitely still Linux.
It's not true of OS X, either. Again, there are lots of new APIs layered on top, but it's still very clearly Unix. Maybe you meant iOS, not OS X. In that case, I don't know if you're right or not because I've never worked in iOS.
I think the idea is that Google, Samsung, Motorola, and HTC have all made themselves into a sort of cartel that don't allow the "open source project" to actually be a source of freedom for consumers. Cyanogen is "rogue" because it bucks that system and restores freedom to the project.
Not really. That may be the perception, but it's not true. Google is quite happy to see CM and similar third party ROMs flourish; this is part of why all Nexus devices are unlockable.
(Disclaimer: I'm a Google engineer, and I work on Android, but I'm not a Google spokesperson and this is my opinion, not an official statement.)
the real-world problems of trying to use a phone's flash to do Linux-style virtual memory
No Android device I'm aware of uses flash for swap. There are a small handful that swap to compressed RAM, the fast majority have no swap at all; when physical memory is exhausted something has to die.
Slashdot Mirror
In addition to the other responses - every non-vaccinated person who contracts the disease increases the chance that said disease mutates into a form the vaccine can no longer protect against.
And one more: Not everyone who is vaccinated actually becomes immune. Vaccines are highly effective, but they're not 100%.
There are lots of reasons that herd immunity is really important.
Talk to a teenager now and they'll think Katy Perry or Taylor Swift are the best evar!
Pleasantly, I think this may be the generation to break that pattern. Oh, there's a lot of what you say, but I also know a lot of teenagers who listen to a wide variety of music. I think the difference is what you pointed out at the beginning of your post: We live in a golden age of music availability. Not only is basically everything recorded in the last 80 years or so easily available, but its trivial for kids today to carry huge amounts of music around with them, all the time.
My teenage kids, for example, have access to my Google Music All Access subscription, and they've built up huge, eclectic and highly dynamic playlists which are kept always synced to their phones/tablets, including everything you mentioned (Pearl Jam, Zeppelin, Queen, and Katy Perry). Not only that, they also use Pandora and stream Internet radio stations from all over the country, including local bands. And then there's YouTube, which provides everything above, plus lots of interesting covers. One of my sons is a huge Postmodern Jukebox fan, and it's as much for the 40s, etc. music styling as it is for the humor in the juxtaposition of the modern lyrics and old styles. Then there are all the new YouTube musicians, including the likes of Lindsey Stirling, Peter Hollens, the Piano Guys, many of whom would never have gotten airplay or visibility in the old music economy. And the kids love all of them.
Corporate taxes are really just a way to tax individual shareholders, employees and customers, but without any of them noticing that the money is coming out of their pockets. Taxes are necessary, but hidden taxes are evil. Taxes should be visible, so the taxpayers know what they're paying and can weigh it against the value they receive, to decide if they're getting good value for their money, and vote accordingly.
This particular proposal is a great example. Obama wants to go after this particular pool of money because to American taxpayers it appears to be "free" money. It doesn't cost them anything... or at least that's how it looks. I suppose to the extent that this is taxing foreign income generated by foreign workers producing goods and services for sale to foreign customers, it is "free". The only Americans who will be hurt are the Americans who are shareholders in the targeted companies, and there are also plenty of foreign shareholders. So to the extent the money is all foreign, it's taken from foreign taxpayers, which is, if anything, even more insidious.
We do need to maintain our infrastructure, and we should pay for it. But up front and in the open.
It takes an expert in "gas physics" to explain the ideal gas law to them? Didn't these lawyers have to take a basic physics or chemistry course in their undergrad coursework?
"No Android device I'm aware of uses flash for swap"
Then you're not paying attention. There are a number of mods to allow exactly this kind of operation, particularly on older hardware with "only" 1Gb ram.
MicroSD cards are cheap, so burning them out isn't a big deal.
Heh. Obviously I was talking about OEM devices, not user customizations. If you include custom configs you'll find just about everything.
fast majority
Er, vast majority. If only there were some way to see my post before I submit it...
Yup.
Ah, I see what you're saying. In all of those cases, I'd say Google shifted to working on a component that integrates with other Google services. It does happen that the service-integrated component largely duplicates the features of an existing OSS component, plus adds a lot, but I don't think that's because of any move to close Android.
At this point there's really no need for Google to maintain generic apps for all of those things; there are plenty out there in every category you mentioned. I'm less sure that there are open source apps in all of those categories... but anyone who wants is free to pick up that ball. I suppose it would be nice if Google were to do it, but that's no longer necessary for the success of the platform.
I reiterate that the above represents only my personal opinions. Google pays me to write code, not define platform strategy (except in my narrow area) and certainly not to act as a proper corporate spokesperson. When I say stupid stuff it reflects on me.
It wouldn't be hard to do something nicer, but my Tasker profile is a pretty crude hack. Since I never connect anything that doesn't have its own volume control, I just have a profile that runs every minute and turns the volume up to max. So if anything turns the volume down, it quickly gets turned back up.
The volume thing annoys me, too. I fix it with a Tasker profile.
As for navigation, try using voice to start the navigation. It's zero-click. I don't know that the maps team intentionally increased the number of taps in the non-voice case, but I think it may actually be a good thing for safety if it encourages more people to use voice rather than taking attention to poke at their screen.
Sure, and the history of life on earth is one of massive, unexpected mass extinctions, which often followed those massive, unexpected perturbations
Mass extinctions which are, most likely, also the biggest driver of speciation and diversity :-)
I think the Holocene Extinction may be the exception to that trend, though.
Could be yours is malfunctioning? Mine works.
Um, no. The proximity sensor shouldn't depend on how you're holding it. I'm suggesting hardware defect, not user error.
I'm 90% certain no officially supported device ever used flash memory for swap.
By "officially supported" do you mean officially-supported by CM, or by device vendors?
That said, I fully agree with the people that are seeing a slow move towards AOSP becoming more and more closed source.
From within Android, I see no such movement. In the short term security concerns have motivated the movement of more stuff into GMS, where it can be updated by Google. Eventually I think the larger update problem will be resolved and that movement will be reversed.
Google is quite happy to see CM and similar third party ROMs flourish
Flourish or tolerate? Honest question. I've seen entire ROMs stymied by small things Google could/should have done as just a decent vendor, regardless of the ROM in question. For instance, a couple years ago the Droid3 port fizzed because the then-Google-owned Motorola wouldn't talk to anybody about releasing specs to turn on the camera.
Flourish.
Your example just demonstrates that Google really did allow Motorola to operate as a separate OEM, not directly influenced by the Android team. It's also possible that Motorola didn't have the option of releasing the specs because of agreements with the camera manufacturer. (Note that I don't know anything about that specific incident, and hadn't even heard of it until you mentioned it. I do know that Google would like its Nexus devices to be much more open than they are, but can't get there without becoming a hardware manufacturer.)
If all life on earth was destroyed, there'd be one hell of a stable equilibrium, but probably not one many of us would like to occur.
If that were an even remotely-likely outcome, it would have happened. Life is extraordinarily good at surviving and evolving new equilibria.
Natural ecosystems can only be expected to be robust against perturbations they have faced regularly for a time, which usually doesn't include much of what humans do.
Meh, the history of life on this planet is one long series of massive, unexpected perturbations, ranging from ice ages so severe that the equatorial seas are covered with several meters of ice, to massive volcanic eruptions that block most global insolation for years, to massive meteor strikes. In addition, the ice core records show that the planet has undergone radical climate change (much faster and more extreme than what we're currently seeing) without any cause at all as far as we can detect, as recent as 60K years ago.
As long as we rely on nature to survive, we shouldn't scoff at the idea that our actions can have disastrous consequences on our own habitat.
Certainly. Equally, we shouldn't ignore the fact that doing nothing at all (assuming we could) will also have disastrous consequences on our own habitat. Earth changes all the time, in all sorts of ways. If we want stability we need to learn to actively engineer the planet.
Okay, but the issue you're complaining about (pocket muting or hanging up) should be impossible on proper hardware regardless of the screen lock status. So with that out of the way, you just disagree with the screen lock behavior. That's your prerogative, but I don't think it's clearly wrong.
Ah, okay. Thanks for the clarification. Yes, there are good reasons that stock Android doesn't use swap, and I can see that people who change that could cause themselves lots of problems :-)
Microsoft has in the past complained that Google Inc., which manages Android, has blocked its programs from the operating system."
MS has a bunch of apps in the Play store. https://play.google.com/store/...
AFAIK, the only MS app Google has blocked was Microsoft's YouTube app, which violated the YouTube terms of service.
Yeah.. well, those "terms of service" was that they required Microsoft to implement their Youtube app in HTML5, while neither the iOS or Android Youtube app had such a requirement and was not implemented in HTML5.
As I recall it was about not making it easy for users to download copies of videos. I could be wrong.
The proximity sensor should make that impossible. Normally the proximity sensor detects when the phone is close you your head and turns off the touchscreen so you don't hang up or mute or whatever with your cheek. It should work equally well in a pocket... no need to muck about with locking. If your Android phone didn't do this, that's the fault of the hardware, not the OS.
Additionally, I personally would argue that from a OMG UNIX has conquered the world perspective that Android == Linux as little as Mac OS X == NetBSD since all the parts that people care about are derivative or proprietary.
That isn't true of Android. Sure, if you're writing in Java the *nix-ness is all abstracted away behind the JVM, but if you choose to write native code, you find yourself right back in Linux-land. There are some oddities, of course, like the assignment of UIDs to apps, rather than users. And starting with Lollipop, SELinux is used to block app native code access to many parts of the system (e.g. you can't go looking around in /proc to find out what else is running). But it's definitely still Linux.
It's not true of OS X, either. Again, there are lots of new APIs layered on top, but it's still very clearly Unix. Maybe you meant iOS, not OS X. In that case, I don't know if you're right or not because I've never worked in iOS.
Microsoft has in the past complained that Google Inc., which manages Android, has blocked its programs from the operating system."
MS has a bunch of apps in the Play store. https://play.google.com/store/...
AFAIK, the only MS app Google has blocked was Microsoft's YouTube app, which violated the YouTube terms of service.
I think the idea is that Google, Samsung, Motorola, and HTC have all made themselves into a sort of cartel that don't allow the "open source project" to actually be a source of freedom for consumers. Cyanogen is "rogue" because it bucks that system and restores freedom to the project.
Not really. That may be the perception, but it's not true. Google is quite happy to see CM and similar third party ROMs flourish; this is part of why all Nexus devices are unlockable.
(Disclaimer: I'm a Google engineer, and I work on Android, but I'm not a Google spokesperson and this is my opinion, not an official statement.)
the real-world problems of trying to use a phone's flash to do Linux-style virtual memory
No Android device I'm aware of uses flash for swap. There are a small handful that swap to compressed RAM, the fast majority have no swap at all; when physical memory is exhausted something has to die.
(I work for Google, on the Android OS.)