...nothing is going to happen. There's no submarine patents possible here. (...from Facebook, anyhow.)
So, better make sure nothing you use has any form of smart overdraw reduction, dom diffing, etc., before you pick a patent fight with Facebook.
Of course, a cursory glance suggests every modern frontend UI library will violate that patent, so I still don't see a reason to avoid React; Vue, Angular, and recent versions of Ember are all just as much in violation. Guess we're back to static HTML and PHP. :)
(More seriously, hopefully it won't go anywhere; it's pretty clearly got a ton of prior art. But given how broken the patent system is, who knows?)
However, imho one of the major problems with software related patents is allowing an extremely ambiguous language in a field where exact language is the native form of expression.
It simultaneously makes it excessively expensive to challenge a patent, and almost impossible to divine if a particular implementation is covered.
There is code I've written that a client wanted to patent, and knowing the nature of the code, it's not a snowball's chance in hell I would recognise that (my own) algorithm if it was written in patentese, at least without spending days on it.
I don't even want to think about how many hours of legal fees it would cost to challenge even such a minor algorithm.