PHP Needs

Latest

Popular

• ∆206 Chuck Norris
• ∆103 A full embrace of OO for core functions, strings especially - would help reduce the 'inconsistent parameters!' complaints
• ∆78 Chaining class constructors with methods new Foo()->bar()->tar() and array access to methods that return collections $this->foo()[1]
• ∆71 A core object that represents the HTTP Request and Response
• ∆65 Short syntax for arrays ($arr = [];) https://wiki.php.net/rfc/shortsyntaxforarrays
• ∆61 to get on the GitHub train
• ∆53 Use only Exceptions in built-in functions instead of the current mix of Errors & Exceptions
• ∆50 Proper Unicode support.
• ∆49 What PHP really needs is: Strong leadership and an official process to submit new ideas, extensions ...
• ∆40 standard naming conventions
• ∆36 Consistency in function parameter ordering. (No more docs hunt for $needle in a $haystack)
• ∆25 Put PHP 5.x into maintenance mode and focus on building a solid php 6. The issues with PHP are widely known and generally not fixable without huge changes to the language. Two-pass compiler with strict syntax checks, dramatically reduce core function base and move non essentials to external modules/namespaces, get rid of shared-nothing architecture, variable scoping (file, class, blocks), get rid of "\" namespace separator, fix type juggling/comparison operators so they do not have unintended side-effects, get rid of php.in (replace them with pragmas in code to localize them to previously mentioned scopes), script run mode (treat file as program not template), get rid of path to include files (Foo::Bar::Baz should know how to find it based on the architecture its running on),
• ∆24 A willingness to break backwards compatibility in the next major release in order to bring about some level of consistency to the language. This also means improving documentation (there's no good reason why different major versions of PHP should share the same documentation).
• ∆22 native package support ala perl, python, ruby: instead of extensions loading at php start, load on demand, allow pure PHP 'extensions'
• ∆21 A String class that can be called staticly or as an object. This would replace the str_* functions while standardizing $needle, $haystack
• ∆19 array literals
• ∆17 New blood, and less old blood.
• ∆17 an option to always throw exceptions instead of trigger errors.
• ∆17 to exile poisonous people, no matter how large their perceived historical contribution
• ∆16 A plan for the future of web development
• ∆15 Threading.
• ∆14 Type Hinting for int, string, double, etc...
• ∆12 Leaner core, with far fewer global functions. Move them to add-on modules.
• ∆12 To die.
• ∆11 less focus on voting, and more focus on real consensus
• ∆11 Allowing objects that implement the array interfaces to be usable by the array manipulation functions.
• ∆11 doers, not voters
• ∆9 PHP needs to leverage more of its own language features (e.g. Namespaces) in the API of its standard library and extensions
• ∆9 object literals for php !!!
• ∆9 A an official, centralized PEAR repository that is open to *anyone* to improve collaboration for common libs (see Pearfarm)
• ∆7 a large cowbell
• ∆7 To focus on community solutions that don't require PHP Internals
• ∆7 Interoperable components – not more frameworks.
• ∆7 #phpneeds to provide real documentation for the SPL classes and other PHP 5.x classes that have no examples, etc.
• ∆7 to not throw a warning on functions that will return false on failure
• ∆6 LLVM front-end.
• ∆5 you.
• ∆5 Ability to determine file loaded percentage
• ∆5 List comprehensions
• ∆5 an interactive command-line interpreter for toying with libraries and new ideas
• ∆5 Better internals documentation in the manual to lower the barrier to entry for prospective contributors.
• ∆5 Readonly properties
• ∆4 Magical methods to implement two more called __before () and __after (), run at the beginning and end a method, but does not not work as and __destruct and __construct (). Based in Kohana Framework Controller Class http://kohanaframework.org/3.0/guide/api/Controller //See Before and after methods
• ∆4 Standard function names.
• ∆4 to loose the semi-colons
• ∆4 More people with people skills
• ∆4 Stop having these public discussions about the future of the language and show us the roadmap to bring PHP up-to-date with other available tools. These public discussions never go anywhere and its getting frustrating.
• ∆3 more community support
• ∆3 less junk in it's trunk.
• ∆3 A focus on simplicity
• ∆3 Test
• ∆3 an enema
• ∆3 it needs $str = qq(interpolated string) and $str=q(plain string) tags like Perl. No more "$he said
• ∆3 a crackdown on the negative attitudes on internals
• ∆3 more contributors to unmaintained extensions
• ∆3 Have a solid development vision, and stick to it.
• ∆3 fewer people trying to make PHP into their own pet non-PHP langauge
• ∆3 More documentation contributors to get the documentation up to date.
• ∆2 A proper hex2bin() function.
• ∆2 solid cross-platform (Windows) parallel processing in Scripts
• ∆2 to get ride of the $ variable syntax
• ∆2 Session handling (locking/race condition) optimized for asynchr. requests
• ∆2 An actually useful, reliable software library repository you can use on any shared host.
• ∆2 A good unit testing library for test driven development!
• ∆1 A closer community
• ∆1 Generate 2D Code like PDF-417, DataMatrix, etc to Image
• ∆1 A spec so other implementations can test compatibility.
• ∆1 coalesce function
• ∆1 interface with optional and required methods
• ∆1 DateTime::__toString() - with a DateTime::setDefaultFormat()
• ∆ ability to write conditionals at the end of a statement e.g. print "I am the walrus - goo goo ca choo" if ( $name == "john lennon");
• ∆ Python like % operator
• ∆ concurrency

Tweets