Also, it seems the poster is really just trying to get attention. Complexity theorists do know all that and have spent a lot of time trying to see which postulated consequences of P?=NP are necessary and which are not.
(If I were to argue it is an ill-posed question, I'd go more in the direction of CO-NP (which is the set of problems for which "NO" answers have short certificates), and why this really strong emphasys on "yes" certificates for NP problems)
Doron Zeilberger's take on that ( http://www.math.rutgers.edu/~zeilberg/Opinion98.html ) is a lot more interesting.
And, also, the "easy" equals "polynomial time" is (a) a good heuristic, if you assume computational power increases exponentially (hence, a problem will be solvable in the foreseeable future if all it needs is polynomially more processing power for larger instances); (b) it is an easy to study class, since it is composable; (c) not the only thing complexity theorists argue about (ie, P=NP means practical bounds for some problems and collapses a lot of classes that are not trivially seen to be equal, like AM and MA)
- The poster is a notable complexity theorist and is not "just trying to get attention".
- Doron Zeilberger's "a lot more interesting" take is completely subsumed in Richard Lipton's blogpost, in that it mentions other possibilities beyond the basic "what if it's polynomial with a really huge exponent" scenario.
- Assuming computational power to increase exponentially indefinitely is completely ridiculous, and without the "indefinitely" part this assumption no longer works to justify "easy = P".
- It is trivial to say that if P=NP, then AM=MA, because both AM and MA are in the polynomial hierarchy, and if P=NP, the hierarchy collapses completely.
- The most important point to be taken away from the blogpost is not just that "easy = P" is an assumption that's been held on too unreflectively and may not turn out to be true. It's that studying what this assumption means, how it could break down, and why it hasn't, by and large, broken down so far, may get us closer to understanding P ?= NP.
He could explain SAT, but then shouldn't he also explain what a randomized algorithm is, why P=NP is (as he says, possibly) relevant to circuit design, what P and NP are, etc. The problem with this approach is that it doesn't know where to stop (explaining what an algorithm is?).
Edit: Oops, must refresh before re-joining a HN thread.
Introduces the term 'SAT' at some point, without explaining what it means. Wikipedia isn't helpful.