はてなブックマーク

Several weeks ago, a correspondent presented a legacy situation that I've never had to deal with. He was working his way through Modernizing Legacy Applications in PHP, and realized the codebase was storing serialized PHP objects in a database. He couldn't refactor the class names without seriously breaking the application. I was carefully moving my classes to a PSR-0/4 structure when I found this

Adherence to Semantic Versioning is just The Right Thing To Do, but it turns out you have to be extra-careful when modifying public interfaces to maintain backwards compatibility. This is obvious on reflection, but I never thought about it beforehand. Thanks to Hari KT for pointing it out. Why do you have to be extra-careful with interfaces and SemVer? To see it more clearly, let's use a concrete

In a tweetstorm that spun up late last week, Taylor Otwell produced the following commentary: look guys I’m “decoupled” because this package doesn’t have composer dependencies!!! HAHAHAHA LOL how many composer packages a given package has does NOT affect YOUR code’s decoupling. that is a matter of programming to an interface, etc. you people seriously do not understand decoupling. at all. if you t

After the previous round of benchmarking, I received one very good criticism from Matthew Weier O’Phinney about it. He suggested that the hardware I was using, a PowerPC G4 Mac Mini, had an I/O system that was not representative of what a "regular" user would have as a web server. I have to agree with that. As such, I have prepared a new set of benchmarks for Cake, Solar, Symfony, and Zend Framewo

UPDATE (2007-01-01): I have conducted a new series of benchmarks; see them here. The numeric results below should be considered as outdated, although the history, methodology, and approach are still valid. Wherein I relate the results of benchmark testing on three (plus one)four frameworks: Cake, Solar, Symfony, and Zend Framework(plus Cake). Anger-inducing broad-brush overview: Solar is 4x faster