3 ms·
Those are upsides. For a dynamic language, i'd want: * A REPL * A language-browsable std lib or trivial reflection * A consistent API where expectations are
by mjburgess 7y ago
Those are upsides.
For a dynamic language, i'd want:
* A REPL
* A language-browsable std lib or trivial reflection
* A consistent API where expectations are reusable
* eg., polymorphic operators "do the right thing"
* Optional typing
* Typing, when present, facilitates polymorphism
* Data processing handed off to fast VM plugins
* Target of major trans-lang libraries (eg., Spark, et al.)
* Good long-running performance
* Community preference for minimalism and clarity
* Easy package management
* Modern functional primitives (eg., comprehensions)
* Modern OO primitives (eg., extension methods)
* Modern metaprogramming primitivates (eg., reified classes)
And probably others. Each poorly provided feels like taking a big step back; and just an injury to my productivity.
I'm not sure I'd get over how manically procedural PHP is; how sequential by nature. Every OO or functional addition runs against its grain and feels random and accidental.
- no_wizard 7y agoI think one of the things holding back 'modern' php is the lack of adopting a proper construct for dealing with threads/async operations. Whether its going to be promises/futures, async await operators or what have you, The inability to easily write async PHP hamstrungs it alot. Its 2019, and I still can't daemonize a PHP process without it leaking memory all over the place.
- nickthemagicman 7y agoPHP 7+ has most or all of these.
- slim 7y agoit has a (useless) repl