user-documentation
Package
Our great sponsors
| user-documentation | Package | |
|---|---|---|
| 3 | 4 | |
| 129 | 0 | |
| 1.6% | - | |
| 7.4 | 0.0 | |
| 22 days ago | over 2 years ago | |
| Hack | ||
| GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
user-documentation
-
RFC: Sealed classes
I think there are thousands of other things to apply to PHP, rather than this, but if that's the way to go, well, the worse is nothing. Also just look at what https://docs.hhvm.com/ has and PHP doesn't, or go through LOLPHP.
-
Ask HN: State of PHP at Facebook
> Are there any large Hack codebases I can explore?
depends what you mean by 'large' - perhaps https://github.com/hhvm/user-documentation ?
> Does anyone know if FB tracks changes to PHP so Hack is "up to date"?
No, for the most part, Hack no longer considers PHP 'upstream'. Exceptions are things like security fixes to extension functions, if that particular extension function was derived from PHP.
-
PHP in 2021
> With Hack's extensive static type checking and even contexts / coeffects
Have you used contexts/coeffects?
My understanding is that it's still yet to be fully rolled out to WWW, and nobody outside FB has yet played around with it. IMO it still has some DX issues (https://github.com/facebook/hhvm/issues/8828) and the examples given in documentation don't actually work in real life (https://github.com/hhvm/user-documentation/issues/1016).
Package
-
RFC: Sealed classes
Kotlin: https://kotlinlang.org/docs/sealed-classes.html#location-of-direct-subclasses ( instead of using permits, all class within the same package are permitted, this won't work in PHP since we don't have pacakges, but if in the future we get packages, we can make it so that classes with no permit clauses are permitted to the same package - see https://github.com/Danack/Package/blob/master/rfc_words.md )
-
Modules and why Namespaces are not them
Yeah....I keep coming back to a lack of modules/packages separate from namespace as being one of the things that PHP is lacking as there are a few different problems that would be possible (though not easy) to solve with them. Have some very rough words: https://github.com/Danack/Package/blob/master/rfc_words.md
-
Interview with Zeev Suraski, cofounder of PHP: Perspectives on PHP, the release of PHP 8, and what it means for WordPress
It would be really good to make the 'prize' not being a thing to be fought for. Some sort of package system might be part of that.
What are some alternatives?
HHVM - A virtual machine for executing programs written in Hack.
PHP OAuth 2.0 Server - A spec compliant, secure by default PHP OAuth 2.0 Server
discourse_docker - A Docker image for Discourse
z-engine - :zap: PHP Engine Direct API
http-message - The purpose of this PSR is to provide a set of common interfaces for HTTP messages as described in RFC 7230 and RFC 7231
Boston-PHP-Meetup-Examples - Boston PHP Meetup examples
ex_twilio - Twilio API client for Elixir
bref - Serverless PHP on AWS Lambda
ent - An entity framework for Go