6 ms·
This is fascinating. It's a well-written post and their plan makes sense to me, but I imagine there's a tough choice ahead for framework authors (the Laravels a
by rrdharan 9y ago
This is fascinating. It's a well-written post and their plan makes sense to me, but I imagine there's a tough choice ahead for framework authors (the Laravels and Drupals of the world) about whether they want to fork their communities, stay with PHP7, or try to target both with the same codebase (in the near term or long term)?
At any rate at least the fact that the HHVM folks are communicating the strategy effectively and transparently should help everyone involved make reasonable decisions.
- wolco 9y agoI can't imagine any large framework spliting or supporting this in place of php 7. This is more of a new beginning with new hack frameworks.
- HugoDaniel 9y agoThat and PATENTS: https://github.com/facebook/hhvm/blob/master/hphp/hack/PATENTS https://github.com/facebook/hhvm/blob/master/hphp/hack/PATEN...
- zimbatm 9y agoIf Facebook had released the code under BSD then nobody would have complained. But this basically gives a BSD plus patent grant, and reverts to BSD if there are any patent litigations. And now people are complaining.
- deleted 9y ago[deleted]
- s73ver_ 9y agoBecause it is them saying, "We can take all of your patents, but if you sue us for it, then you don't get to use this."
- jbergens 9y agoIANAL. I think that is a common misunderstanding of the clause. If you sue them for react patents you can still use HHVM, or vice versa. https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revokable-patent-license-why-its-a-paper-25c40c50b562 https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revok...
- abritinthebay 9y agoNot even close to true
- deleted 9y ago[deleted]
- cstrasen 9y agoWoah. Its bad enough with react which many did not expect. Now also this BS. No thanks really.
- dingdingdang 9y agoExactly like React - means the language will be abandoned by wider community. The Facebook peeps are gradually building themselves into corporate self-invented mono-culture.
- m00x 9y agoI'd like to see any concrete numbers on this. I'm seeing React getting stronger and stronger in my area, and patent worries are mostly accepted as crazy hypotheticals.
- georgebarnett 9y agoDo you work with any lawyers in your company or peer group? I doubt they view the patent issue as "crazy hypotheticals".
- abritinthebay 9y agoThe only lawyers I know with software patent experience consider the fuss absolutely rediculous. It gives you more rights. Full stop, end of story.
- dreamfactored 9y agoWordpress are just starting what could easily be a multi-year rewrite as a result and Drupal has specifically excluded React from evaluation - both on the basis of the patent issues
- true_religion 9y agoTrue, but PHP development has always been split from the rest of the web-dev community. React has managed to bring together people in C#, Python, Ruby, and Erlang to name a few languages... who all previously used different frameworks, or just jQuery.
- sneak 9y agoYes, it is clearly in wordpress' best interests to spend all that time and money to preserve their very important right to sue facebook for violating wordpress' software patents in the future. /sarcasm
- fredemmott 9y agoThanks; we don't feel that the framework authors have to make a choice here: - short-term, those of us working on HHVM - not the frameworks - need to make sure that HHVM can run the frameworks that Hack developers require - long-term, we expect Hack and HHVM to continue to diverge from PHP; it's unlikely that targeting both HHVM and PHP will be a practical long-term strategy
- chx 9y agoIf I still were a Drupal core developer (and I was the #1 core contributor for 5, 6 and #4 for 7 and still #10 for 8 though I regret that) I would tell you there's no tough choice here, I would target PHP 7.x and forget the rest. Currently, others steers the core and they struggle mightily with just the transition to PHP 7.0 requirement. Check the issue queue. I filed https://www.drupal.org/node/2605226 https://www.drupal.org/node/2605226 in 2015 fall but it was voted down, the current open issue is https://www.drupal.org/node/2842431 https://www.drupal.org/node/2842431 HHVM is way too niche to bother with it, sorry.
- TazeTSchnitzel 9y agoPHP packages are dropping HHVM support right and left right now because HHVM has already been… lagging in its PHP support. So there's not really a choice to make. HHVM was tiny anyway.
- dabernathy89 9y agoLaravel dropped HHVM support a year ago, and i'm sure many other CMS's / frameworks have either followed suit (if they ever supported it) or will soon.