31–40 of 67 posts
Is there a good reason to still use php when you can use hacklang ( https://hacklang.org/ ) which has much stronger type system. Some would even call it php++.
(Sad because I use Hack in my day job and PHP for my open source projects, and find Hack way more pleasant and productive)
PHP rocks in 2020. Couple it with laravel or something and you get a solid platform to build a monolith-type web app with really fast performance.
It's gotten a lot better since I started using it ~2009 and now. 7.4 added typed properties. 8 is adding better caching, a jit and my favourite feature match() https://php.watch/versions/8.0#match-expression for all the enterprise heavy stuff I write a nicer cleaner and safer (by default) alternative to switch is going to make some code much cleaner to write and read and really that is what I care about more than alm…
Is there a good reason to still use php when you can use hacklang ( https://hacklang.org/ ) which has much stronger type system. Some would even call it php++.
If you’re building an app to run on other people’s servers, vanilla PHP is much more widely available :( (Sad because I use Hack in my day job and PHP for my open source projects, and find Hack way more pleasant and productive)
Main takeaway: strict types won't make your code faster! It may make it slightly slower
Earlier quoted context omitted.
Ruby is slower than PHP7+ by orders of magnitude. I doubt it.
Orders of magnitude? Do you thibk that PHP is at least x100 times faster than Ruby?
It actually makes me really happy to see more positive comments on a thread about PHP. It is an incredible workhorse, and doesn't get the credit it deserves. I'm often amused by developers that revile PHP, while going on to use another language, which suffers from a similar set of problems to PHP, oftentimes with poorer performance and more complex toolchains. PHP deserves a little more love, imo.
Earlier quoted context omitted.
Orders of magnitude? Do you thibk that PHP is at least x100 times faster than Ruby?
Alright, maybe an exaggeration. But the difference is huge. https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
Adding a static analyzer (like Psalm [1]) to the mixture makes PHP's types much more powerful. Psalm can use docblock annotations to attach more complex types to functions and variables, including: * A "list" type representing a non-associative array * Types representing specific kinds of values, like numeric-string or non-empty-array, as well as exact values as types (like true and false, or string constants). * Typ…
Psalm is nice, however I would suggest PHPStan as an alternative for people that encounter a lot of friction with Psalm. For example, in a project using doctrine I have to add a bunch of is null/@psal-mutation-free annotations. As all the methods can return null. However, if Psalm had support for something like phantom types, maybe I could tag entities returned from the database for whom certain fields are guaranteed…
Maybe the `@psalm-ignore-nullable-return` annotation is more appropriate for those methods?
Do you use the Doctrine plugin?
Earlier quoted context omitted.
The point of strict types is generally not speed, but rather, to make your code more correct.
Correct? I'd probably say predictable.