That's true. I wonder if they'd steer clear of Preact just because it is similar to React though? Also, Preact seems to be heavily reliant on the React ecosystem and it wouldn't be much of a rage quit if they picked up the skinnier version of React when that is what they should be doing anyways because... you know... bandwidth.
I agree that the risk of running into legal trouble with Facebook is pretty low for many companies. However, that doesn't make it feel any less dirty. It would be nice if the lawyers at Facebook would take a chill pill on this one but that will never happen. It will be interesting to see where OSS projects from Facebook go moving forward given that the noise surrounding their patent clause seems to get louder and louder.
On a side note - I'll bet WordPress get's rewritten in Vue.js
Same boat. I use Atom with vim keybindings now and I feel much more productive than when I rolled with straight vim + tmux. Great tools, but there are much better options these days.
According to the Supreme Court you don't have any expectation of privacy in information given to a third party so whether the VPN is in the US or not does not matter.
So, assuming you actually have a patent, and Facebook actually decides to infringe on that patent, the worst case scenario is that you lose your license to use React. There are principles of fairness and equity in the law that would allow you to stop using React in a reasonable amount of time. So write your frontend in Elm. It probably needed a rewrite anyways.
It definitely could be the case that the jurors came up with the numbers they did in order to put Gawker out of business. However, a jury can't just make a random number up. The awarded amount has to be supported by evidence or an appeals court will strike it down as unconstitutional.
I've been involved in a number of trials and my experience leads me to believe that a lot of what is behind a damages award has to do with the show put on by the plaintiffs attorney. If the plaintiffs attorney can anchor high and get experts to support the damages they are asking for anything can happen. This is perhaps one of the main downsides/upsides to a trial by jury. Depending on which side you are on this is a good or very bad thing.
This is a duty of loyalty issue. When there is a board decision and a conflict of interest arises (like in this circumstance) a court would look at whether the transaction was fair to the company and shareholders to determine if there has been a breach of fiduciary duties. Generally, a board needs to make sure that the deal was both procedurally fair (voted on and approved by disinterested board members, special committees, etc...) and substantively fair (fair dealing, fair price). There is a ton of case law that fills in all the cracks as to what procedurally fair and substantively fair actually mean but that's a high level overview.
Oh they very much do. Legislative intent is a major factor that many judges consider when enforcing legislation. Intent often has a very big impact on consequence.
Whether the purpose of legislation matters very much depends on a judge's beliefs regarding statutory interpretation. Enforcement of a statute is often all about the purpose of it. That said, I see your point and its a valid one. I'm just not sure I believe getting rid of 1201 will do less harm than good. I guess we'll see how the lawsuit turns out!
I studied section 1201 thoroughly during law school and I think this post doesn't give a fair characterization of it. The reason this statute exists is because companies were unable to devise protection for copyrighted works that hackers were not able to immediately circumvent. As a result, the government stepped in and created 1201 to make it illegal for someone to circumvent some form of access control that a company used to protect their copyrighted works. The purpose of the statute isn't to destroy <insert Internet activist claimed right> but is to make it much less expensive for a company to protect its products. I don't see anything wrong with that.
Most of the time it happens on Twitter. Someone will tweet a bitly link with some enticing headline but I refuse to click it because I don't know where the link is taking me. Perhaps I'm just overly cautious...
I think Meteor 1.3 + React is a really promising stack. If you are overwhelmed by all that comes with the default React stack (Webpack, Redux, React Router, etc...) then give Meteor 1.3 + React a try. It eliminates the need to write your own build system, makes writing a full stack JS app stupid simple, and overall makes you a lot happier.