<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Muhammet Şafak — Tooling comparison research</title><description>The measurable difference between two tools doing the same job: build time, output size, memory and the developer loop.</description><link>https://www.muhammetsafak.com.tr/</link><language>en-US</language><lastBuildDate>Thu, 20 Aug 2026 00:00:00 GMT</lastBuildDate><managingEditor>info@muhammetsafak.com.tr (Muhammet Şafak)</managingEditor><atom:link href="https://www.muhammetsafak.com.tr/en/research/program/arac-karsilastirma/rss.xml" rel="self" type="application/rss+xml"/><item><title>The fixed cost of installing a PHP framework: disk size tells you nothing</title><link>https://www.muhammetsafak.com.tr/en/research/php-framework-footprint/</link><guid isPermaLink="true">https://www.muhammetsafak.com.tr/en/research/php-framework-footprint/</guid><description>Disk size predicts nothing: Yii2 has the largest vendor tree at 34.1 MB and loads only 62 files per request, among the fewest in the field. Files per request predicts nothing either: CodeIgniter loads 96 files and serves 6,431 req/s, Symfony loads 224 and serves 13,067. The one number that genuinely separates them is the first request served with a cold opcache: 2.2 ms for Phalcon, 72.2 ms for Laravel — thirty-three times. That is the compile bill the first visitor pays after every deploy, and it is measured in tens of milliseconds, not kilobytes.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><category>arac-karsilastirma</category><category>php</category><category>framework</category><category>opcache</category><category>composer</category><category>dependencies</category></item></channel></rss>