"Open-Source, not Open-Contribution: SQLite is open-source, meaning that you can make as many copies of it as you want and do whatever you want with those copies, without limitation. But SQLite is not open-contribution. The project does not accept patches. Only 27 individuals have ever contributed any code to SQLite, and of those only 16 still have traces in the latest release. Only 3 developers have contributed non-comment changes within the previous five years and 96.4% of the latest release code was written by just two people. (The statistics in this paragraph were gathered on 2018-02-05.)"
Hey I'm not a security engineer but it occurred to me that when using an unsecured public WIFI network the real concern is in doing the initial TLS handshake over that network. My question is - If I switch my laptop to use a tethered network via my cellphone prior to hitting an HTTPS website and then switch it back to using the public WIFI after the connection has been established would I be...
For example if you are using Ember you gain the advantage of a client-side ORM called Ember Data which handles caching and cache invalidation for your API data. Did you handle that in your non-framework application? If you did, how long did it take you to implement? How well tested is it? How many developers besides yourself have reviewed it? How much documentation did you write and how long does it take to bring new developers up to speed on it? If it breaks, who will fix it?
Multiply that by ten or twenty depending on the framework and you start to see what the benefits are.
Which certainly does allow for a conflict free story. The important thing is that a story has events which are causally related. Otherwise it really is just a list of unconnected statements.
Also, Inform is a fascinating "English language" programming experience! For example here's an actual Inform program:
` "Prototype" by Josh
The Lookout Point is a room. An old man is here.
The Outskirts is south from the Lookout Point. A campaign poster is here.
The Village is east from the Outskirts.
The Scumm Bar is inside from The Village. `
"To load a program named AGATHA, use the command LOAD AGATHA and the program of that name, if there is one in the catalog, will be loaded. To test if AGATHA is loaded, see if it can walk along a straight line."
If Facebook had not included this Patent grant and had released React under only the BSD license then any user would be in the exact situation which everyone is complaining so loudly about being in IF they decide to bring a patent action against Facebook. Specifically, you would be open to being sued by Facebook for violating a patent which they own.
What this grant says is for one specific circumstance (you haven't brought a patent suit against them) and for one specific limited set of patents (those related to React), Facebook will not sue you. If you like that protection then don't sue them. If you decide that you do want to bring a patent suit against them then you're right back where you were to begin with. Your one small limited protection is removed and Facebook can once again sue you if you violate one of their patents - just like they could before you started using React in the first place.
This business about it being asymmetrical is IMO a distraction. What would it mean for it to be symmetrical? That it would only trigger if you sue them for a patent violation related to React? What does that mean? You don't hold React patents, Facebook does. How would you sue them for a violation of a React patent? It makes no sense.