Hi! > This makes an opportunity to replace the old API with object oriented one > preventing any kind of BC break. > > But instead of using this as an extension because of some limitations like > “string”->startsWith(‘s’); the API should be bundled with the engine (not > written in PHP).
This is the problem with all these proposals. Instead of taking the gradual road of making a beautiful API in extension, having it accepted (I'm taking the optimistic scenario), popular and then merged into the engine, it's always "let's redo the whole engine from scratch". That's why these things haven't gone beyond talk for years. > This will make the opportunity to also remove any inconsistencies in the > API behavior as well. You write "remove inconsistencies", I read "break all existing code". > I’ve seen many articles encouraging new comers to learn languages like > Python or Ruby, and highly discourage them from using PHP. Also many new > projects are using languages different than PHP. (don’t tell me you haven’t > seen this) I've seen a lot of silly stuff on the Internet, so what? It's a free medium, anyone can write anything. That doesn't mean it carries any weight by the fact of writing. > The old API should be deprecated in PHP 8.0 and removed completely in PHP > 9.0 (finally) Which means no code written in PHP would work in PHP 9.0. Why then call it PHP? Call it something else. BTW, if you look at Java, some methods deprecated in Java 2 are still around in Java 8. Java didn't die from it. Why people are so zealous to break things that work? -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
