If P = NP that implies that *all* problems of at least NP complexity are equivalent to P complexity. This implies that we should be able to solve *any* NP problem with a P solution. That's what the debate is about and why many people have for years now thought that P != NP. The intuition says that NP must be a harder complexity class and P is a sub-set within it otherwise we would be seeing general solutions for NP-hard problems that run in P time. The solutions to NP-hard problems we have today that approach this are very specialized corner-case NP problems. This would be another benefit to actually proving P != NP. We would be able to more accurately categorize higher level complexity beyond P into the other classes you mentioned as well as domain-specific sub-classes.
Multiple correlations. Not just one. From one experiment. Multiple from multiple experiments attempting to test multiple facets of the same problem domain. Yes, correlation and causation are correlated! One more so than the other!
It's reliant on instruments that have variable value and are inherently risky. This completely ignores the time value of money because accolades are awarded on nominal values rather the actual distributions that come out of a trust or fund. Tell me the *total* amount distributed and how that has impacted the world and you might get some applause from me.
Why would you assume I stated it for honor. I stated it for truth. I will continue to slaughter animals and eat their flesh without guilt so long as I am alive.
Bees aren't native to North America and aren't the only pollinators. Also, it might be important to note that something like 40% of bee hives are transported to California yearly solely for the purposes of running on the gigantic food industry there. Maybe we should be re-thinking how we do food and why bees are such a critical part of it. I eat beef and cows don't need bees.
Personally I think "exposing" objects is the problem. Your border should be a mailbox that exchanges messages and those messages should be inspected carefully before internal delivery. I have no idea why people want to dump a class they wrote onto a live internet service and just hope that it dumps data into the correct table somewhere. They dragged the "security api" icon onto the project space so it's secure.
I've looked at protocol buffers but everything I've ever read about people actually using them in production says they are a nightmare over time because they are binary. Supposedly the object versioning alleviates some of this but I think people were complaining about how to deal with mandatory fields over time. I can't remember but I suspect this plus JavaScript being in the browser is what makes JSON so prevalent. I have no idea why XML is used. I can't even think of a single advantage it has over anything. I guess I should just be glad ASN.1 didn't become more popular.
Data by itself doesn't do much. The way to think about data is that it is being fed into a machine that is doing stuff. That means I can program the internal state of that machine using data. Normally we just call this "processing" but bugs like this illustrate that you have to be very careful with how you handle state. Even for "simple" formats that are just "text" like JSON, XML, YAML, and everything else. Image (binary) formats are also not immune as there have been browser attacks using bugs in common image libraries. If your data is used as input, it is executing passively.
JSON or YAML are probably both fine. XML is simply wasteful and unnecessary. Personally I think we should be using something like s-expressions (lisp-like). People hate them because of the parens but every other encoding has as many negative points in different ways. The advantage is that the syntax is far simpler to understand and parse leading to safer software. Some might say that having an "executable" format is bad but I'd point to bugs like this as being proof that even "text" formats are just executables in disguise. The Lisp creed is "data is code" and I've come to agree.
Damage to the carrier is the least of my worries. If an explosive device ever went off on a British carrier, I'd be far more worried about the political response and what that would mean for freedom. The towers coming down didn't end the world but it sure changed the way the US views things like flying.
While I applaud the effort, attempting to clean up HTTP at this point seems blasphemous. I mean how many unused codes would remain if this one was removed? We only use like 5 right now anyway. I say keep it because it is a scar and you should be proud of your scars, HTTP. Leper protocols are people, too.
It's not YOUR beach either. Or the public's since no such thing exists. Technically the "public" contains all dead persons in the past as well as unborn persons of the future. It's especially the people of the future who matter for these things since the reason we arrive at where we are today is because of the decisions of prior people's before us.
This will happen as long as people think they can control land or control the use of it. You can only control yourself and your surroundings. While a beach is nice, if every asshole and his mom are going to live there, you will have to put up with fights over control of it. The rich have more resources to apply force and the poor have a will to anger. It won't change because all of them feel they OWN a piece of dirt and sky. This is all of civilized history.
Tear down the walls. Tear down the fences. Read some Prudhomme. Property is the root of all evil.
This whole thing is strange because it mentions that they have to vest for two or three years before cashing out. It sounds like Amazon is both taking advantage of share dilution and a loop-hole for tax-free payments via stock. It ends up working out for the employee because they don't pay taxes on the "income". I guess in the US that would probably be taxed at 15% under capital gains but IANATL.
It would depend on British law. In the US you have to exercise the option and turn it into actual stock before you have a tax liability. It's possible that British law just includes stock options are part of your overall compensation and uses some nominal market value to report it. It does seem weird to me to include non-vested options in a dynamic financial instrument as "compensation" even if it is used to supplement actual money.
I find it interesting that there is so much fear here. People are both afraid of what can be said as well as saying anything that might be offensive. We need to bring back the flame wars and asbestos suits. It hardens you.
Slashdot Mirror
Twitch.tv has an illegal... wait ... /me watches c-net on ustream... wait
If P = NP that implies that *all* problems of at least NP complexity are equivalent to P complexity. This implies that we should be able to solve *any* NP problem with a P solution. That's what the debate is about and why many people have for years now thought that P != NP. The intuition says that NP must be a harder complexity class and P is a sub-set within it otherwise we would be seeing general solutions for NP-hard problems that run in P time. The solutions to NP-hard problems we have today that approach this are very specialized corner-case NP problems. This would be another benefit to actually proving P != NP. We would be able to more accurately categorize higher level complexity beyond P into the other classes you mentioned as well as domain-specific sub-classes.
Multiple correlations. Not just one. From one experiment. Multiple from multiple experiments attempting to test multiple facets of the same problem domain. Yes, correlation and causation are correlated! One more so than the other!
Hitler drank mother's milk. Think of the children.
It's reliant on instruments that have variable value and are inherently risky. This completely ignores the time value of money because accolades are awarded on nominal values rather the actual distributions that come out of a trust or fund. Tell me the *total* amount distributed and how that has impacted the world and you might get some applause from me.
Why would you assume I stated it for honor. I stated it for truth. I will continue to slaughter animals and eat their flesh without guilt so long as I am alive.
From the thing you tried to defeat me with:
"Most people don’t realize that there were no honey bees in America until the white settlers brought hives from Europe."
We call them native because we are stupid.
As long as I am alive, the slaughter of animals will be performed.
When we open their hives and see that they actively store and eat pollen. Because we can see it with our eyes. Our eyes speak bee.
Bees aren't native to North America and aren't the only pollinators. Also, it might be important to note that something like 40% of bee hives are transported to California yearly solely for the purposes of running on the gigantic food industry there. Maybe we should be re-thinking how we do food and why bees are such a critical part of it. I eat beef and cows don't need bees.
Personally I think "exposing" objects is the problem. Your border should be a mailbox that exchanges messages and those messages should be inspected carefully before internal delivery. I have no idea why people want to dump a class they wrote onto a live internet service and just hope that it dumps data into the correct table somewhere. They dragged the "security api" icon onto the project space so it's secure.
I've looked at protocol buffers but everything I've ever read about people actually using them in production says they are a nightmare over time because they are binary. Supposedly the object versioning alleviates some of this but I think people were complaining about how to deal with mandatory fields over time. I can't remember but I suspect this plus JavaScript being in the browser is what makes JSON so prevalent. I have no idea why XML is used. I can't even think of a single advantage it has over anything. I guess I should just be glad ASN.1 didn't become more popular.
Data by itself doesn't do much. The way to think about data is that it is being fed into a machine that is doing stuff. That means I can program the internal state of that machine using data. Normally we just call this "processing" but bugs like this illustrate that you have to be very careful with how you handle state. Even for "simple" formats that are just "text" like JSON, XML, YAML, and everything else. Image (binary) formats are also not immune as there have been browser attacks using bugs in common image libraries. If your data is used as input, it is executing passively.
JSON or YAML are probably both fine. XML is simply wasteful and unnecessary. Personally I think we should be using something like s-expressions (lisp-like). People hate them because of the parens but every other encoding has as many negative points in different ways. The advantage is that the syntax is far simpler to understand and parse leading to safer software. Some might say that having an "executable" format is bad but I'd point to bugs like this as being proof that even "text" formats are just executables in disguise. The Lisp creed is "data is code" and I've come to agree.
Damage to the carrier is the least of my worries. If an explosive device ever went off on a British carrier, I'd be far more worried about the political response and what that would mean for freedom. The towers coming down didn't end the world but it sure changed the way the US views things like flying.
Insects win by being small, fast, and numerous. Give the Chinese enough money and time...
Windows? The O/S that launched a multi-billion dollar virus industry because of its horrible programming? Flawless.
They do. Some of their protected works are on the block in 2020, iirc. I've been waiting years now to see how they are going to extend it again.
While I applaud the effort, attempting to clean up HTTP at this point seems blasphemous. I mean how many unused codes would remain if this one was removed? We only use like 5 right now anyway. I say keep it because it is a scar and you should be proud of your scars, HTTP. Leper protocols are people, too.
It's not YOUR beach either. Or the public's since no such thing exists. Technically the "public" contains all dead persons in the past as well as unborn persons of the future. It's especially the people of the future who matter for these things since the reason we arrive at where we are today is because of the decisions of prior people's before us.
This will happen as long as people think they can control land or control the use of it. You can only control yourself and your surroundings. While a beach is nice, if every asshole and his mom are going to live there, you will have to put up with fights over control of it. The rich have more resources to apply force and the poor have a will to anger. It won't change because all of them feel they OWN a piece of dirt and sky. This is all of civilized history.
Tear down the walls. Tear down the fences. Read some Prudhomme. Property is the root of all evil.
This whole thing is strange because it mentions that they have to vest for two or three years before cashing out. It sounds like Amazon is both taking advantage of share dilution and a loop-hole for tax-free payments via stock. It ends up working out for the employee because they don't pay taxes on the "income". I guess in the US that would probably be taxed at 15% under capital gains but IANATL.
It would depend on British law. In the US you have to exercise the option and turn it into actual stock before you have a tax liability. It's possible that British law just includes stock options are part of your overall compensation and uses some nominal market value to report it. It does seem weird to me to include non-vested options in a dynamic financial instrument as "compensation" even if it is used to supplement actual money.
Are they worth paying if they end up breaking your society apart?
I find it interesting that there is so much fear here. People are both afraid of what can be said as well as saying anything that might be offensive. We need to bring back the flame wars and asbestos suits. It hardens you.
Truth was a meme... once...