4 ms·
Nobody can blame the guy for the design choices and naming conventions he made back then. The problem is that they still exist 20 years later when much of the w
by laumars 13y ago
Nobody can blame the guy for the design choices and naming conventions he made back then. The problem is that they still exist 20 years later when much of the worlds web infrastructure runs on PHP.
I'd have expected (hoped) that by the time of the last major release (v5.0) the chief PHP devs would have used that opportunity to to rename some of the core functions. By that point PHP's popularity was already established and the shortcomings of it known. Plus as there was already a major Zend rewrite under way, to me it seems a sensible time to throw in a few in a few niceties to beautify / simplify the APIs.
Perl -PHP's spiritual predecessor- managed to tidy itself up circa v5.8 and now, ironically, Perl is cleaner language to code in despite the jokes about it being executable line noise.
- choult 13y agoThe past five or so years have seen engineers of greater experience take interest in PHP's ecosystems and core; a greater maturity in PHP is emerging. I suspect we'll see bigger changes coming over the next five or ten years, but it takes time to tame chaos.
- dscrd 13y agoBut.. why? Why not just move to a language that is already clean and good?
- chaosphere2112 13y agohttp://en.wikipedia.org/wiki/Sunk_costs http://en.wikipedia.org/wiki/Sunk_costs
- darkf 13y agohttp://en.wikipedia.org/wiki/Sunk_costs#Loss_aversion_and_the_sunk_cost_fallacy http://en.wikipedia.org/wiki/Sunk_costs#Loss_aversion_and_th...
- chaosphere2112 13y agoI'm not defending the practice, I'm just saying it's the argument that gets used. "We're an oracle shop, we've spent $N Million on getting set up as an oracle shop, and we'll always be an oracle shop. Let's use ADF[1]." [1]:http://www.oracle.com/technetwork/developer-tools/adf/overview/index.html http://www.oracle.com/technetwork/developer-tools/adf/overvi...