I have forgotten one major difference from the user's perspective.
-- If you decide to go with HHVM and start using the additional strong typing then you won't be able to go back to PHP (at least at the moment, shouldn't be too hard to generate PHP code instead of Bytecode though - but this feature does not exist yet).
In contrast, code in TSPHP is always translated to PHP. Thus you can always go back to PHP if you don't like TSPHP any more and you are also able to reuse your TSPHP components in a purely PHP project. IMO that's a nice feature.
As far as I see most bigger frameworks write PHP in a type-safe manner anyway thus I could imagine that (some) frameworks are written in TSPHP in the future and "normal" users are still using it in PHP.
You received this message because you are subscribed to the Google
Group: "Washington, DC PHP Developers Group" - http://www.dcphp.net
To post, send email to washington-dcphp-group@googlegroups.com
To unsubscribe, send email to washington-dcphp-group+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/washington-dcphp-group?hl=en
---
You received this message because you are subscribed to the Google Groups "Washington, DC PHP Developers Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to washington-dcphp-group+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
0 comments:
Post a Comment