Hacker News Reader

Comment by Wulfheart | Hacker News Reader

[dead]

Both of those are currently hobbyist projects. They may develop further and become useful to the average PHP dev, but they're definitely not there yet.

Yeah, Matt is absolutely right. I'm working on PXP as a passion project, something that I've been trying to do over the last year or so and only started to invest serious time into the last couple of months.

The goal isn't to completely replace PHP but to complement it. You can think of it like a playground for future PHP syntax. Something could be added to PXP and released in a week, PHP on the other hand has 1 big release a year. If something is successful and widely used in PXP, then it could be a contender for PHP core.

Not sure he 'forgot'. People dont tend to do that kind of thing in PHP as honestly it's totally unnecessary.

What's the point? You can use types in the vast majority of places in PHP and it works well, so I don't really see the point of that instead of contributing to the native typing system.

Javascript already set the precedent. If you don't like the way a language works, it's preferable to have a proxy language that does work the way you want that compiles to it, rather than accept the language for what it is and learn to work with it.

Javascript can't be compared with PHP, javascript is the only scripting language that all browsers understand except wasm. And there are multiple interpreters that may work different or have not all features avail.

PHP is used on servers that can run many different languages. Additional there is only one php interpreter that is widely used (yes there was hhvm and some others ), that means you can rely on all features of this version.

You missed my point: PHP is adding types to the core language, so instead of developing a superset, contribute to the type system of PHP.

The comparison just isn't relevant.

what do you suggest to achieve this? electron?

just a downvote then. helpful.

The only gripe I have with PHP is that the standard library while extensive is a total inconsistent mess. Would rather see that addressed first.

It's unlikely to happen. 10-20 years of use for many of those community generated functions is a lot to break. It may happen eventually, but I wouldn't count on it.

Reply on news.ycombinator.com