Interesting and possibly relevant to note that SQLite is not your typical opensource project:
"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.)"
The fact that it doesn't can be exploited by running it in a virtual machine and using the snapshot feature to go back in time. That's how we made this Website is Down video: https://www.youtube.com/watch?v=1SNxaJlicEU
Will this technology be licensed for redistribution or only for online API use? I ask because in the video game scenario it would be great to have this in a library I could distribute instead of relying on the API to be available at all times.
Interesting... so there no security concern with using HTTPS on a public Wifi? I thought there was some way the connection could be hijacked. Thanks for the response.
I am surprised at the number of people who think they can do everything without a framework and that everything would just be better if they weren't weighed down by the horrible affliction of using one. Frameworks provide real value and while not required for many small applications they can be a huge advantage in large enterprise applications.
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.
I always liked Brian Moriarty's definition of story: "a particular causally related sequence of events".
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.
This reminds me of some words of advice I noticed in an even older manual for the Apple II floppy disk drive:
"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."
My feeling is that as an adult I have the ability to "think creatively" when I want to. I don't feel like a study of this nature really takes that into account. I'd be curious what would happen if they added a segment of the test where they ask the subjects to intentionally come up with a creative response.
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.
"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.)"
https://www.sqlite.org/copyright.html