What happened was that the president of Chik-Fil-A, Dan Cathy, expressed an opinion on same-sex marriage
You forgot to mention the part where Chik-Fil-A's charitable organization was donating millions of dollars to anti-LGBT political organizations. The protests were largely effective at halting those donations.
But, he doesn't claim to be a "Democrat", which is an allegiance which absolves one from all responsibility and repercussions from their opinions.
Obama--for all of his many problems--has done more than any other president to support equal protection under law for people who are LGBT.
Maybe we could just work together on that and then most of these abortions need never happen.
Good idea, but you need to get conservatives on board with embracing contraceptives. For many of them, it isn't just about eliminating abortion, it's also about eliminating non-martial sex and boosting the pregnancy rate after marriage. To get there, they are willing to (1) withhold medically pertinent information, (2) cultivate sexual fears and stigmas, (3) encourage premature marriage, and (4) prescribe rigid/misogynistic gender roles. (Source: grew up in a christian school.) A lot of this just naturally flows from the fundamentalist/authoritarian worldview... other christian subcultures may be different.
The number of unplanned pregnancies in the US every year is Insane.
Download.deb
Double click it
Insert password, hit ok
Seriously it is a hell of a lot easier than Windows
Oh, I'm sorry. You need libglib2.0-0 (>= 2.35.9), but I'm on libglib2.0-0 (2.34.8) and upgrading it will cause a conflict with libwtf5.0 (1:5.0.99) and also require installing libancientrelic0.8 (0.8.0.012), which I can't seem to find anywhere. Let me suggest removing a bunch of packages (leaving some things broken). Accept this solution? (y/N) Alternately, I could suggest you blow your weekend learning to build a dummy package just to shut me up... there so many wonderful commands that start with deb and dpkg, you'll love digging thru layers and layers of accumulated shell scripts!
The true mind-blower of Unix is how so many people defend their flat files unto death
And their scripts. Don't forget the piles upon piles of scripts that preclude any straightforward notion of what's going on. (Coincidentally, dpkg is a good example of this failure too.)
Why? Nothing is blocked, it is just slower. This sucks for streaming, but streaming is not the only way to share information. Speeds that will not work at all for Netflix work fine on The Pirate Bay... It just requires people to think differently and not stream everything but download it instead.
Why? Because now if you want to start an internet business (streaming or not) that becomes even modestly successfully, every ISP on the planet will start looking for a way to demand a chunk of your profits. "Yeah, sorry that that little 100ms latency spike is affecting 1 million customers of yours, Blizzard, but we'll be happy to form a collaborative network-tuning relationship with you for $250,000/mo."
Cumulatively, it means that ISP's can rent-seek off of internet businesses, cutting down on the quantity and competitiveness of such businesses while simultaneously forcing them to raise prices.
The benefit is ease of use for people who have no idea what a URL is. They just look up there and see, "yes, this is definitely my bank's website," instead of "holy shit what does long string of symbols that mean."
Maybe a basic part of web literacy is learning what a URL is and what it's useful for. "Whoa!" you say, "we need to do anything we can to make computers easier and more self-explanatory." Well, yes, I agree with that, but we're reaching a point where designers start to "overtrain" their design. Take this "origin chip", for example. You make it slightly easier to identify the site you're on and perhaps slightly less intimidating for a newbie [which is sort of ridiculous in this context because the web is do damn ubiquitous now], but you've also made a host of other tasks slightly harder (viz., copying/emailing a link, fixing a link, manually entering a link, inspecting a link, etc.). In addition, you're no longer subtly informing the intuitions of future authors, librarians, technicians, webmasters, programmers, and judges/juries as to the URL~=page association. That's ultimately making it harder for people to understand how their technology works.
Usability design is a noble endeavor, and I'm all on board with Norman, Tufte, etc. What I'm NOT on board is the current fad of software that drops functionality, removes technical visibility, and overhauls the interface with each release. That's just user-hostile.
[ranting because Google Camera dropped exposure control recently]
mind-boggling complexity of life that could never be duplicated but by a mind-boggling intelligence
Complexity can arise spontaneously out of simple interactions. We see this over and over and over again. Pretending it requires intelligence just reveals our collective cognitive bias towards personifying the world and ascribing agency to inanimate objects and processes.
This is our tax dollars being spent on a national religion.
No, it's merely a line of scientific questioning that threatens your worldview. A lot of things can threaten a worldview (science, humanities, foreign travel, self-reflection, getting older, etc.), but we should only call them a "religion" if they substantially function like a religion (e.g., providing things like community, life ceremonies, spirituality, moral codes, holy texts, etc.).
Duplicating all pagan religions. They start with water because Genesis starts with the Holy Spirit hovering over the water.
Civilization begins with agriculture, and agriculture begins with water. It was true in lower Mesopotamia (the world's first civilization) and on the banks of the Nile (Egypt, the second civilization). It seems appropriate, then, that many creation myths--including those much older than the Genesis 1:1 account--feature water as prominent (and often chaotic) element.
I know too many smart highly-educated Christians to think that religion is merely some lack of applied thought. It's a choice they made, knowingly and subjectively, to have religious faith.
Skeptics seem to have this assumption that humans are inherently rational, and it's only those who are intellectually weak that let bad/illogical ideas into the mind. I'd argue that this is a bad model because we are forced throughout life to rely on incomplete/inaccurate information from a wide variety of sources... our senses, our emotions, our peers and society at large, etc. Our brains are a very muddy place that was never tidy and logically "clean" to begin with, but we make do (more or less). A purely skeptical species would go extinct questioning the need to plant crops, etc.,
The way I see it, rationality (and the engineered pursuit of it, science) is a skill that must be developed and subsequently imposed on various facets of our worldview. How we select those facets (and how vigorously we investigate them) is a strategic question ("what is my biggest blindspot?") that we're not well equipped to answer (they're called "blindspots" for a reason). And we ALL have blindspots of various topic and magnitude.
In the case of religion, it's particularly hard to investigate these blindspots because adherents have been strongly conditioned to self-identify with the cause. Their parents, friends, community, and everyone they trusted as a child told them "this is what we believe, it is the only way to live a good life, and everything outside of it is corrupt and destructive". Like Tevye says in Fiddler on the Roof, "tradition tells us who we are and what G-d expects of us".
Analytically re-evaluating one's faith as an adult requires a tremendous amount of courage and vigour. To do so, they must overcome:
Religious instructions to defer to authority.
Implied instructions to not question faith.
Perceptions that questioning is risky and/or evil.
The nastiness of some skeptics (e.g., living examples of the "evil" of questioning)
Accusations that the questioner's "real problem" is something spiritual and not intellectual.
Desperate feelings that the faith "has to be true", precluding need for further analysis.
Anecdotal proofs and feel-good stories ("testimonies") that offer emotional evidence for faith.
Single-shot ad hoc arguments (emotional or intellectual) that preclude comprehensive analysis
Apologetics literature or speakers that sound convincing initially, esp. when presented without opposing views.
This is not the only way people leave their faith, but it's relevant to skeptics because it's the "rational" route. I suspect that those who use "emotional evidence" as their primary waypoints for evaluating complex situation have it easier... they see the history of Christanity's/Islam's treatment towards women or they consider how wholly abhorrent the concept of hell is, and then they proceed to reject the system that generated those ideas.
Instead of offering mockery (a tempting practice), skeptics would do better to (1) humbly remember that we all have blindspots, (2) that every population has smart and dumb individuals, (3) that believers make many valuable contributions to rationality/science, (4) and that social and emotional arguments against a faith can compliment their existing intellectual arguments.
Let me elevate the question: why do we need yet another programming language?
Because we're nowhere near figuring out how to best express ourselves to computers for the wide variety of problems we wish to solve and the large diversity of skill-sets and backgrounds we wish to solve them with.
In this example, F# solves the problem of "how do we do statically-typed functional programming (a la OCaml and Haskell) in a way that integrates with the.NET ecosystem?". C# doesn't solve that problem because you can't do nearly enough type theory. OCaml doesn't solve that problem because it's not vendor-supported and it's not designed from the ground up with the.NET platform (and the existing base of C# programmers) in mind.
While I share your unstated assumption... that it seems like there are too many half-baked programming languages instead of a few really good ones, I also think Microsoft deserves credit (much as I hate to say it) for recognizing the need to focus on platforms (like.NET) instead of languages. Of course, then they go and do the whole WinRT thing...:-\
Instead of turning around at the halfway point and using the same thrust to decelerate, would it be possible to, theoretically, initiate an explosion in front of the craft, equal in yield to the amount of thrust used to achieve whatever speed your craft is at when you need to start accelerating?
Yes, because the explosion you propose is simply a shorter duration, higher intensity version of retro-thrusting. (Incidentally, some sci-fi authors have proposed using explosions [such as nukes] for the initial thrust as well [Anathem comes to mind].)
However, the problem with your approach is that it's less efficient: first, it requires extra machinery because you're building a second propulsion system instead of reusing the one you already have; second, it requires extra structural support because you're going to subject the vehicle to higher delta-V's. Obviously, this adds a lot of weight, a lot of extra engineering, and several more points of failure.
The implicit engineering assumption you're running into here is that the most viable approach for interstellar voyages (if anything is viable, which is doubtful) will be a regime of nearly symmetrical acceleration/deceleration provided by a single propulsion system.
The distinction that P algorithms are "efficient" and NP algorithms are "inefficient" is merely a convention of complexity theorists. You could easily draw the dividing line further in or out depending on your purposes. That makes me wonder what constitutes their assumption that this particular P/NP type "efficency" is necessary for a macroscopic Schrodinger algorithm.
If you think this makes a car too expensive, what price do you put on accidentally running over a human being?
This article says it will save (max) 15 deaths/year at a (min) cost of $132/vehicle. With 15.6 million vehicles sold in the US last year, that implies a >$137 million dollars per death avoided. That's way above the $6million you referenced.
At any rate, it certainly seems that if we're going to spend >$2 billion dollars, we should able to save more than 15 lives with it. But no... some mum went to Washington and proclaimed it should "never happen again", so we get this crap. (Granted, my analysis isn't including injuries... that could swing the balance.)
Reality. At the end of the day, what will the insurance company accept as sufficient security...
No, the security only has to be sufficient enough to blame you for the theft.
the balance of easy usability vs number of features vs security implementation, with a modern electric computerised vehicle that might best be left to a consultation between the sales consultant and the end user
The salesman and customer are the least informed for making security tradeoffs, and the complications of having multiple security arrangements across a fleet of supported vehicle isn't worth the extra headache for the manufacturer.
The "balance" of this situation should not lie in the boneheaded territory of elementary security mistakes... if you're going to have a remotely accessible API, hire programmers who understand security and have them design the damn thing to be secure from the ground up. It's not impossible or mystical or some big unknown.
I wonder what other options they investigated... for instance, would it have been feasible to do a spacewalk and relocate foam to critical areas? I know this stuff is way more complicated than any simplistic suggestions from the internet, but NASA pulled hell and high water to bring Apollo 13 home safely. Imminent emergencies have a way bringing out the greatness in an otherwise bureaucratic organization.
You can't control network access outright per-app, that would be nice.
AFWall+ does a great job of that on Android, but it requires root. Using it, I say which apps can use cellular, which can use wifi, and which are isolated completely.
I'd like to define some per-app sandboxes so, for instance, only selected apps can see my "real" contacts... the others would see my "fake" contacts and not know the difference. Ditto for GPS location and countless other things...
If you're not breaking existing laws, why create others to make sure you're less likely to? If you are breaking laws, well - There are already laws in place to enforce that.
Existing laws against reckless driving are full of vague generalities... What exactly constitutes driving with "due care and attention"? As your burrito example indicates, there's a continuum, and reasonable people can reasonably disagree on what's legal and illegal under such statures. Those sort of laws are best reserved for the extreme cases that legislators never could have imagined up front (If that story had been real and if the guy had lived to see a courtroom). New, more targeted laws can set consistent expectations about what's legit and what's not, so that drivers, police, and judges are all on the same page. That's the opposite of "more complicated"... it's simpler because it clarifies what is and is not considered a problem for an extremely frequent set of opportunities (cell phone & texting usage).
(And no, they aren't going to pass a similar law for burrito assembly, because that's extremely uncommon. Sometimes the law is a little bit like code optimization: just as you target the 5% of your code that's taking the bulk of CPU time, so do legislators target specific behaviors that are especially vexing to their constituency/campaign contributors.)
It seems that the only way to enforce "distracted driving" is if the driver is doing something else wrong.
Enforcement is difficult... I know a city jurisdiction that only caught one violator of its anti-texting law in the first year of operation, and it was only because the man admitted his usage to the cop. However, even with minimal enforcement, the mere presence of the law can subtly encourage the right behaviors: humans have a surprisingly strong instinct to follow the rules, especially when this instinct has been cultivated in their upbringing.
They close out "good" questions there too (examples)... came across one the other day (while programming), in fact. It's like the wikipedia notability police all over again.:O
Technically knowledgeable people often give very poor names to their efforts.
I thought "Stack Overflow" was great branding for a website aimed at helping programmers solve technical problems. It's a distinctive, cheeky in-reference understood by its intended audience. (And honestly, it didn't hurt that most developers enjoy being made to feel clever about themselves.) That's what a brand is suppose to do, and it partially* explains their overwhelming success. And hey, much better branding choice than ExpertSexChange.com!
*Of course, branding is just one of many things they did right. They also filled a unique niche, understood their community (because it was started by programmers, for programmers), and made the site super-easy to use by (here comes the important part...) NOT crapping over the UI with a fake paywall that sought rent for years' worth good-faith user contributions. However, they are sort of starting to be dicks about subjective questions (such as help with API choices, etc.). That may provide a niche for a new competitor to fill...
If you apply an update to a customers car and that causes them to crash and burn half their face off, you can bet you'll get sued.
Granted, but that doesn't entirely invalidates JDG1980's point... knowing that lives are on the line will make you a very paranoid coder or tester, but knowing that the code can't ever be changed (without a mountain of hassle) will you make you that much more paranoid.
[Side note: I use the term "paranoid" instead of "cautious" here because paranoid describes the mindset that drives one to examine, poke, and test their code exhaustively from multiple angles. The cautious mindset, by contrast, is the instinct to freeze up and make no changes (especially no innovative changes) altogether. I suppose they both have their place in life-critical systems, but the former is empirical and ambitious while the latter is superstitious and reluctant.]
Groundwater contamination, for one. Especially, flammable tap water. Perhaps you dismiss that as anecdotal, but it's not as if scientist have been given the access, data, and funding to run these claims to ground... that will take another ten or twenty years, by which point the perpetrators will have long since taken off with the profits while the general public gets stuck with whatever environmental catastrophes this created.
Don't get me wrong... I wish fracking was as safe and plentiful as proponents claim. And maybe it's worth some amount of contamination even if it isn't safe. I just wish these things could be determined objectively and scientifically in the best public interest instead of this same old sh*t where the powerful simultaneously exert influence over corporations, media, government, and public opinion to effect the fattest profit instead of the utilitarian good.
It's true with animals too... modern zoo design tries to take this into account by giving the animals places to hide, which benefits their mental health in addition to creating more immersive/meaningful exhibits. It's tricky though, because too much animal hiding => pissed off visitors.
But you'd have to be an idiot to want to check this proof without a computer.
Historically, mathematicians have resisted computer-only proofs. They want eyeballs end-to-end. Your ideas (independent implementations, hardware, etc.) are sound/feasible from a software engineering standpoint, but unsatisfying to mathematicians. (Not being a mathematician myself, I'm ill-suited to testify as to why that's the case, but so it is.)
Maybe one day that mindset will be abandoned, but what's more likely to happen is that mathematics will bifurcate: there will be the set of mathematics that relies on computer proofs and the "pure" subset of that that doesn't require computers. Probably, that's already considered the case. Regardless, this is how the field has dealt with countless other issues (such as not accepting negative proofs), often to great fecundity.
What happened was that the president of Chik-Fil-A, Dan Cathy, expressed an opinion on same-sex marriage
You forgot to mention the part where Chik-Fil-A's charitable organization was donating millions of dollars to anti-LGBT political organizations. The protests were largely effective at halting those donations.
But, he doesn't claim to be a "Democrat", which is an allegiance which absolves one from all responsibility and repercussions from their opinions.
Obama--for all of his many problems--has done more than any other president to support equal protection under law for people who are LGBT.
Maybe we could just work together on that and then most of these abortions need never happen.
Good idea, but you need to get conservatives on board with embracing contraceptives. For many of them, it isn't just about eliminating abortion, it's also about eliminating non-martial sex and boosting the pregnancy rate after marriage. To get there, they are willing to (1) withhold medically pertinent information, (2) cultivate sexual fears and stigmas, (3) encourage premature marriage, and (4) prescribe rigid/misogynistic gender roles. (Source: grew up in a christian school.) A lot of this just naturally flows from the fundamentalist/authoritarian worldview... other christian subcultures may be different.
The number of unplanned pregnancies in the US every year is Insane.
Actually, the rate of teen pregnancies has hit an historic low.
Download .deb
Double click it
Insert password, hit ok
Seriously it is a hell of a lot easier than Windows
Oh, I'm sorry. You need libglib2.0-0 (>= 2.35.9), but I'm on libglib2.0-0 (2.34.8) and upgrading it will cause a conflict with libwtf5.0 (1:5.0.99) and also require installing libancientrelic0.8 (0.8.0.012), which I can't seem to find anywhere. Let me suggest removing a bunch of packages (leaving some things broken). Accept this solution? (y/N) Alternately, I could suggest you blow your weekend learning to build a dummy package just to shut me up... there so many wonderful commands that start with deb and dpkg, you'll love digging thru layers and layers of accumulated shell scripts!
The true mind-blower of Unix is how so many people defend their flat files unto death
And their scripts. Don't forget the piles upon piles of scripts that preclude any straightforward notion of what's going on. (Coincidentally, dpkg is a good example of this failure too.)
As always, the truth is in the Bible
Yep, this speciously-reasoned physics paper supports the Absolute Truth(TM) revealed to us in an ancient text of unknown authorship!
Why? Nothing is blocked, it is just slower. This sucks for streaming, but streaming is not the only way to share information. Speeds that will not work at all for Netflix work fine on The Pirate Bay... It just requires people to think differently and not stream everything but download it instead.
Why? Because now if you want to start an internet business (streaming or not) that becomes even modestly successfully, every ISP on the planet will start looking for a way to demand a chunk of your profits. "Yeah, sorry that that little 100ms latency spike is affecting 1 million customers of yours, Blizzard, but we'll be happy to form a collaborative network-tuning relationship with you for $250,000/mo."
Cumulatively, it means that ISP's can rent-seek off of internet businesses, cutting down on the quantity and competitiveness of such businesses while simultaneously forcing them to raise prices.
The benefit is ease of use for people who have no idea what a URL is. They just look up there and see, "yes, this is definitely my bank's website," instead of "holy shit what does long string of symbols that mean."
Maybe a basic part of web literacy is learning what a URL is and what it's useful for. "Whoa!" you say, "we need to do anything we can to make computers easier and more self-explanatory." Well, yes, I agree with that, but we're reaching a point where designers start to "overtrain" their design. Take this "origin chip", for example. You make it slightly easier to identify the site you're on and perhaps slightly less intimidating for a newbie [which is sort of ridiculous in this context because the web is do damn ubiquitous now], but you've also made a host of other tasks slightly harder (viz., copying/emailing a link, fixing a link, manually entering a link, inspecting a link, etc.). In addition, you're no longer subtly informing the intuitions of future authors, librarians, technicians, webmasters, programmers, and judges/juries as to the URL~=page association. That's ultimately making it harder for people to understand how their technology works.
Usability design is a noble endeavor, and I'm all on board with Norman, Tufte, etc. What I'm NOT on board is the current fad of software that drops functionality, removes technical visibility, and overhauls the interface with each release. That's just user-hostile.
[ranting because Google Camera dropped exposure control recently]
"Culture's worth huge, huge risks. Without culture we're all totalitarian beasts." -- Norman Mailer
mind-boggling complexity of life that could never be duplicated but by a mind-boggling intelligence
Complexity can arise spontaneously out of simple interactions. We see this over and over and over again. Pretending it requires intelligence just reveals our collective cognitive bias towards personifying the world and ascribing agency to inanimate objects and processes.
This is our tax dollars being spent on a national religion.
No, it's merely a line of scientific questioning that threatens your worldview. A lot of things can threaten a worldview (science, humanities, foreign travel, self-reflection, getting older, etc.), but we should only call them a "religion" if they substantially function like a religion (e.g., providing things like community, life ceremonies, spirituality, moral codes, holy texts, etc.).
Duplicating all pagan religions. They start with water because Genesis starts with the Holy Spirit hovering over the water.
Civilization begins with agriculture, and agriculture begins with water. It was true in lower Mesopotamia (the world's first civilization) and on the banks of the Nile (Egypt, the second civilization). It seems appropriate, then, that many creation myths--including those much older than the Genesis 1:1 account--feature water as prominent (and often chaotic) element.
I know too many smart highly-educated Christians to think that religion is merely some lack of applied thought. It's a choice they made, knowingly and subjectively, to have religious faith.
Skeptics seem to have this assumption that humans are inherently rational, and it's only those who are intellectually weak that let bad/illogical ideas into the mind. I'd argue that this is a bad model because we are forced throughout life to rely on incomplete/inaccurate information from a wide variety of sources... our senses, our emotions, our peers and society at large, etc. Our brains are a very muddy place that was never tidy and logically "clean" to begin with, but we make do (more or less). A purely skeptical species would go extinct questioning the need to plant crops, etc.,
The way I see it, rationality (and the engineered pursuit of it, science) is a skill that must be developed and subsequently imposed on various facets of our worldview. How we select those facets (and how vigorously we investigate them) is a strategic question ("what is my biggest blindspot?") that we're not well equipped to answer (they're called "blindspots" for a reason). And we ALL have blindspots of various topic and magnitude.
In the case of religion, it's particularly hard to investigate these blindspots because adherents have been strongly conditioned to self-identify with the cause. Their parents, friends, community, and everyone they trusted as a child told them "this is what we believe, it is the only way to live a good life, and everything outside of it is corrupt and destructive". Like Tevye says in Fiddler on the Roof, "tradition tells us who we are and what G-d expects of us".
Analytically re-evaluating one's faith as an adult requires a tremendous amount of courage and vigour. To do so, they must overcome:
This is not the only way people leave their faith, but it's relevant to skeptics because it's the "rational" route. I suspect that those who use "emotional evidence" as their primary waypoints for evaluating complex situation have it easier... they see the history of Christanity's/Islam's treatment towards women or they consider how wholly abhorrent the concept of hell is, and then they proceed to reject the system that generated those ideas.
Instead of offering mockery (a tempting practice), skeptics would do better to (1) humbly remember that we all have blindspots, (2) that every population has smart and dumb individuals, (3) that believers make many valuable contributions to rationality/science, (4) and that social and emotional arguments against a faith can compliment their existing intellectual arguments.
Let me elevate the question: why do we need yet another programming language?
Because we're nowhere near figuring out how to best express ourselves to computers for the wide variety of problems we wish to solve and the large diversity of skill-sets and backgrounds we wish to solve them with.
In this example, F# solves the problem of "how do we do statically-typed functional programming (a la OCaml and Haskell) in a way that integrates with the .NET ecosystem?". C# doesn't solve that problem because you can't do nearly enough type theory. OCaml doesn't solve that problem because it's not vendor-supported and it's not designed from the ground up with the .NET platform (and the existing base of C# programmers) in mind.
While I share your unstated assumption... that it seems like there are too many half-baked programming languages instead of a few really good ones, I also think Microsoft deserves credit (much as I hate to say it) for recognizing the need to focus on platforms (like .NET) instead of languages. Of course, then they go and do the whole WinRT thing... :-\
Instead of turning around at the halfway point and using the same thrust to decelerate, would it be possible to, theoretically, initiate an explosion in front of the craft, equal in yield to the amount of thrust used to achieve whatever speed your craft is at when you need to start accelerating?
Yes, because the explosion you propose is simply a shorter duration, higher intensity version of retro-thrusting. (Incidentally, some sci-fi authors have proposed using explosions [such as nukes] for the initial thrust as well [Anathem comes to mind].)
However, the problem with your approach is that it's less efficient: first, it requires extra machinery because you're building a second propulsion system instead of reusing the one you already have; second, it requires extra structural support because you're going to subject the vehicle to higher delta-V's. Obviously, this adds a lot of weight, a lot of extra engineering, and several more points of failure.
The implicit engineering assumption you're running into here is that the most viable approach for interstellar voyages (if anything is viable, which is doubtful) will be a regime of nearly symmetrical acceleration/deceleration provided by a single propulsion system.
The distinction that P algorithms are "efficient" and NP algorithms are "inefficient" is merely a convention of complexity theorists. You could easily draw the dividing line further in or out depending on your purposes. That makes me wonder what constitutes their assumption that this particular P/NP type "efficency" is necessary for a macroscopic Schrodinger algorithm.
If you think this makes a car too expensive, what price do you put on accidentally running over a human being?
This article says it will save (max) 15 deaths/year at a (min) cost of $132/vehicle. With 15.6 million vehicles sold in the US last year, that implies a >$137 million dollars per death avoided. That's way above the $6million you referenced.
At any rate, it certainly seems that if we're going to spend >$2 billion dollars, we should able to save more than 15 lives with it. But no... some mum went to Washington and proclaimed it should "never happen again", so we get this crap. (Granted, my analysis isn't including injuries... that could swing the balance.)
Reality. At the end of the day, what will the insurance company accept as sufficient security...
No, the security only has to be sufficient enough to blame you for the theft.
the balance of easy usability vs number of features vs security implementation, with a modern electric computerised vehicle that might best be left to a consultation between the sales consultant and the end user
The salesman and customer are the least informed for making security tradeoffs, and the complications of having multiple security arrangements across a fleet of supported vehicle isn't worth the extra headache for the manufacturer.
The "balance" of this situation should not lie in the boneheaded territory of elementary security mistakes... if you're going to have a remotely accessible API, hire programmers who understand security and have them design the damn thing to be secure from the ground up. It's not impossible or mystical or some big unknown.
their reasoning was that a screen on the controller forced you to split your attention between the TV screen and the controller screen
Yep... glad to see someone is learning from the Wii U's mistakes.
I wonder what other options they investigated... for instance, would it have been feasible to do a spacewalk and relocate foam to critical areas? I know this stuff is way more complicated than any simplistic suggestions from the internet, but NASA pulled hell and high water to bring Apollo 13 home safely. Imminent emergencies have a way bringing out the greatness in an otherwise bureaucratic organization.
You can't control network access outright per-app, that would be nice.
AFWall+ does a great job of that on Android, but it requires root. Using it, I say which apps can use cellular, which can use wifi, and which are isolated completely.
I'd like to define some per-app sandboxes so, for instance, only selected apps can see my "real" contacts... the others would see my "fake" contacts and not know the difference. Ditto for GPS location and countless other things...
If you're not breaking existing laws, why create others to make sure you're less likely to? If you are breaking laws, well - There are already laws in place to enforce that.
Existing laws against reckless driving are full of vague generalities... What exactly constitutes driving with "due care and attention"? As your burrito example indicates, there's a continuum, and reasonable people can reasonably disagree on what's legal and illegal under such statures. Those sort of laws are best reserved for the extreme cases that legislators never could have imagined up front (If that story had been real and if the guy had lived to see a courtroom). New, more targeted laws can set consistent expectations about what's legit and what's not, so that drivers, police, and judges are all on the same page. That's the opposite of "more complicated"... it's simpler because it clarifies what is and is not considered a problem for an extremely frequent set of opportunities (cell phone & texting usage).
(And no, they aren't going to pass a similar law for burrito assembly, because that's extremely uncommon. Sometimes the law is a little bit like code optimization: just as you target the 5% of your code that's taking the bulk of CPU time, so do legislators target specific behaviors that are especially vexing to their constituency/campaign contributors.)
It seems that the only way to enforce "distracted driving" is if the driver is doing something else wrong.
Enforcement is difficult... I know a city jurisdiction that only caught one violator of its anti-texting law in the first year of operation, and it was only because the man admitted his usage to the cop. However, even with minimal enforcement, the mere presence of the law can subtly encourage the right behaviors: humans have a surprisingly strong instinct to follow the rules, especially when this instinct has been cultivated in their upbringing.
You mean like https://programmers.stackexcha... ?
They close out "good" questions there too (examples)... came across one the other day (while programming), in fact. It's like the wikipedia notability police all over again. :O
Technically knowledgeable people often give very poor names to their efforts.
I thought "Stack Overflow" was great branding for a website aimed at helping programmers solve technical problems. It's a distinctive, cheeky in-reference understood by its intended audience. (And honestly, it didn't hurt that most developers enjoy being made to feel clever about themselves.) That's what a brand is suppose to do, and it partially* explains their overwhelming success. And hey, much better branding choice than ExpertSexChange.com!
*Of course, branding is just one of many things they did right. They also filled a unique niche, understood their community (because it was started by programmers, for programmers), and made the site super-easy to use by (here comes the important part...) NOT crapping over the UI with a fake paywall that sought rent for years' worth good-faith user contributions. However, they are sort of starting to be dicks about subjective questions (such as help with API choices, etc.). That may provide a niche for a new competitor to fill...
If you apply an update to a customers car and that causes them to crash and burn half their face off, you can bet you'll get sued.
Granted, but that doesn't entirely invalidates JDG1980's point... knowing that lives are on the line will make you a very paranoid coder or tester, but knowing that the code can't ever be changed (without a mountain of hassle) will you make you that much more paranoid.
[Side note: I use the term "paranoid" instead of "cautious" here because paranoid describes the mindset that drives one to examine, poke, and test their code exhaustively from multiple angles. The cautious mindset, by contrast, is the instinct to freeze up and make no changes (especially no innovative changes) altogether. I suppose they both have their place in life-critical systems, but the former is empirical and ambitious while the latter is superstitious and reluctant.]
Are there risks with fracking?
Groundwater contamination, for one. Especially, flammable tap water. Perhaps you dismiss that as anecdotal, but it's not as if scientist have been given the access, data, and funding to run these claims to ground... that will take another ten or twenty years, by which point the perpetrators will have long since taken off with the profits while the general public gets stuck with whatever environmental catastrophes this created.
Don't get me wrong... I wish fracking was as safe and plentiful as proponents claim. And maybe it's worth some amount of contamination even if it isn't safe. I just wish these things could be determined objectively and scientifically in the best public interest instead of this same old sh*t where the powerful simultaneously exert influence over corporations, media, government, and public opinion to effect the fattest profit instead of the utilitarian good.
Being observed puts people in a stress position.
It's true with animals too... modern zoo design tries to take this into account by giving the animals places to hide, which benefits their mental health in addition to creating more immersive/meaningful exhibits. It's tricky though, because too much animal hiding => pissed off visitors.
But you'd have to be an idiot to want to check this proof without a computer.
Historically, mathematicians have resisted computer-only proofs. They want eyeballs end-to-end. Your ideas (independent implementations, hardware, etc.) are sound/feasible from a software engineering standpoint, but unsatisfying to mathematicians. (Not being a mathematician myself, I'm ill-suited to testify as to why that's the case, but so it is.)
Maybe one day that mindset will be abandoned, but what's more likely to happen is that mathematics will bifurcate: there will be the set of mathematics that relies on computer proofs and the "pure" subset of that that doesn't require computers. Probably, that's already considered the case. Regardless, this is how the field has dealt with countless other issues (such as not accepting negative proofs), often to great fecundity.