Well that is rather obvious. I doubt PHP has RTOS type guarantees built in.
Funny you should mention stabilizer control (I don't think that is an aeronautic term). I recently visited the Battle of Britain Memorial Flight hanger at RAF Conningsby. It turns out that the Hurricane and Spitfire had unusual (by today's standards but normal for the times) ways of applying trim to control surfaces.
One of them - you glue a piece of string on top of an aileron and on the other you smack it with a hammer to bend it (that must be the Spitfire) and then you test it out and keep fettling until the job is done.
Well, that's roll sorted out, I'm not sure what trim for the other two axes (pitch, yaw) involves. Probably knicker elastic.
> Well that is rather obvious. I doubt PHP has RTOS type guarantees built in.
It's not multithreaded by default (as long as you're not running it in an environment like Apache), no async stuff going on, so the major roadblocks for real-time guarantees are already out of the picture.
The things I would be worried about is garbage collection and array handling. The former should be able to be configured (or in the worst case, rewritten) in a way that provides upper bounds on performance, people have already managed to do that for Java, the latter should be manageable by enforcing boundaries in the user code (e.g. disallow stuff like $foo[]='bar' that dynamically extends the length of an array).
We didn't have time to polish ours like that what with the enemy shooting at them all the time. Oh and most of them were made of wood and wishes! The Hurricane was a bit of a crossover from WWI to WW2, yet rather a lot of Brits and Poles (int al) flew them against the Luftwaffe, who had rather more modern ME109s etc. It must have been a bit of a pain to see your enemy deploy a cannon when you only have a .303.
There is absolutely no doubt that if the US hadn't rocked up, we would have been ... well I'm not sure what Europe might mean nowadays if things had been different.
Possibly, our most lethal aircraft was the Mosquito. It was made of wood and twin enginned. So it was light and very, very fast and could pack a real punch - a quad cannon or lots of machine guns in the nose and carry bombs too. Parts were made in furniture factories and garden sheds - it was totally mad and rather hard to target manufacturing.
I think that the Nazi regime gave two kills for downing a Mosquito because it was considered a bit of a handful.
it'll be alright as long as you're not receiving the trim updates as part of a search query using parse_str, otherwise, you might be susceptible to script kiddies.
It seems like the only clauses being removed are those that protect PHP and Zend trademarks. Other than that, it's just unifying the two projects under a single license.
--
Basically, these two clauses (first from PHP, second from Zend) are removed:
The name “PHP” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact group@php.net.
The names “Zend” and “Zend Engine” must not be used to endorse or promote products derived from this software without prior permission from Zend Technologies Ltd. For written permission, please contact license@zend.com.
And replaced with:
Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
--
Then the following three terms (4-6) are removed from PHP:
4. Products derived from this software may not be called “PHP”, nor may “PHP” appear in their name, without prior written permission from group@php.net. You may indicate that your software works in conjunction with PHP by saying “Foo for PHP” instead of calling it “PHP Foo” or “phpfoo”
5. The PHP Group may publish revised and/or new versions of the license from time to time. Each version will be given a distinguishing version number. Once covered code has been published under a particular version of the license, you may always continue to use it under the terms of that version. You may also choose to use such covered code under the terms of any subsequent version of the license published by the PHP Group. No one other than the PHP Group has the right to modify the terms applicable to covered code created under this License.
6. Redistributions of any form whatsoever must retain the following acknowledgment: “This product includes PHP software, freely available from http://www.php.net/software/”.
--
And the following three terms (4-6) are removed from Zend:
4. Zend Technologies Ltd. may publish revised and/or new versions of the license from time to time. Each version will be given a distinguishing version number. Once covered code has been published under a particular version of the license, you may always continue to use it under the terms of that version. You may also choose to use such covered code under the terms of any subsequent version of the license published by Zend Technologies Ltd. No one other than Zend Technologies Ltd. has the right to modify the terms applicable to covered code created under this License.
5. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes the Zend Engine, freely available at http://www.zend.com"
6. All advertising materials mentioning features or use of this software must display the following acknowledgment: "The Zend Engine is freely available at http://www.zend.com"
This is exactly the reason that "Windows Subsystem for Linux" never made sense: the correct preposition would've been "including". Other suggestions: the verb phrase "consisting of"; the adverb "to wit" ("Windows Subsystem, to wit: Linux" has a nice ring to it); whatever part of speech "which is" is.
NB: This was added "later" that is why tons of projects were grandfathered in, because they were already called phpMyAdmin, phpMyFAQ, etc. (IIRC at least)
It's sold to us as non-news, which is good. No change for contributors, no change for end users, rights wise.