> On 3 Nov 2014, at 19:48, Stas Malyshev <smalys...@sugarcrm.com> wrote: > > Hi! > >> This is an unfair comparison. Hack is a compatible superset of PHP, >> much like TypeScript is a compatible superset of JavaScript. > > So? PHP once borrowed Perl syntax, and Java syntax, and so on. Hack > borrowed PHP syntax, and that's great. But that doesn't mean what they > do in their own language should constraint what we do in PHP.
Again, an unfair comparison. Hack isn’t intended to be a completely separate language. It’s supposed to be an augmented PHP, which is compatible with PHP. PHP code can use Hack code (in HHVM, anyway) and Hack code can use PHP code. Hack is a superset of PHP. There are transitional modes, too. > >> I’d rather there be less divergence between Hack and PHP, to limit >> the damage that it causes to the community. > > I don't see any damage to the community. How PHP not matching other > language's syntax does any damage to the community? What kind of damage > and where this damage comes from? Are we damaged because PHP arrays and > Perl arrays have different syntax, despite obvious Perl roots in PHP? The damage is in fragmentation. Hack threatens to fragment the PHP community by making people jump ship to use its added features. While the whole Hack community can use PHP libraries, only some of the PHP community (HHVM users) can use Hack code. The consequences of this could be severe. I’d rather there are less differences between PHP and Hack so there are less reasons to switch. Though I suppose the specific syntax of types is probably not a major issue. -- Andrea Faulds http://ajf.me/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
