Why I prefer LAMP / LLMP
2026-11-07 03:52:15 UTC
The strongest argument for the traditional LAMP stack is not nostalgia. It is simplicity, maturity, efficiency, portability, and the ability to maintain a production website without assembling an increasingly complicated collection of technologies.
Linux
Why Linux?
Because it's the only operating system that doesn't treat you like a clueless child or a walking wallet.
Here's the no-BS breakdown:
The Honest Reasons I (and most serious developers) use Linux
1. You Actually Own Your Machine
- Windows: "Hey, can I reboot for 47 updates? No? Too bad, I'm doing it anyway."
- macOS: "Sorry, you can't install that. Apple knows best."
- Linux: "Do whatever the hell you want. It's your computer."
2. It's Built for People Who Actually Understand Computers
Linux respects your intelligence. The entire system is inspectable. Want to know exactly what a program is doing? strace, lsof, netstat, ss, systemd-analyze — the tools are insanely good.
3. The Server Reality (This is the real reason)
- ~80-90% of the internet runs on Linux.
- Every serious company (Google, Amazon, Meta, Netflix, etc.) runs Linux in production.
- If you're a developer and you don't understand Linux, you're basically cosplaying.
4. Performance & Efficiency
Linux is lean as hell. My servers typically run with:
- 300-800MB RAM idle
- Near-zero bloat
- Updates that don't require a reboot (usually)
Windows Server? lol.
5. The "Actually Good" Software
- Package managers that don't suck (
apt,dnf,pacman) zsh+tmux+neovim+gitworkflow that makes you terrifyingly productive- Tools that were designed by engineers, not marketing departments
My Personal Ranking (No Corporate Agenda)
| Use Case | Best Choice | Why |
|---|---|---|
| Server/Hosting | Linux | Not even a contest |
| Development | Linux | Best tools, best workflow |
| Desktop (daily) | Linux | Once you get past the first month |
| Gaming | Windows | (for now) |
| Corporate Laptop | macOS | Least hassle for normies |
| Grandma's computer | Windows or ChromeOS | Don't torture her |
The Peter Martin Special Reason
As someone who runs a web hosting company (ABOL), Linux isn't a preference — it's a survival requirement. Every time a client comes to me with a bloated Windows server or some janky macOS setup, I migrate them to Linux and their hosting costs usually drop by 60-80% while performance doubles.
Bottom line: If you're just browsing Facebook, use whatever.
If you're a developer, sysadmin, or someone who wants to actually understand computers...
Use Linux. Full stop.
The learning curve is real, but once you're over it, going back feels like putting training wheels back on your bike.
Apache / LiteSpeed
Why I choose Apache or LiteSpeed
Here's the honest, no-BS breakdown from someone who's been running production servers for decades:
My Core Philosophy
"Fast enough + stupidly reliable + easy to maintain long-term beats theoretically faster but fragile every single time."
Apache + LiteSpeed – Why This Combo Wins for Me
1. Apache (httpd) – The Old Reliable
- .htaccess support is a killer feature for me.
- Clients can tweak rewrite rules, security headers, caching, etc. without needing me.
- This dramatically reduces support tickets.
- Extremely mature and battle-tested (literally decades).
- Excellent logging and debugging tools.
- Modules like
mod_security,mod_evasive,mod_expires, etc. are rock solid. - Works beautifully with DirectAdmin and cPanel (which most of my clients use).
2. LiteSpeed – The Performance Beast
- Drop-in replacement for Apache (same config files, same
.htaccess). - Usually 3-5x faster than Apache + PHP-FPM on real WordPress sites.
- Built-in LS Cache (often better than Redis for WordPress).
- Native HTTP/3 (QUIC) support.
- Excellent anti-DDoS features.
- Uses way less RAM than Nginx + PHP-FPM in many real-world scenarios.
The Honest Comparison (My Experience)
| Factor | Apache + mod_php | Nginx + PHP-FPM | LiteSpeed | Winner for Me |
|---|---|---|---|---|
| Ease of maintenance | Excellent | Painful | Excellent | LiteSpeed |
| .htaccess support | Yes | No (painful) | Yes (native) | LiteSpeed/Apache |
| WordPress performance | Good | Good | Outstanding | LiteSpeed |
| Memory usage | Higher | Medium | Surprisingly low | LiteSpeed |
| Debugging difficulty | Easy | Hard | Easy | LiteSpeed |
| Security hardening | Very good | Good | Excellent | LiteSpeed |
| Client self-management | High | Very Low | High | LiteSpeed |
When I Choose What:
- Most new projects → LiteSpeed Enterprise (if client can afford it) or OpenLiteSpeed
- Budget/shared hosting → LiteSpeed + LS Cache
- Legacy clients who refuse to change → Plain Apache + mod_php or Apache + PHP-FPM
- Only time I use Nginx → Very specific high-concurrency API-only projects (rare)
Bottom line: I don't chase "theoretically fastest" benchmarks. I chase fast enough + maintainable + secure + makes my clients happy.
LiteSpeed gives me 80-90% of the theoretical maximum performance while keeping all the things I love about Apache.
It's the ultimate "I want performance but I don't want to suffer" solution.
MySQL / MariaDB
Why MySQL / MariaDB?
Because after 25+ years of building websites, MySQL/MariaDB is still the sweet spot for 90% of real-world web applications.
The Honest Breakdown
Why I (and most of the internet) still choose it:
-
It's stupidly fast for what most websites actually do
Reads, simple joins, and transactional writes — exactly what 95% of web apps need. I can make a properly indexed MariaDB query scream on cheap hosting.
-
Rock-solid hosting ecosystem
Every single host on the planet knows how to run it. You can move a MySQL-based site from $5/mo shared hosting to a $5000/mo dedicated server without changing a single line of SQL in most cases.
-
MariaDB is the grown-up, free version now
Oracle bought MySQL and started acting like Oracle. The MariaDB fork (led by the original MySQL creator) has become the default choice for anyone who cares about freedom and performance. I almost exclusively use MariaDB 10.11/11.x now.
-
Battle-tested beyond belief
It's been running Facebook, Wikipedia, WordPress.com, and millions of other sites for decades. The bugs have been found.
When I don't choose it (being maximally truthful)
I reach for PostgreSQL when I need:
- Complex geospatial queries
- Very strict ACID compliance with complicated transactions
- Advanced JSON handling at massive scale
I reach for something else entirely (Redis, ClickHouse, etc.) when we're talking about caching, analytics, or time-series.
But for normal websites, CRMs, e-commerce, membership sites, SaaS dashboards? MySQL/MariaDB wins every time.
My Practical Stack in 2026
-- What I actually run
MariaDB 11.4
InnoDB (always)
UTF8MB4
Proper indexing strategy
Query cache? Hell no (turned off years ago)
The Real Reason I Love It
It's boring.
Boring technology is the best technology. I want my database to be like a refrigerator — I don't want to think about it. I open the door, the food is cold, and it just works for the next 10 years.
My rule of thumb:
- If your site gets fewer than ~50k visitors/day and isn't doing weird machine learning stuff → Use MariaDB
- If you're Instagram → call the PostgreSQL or Cassandra team
Want me to show you the exact MariaDB configuration tweaks I use on production servers that make most WordPress sites load 3-5x faster? Just say the word.
(And yes, I'm slightly paranoid about it — which is why my databases don't get hacked.)
PHP
Why PHP?
Let me give you the unfiltered truth:
The Honest Pros (Why I still bet my career on it)
- It's everywhere — Literally runs ~75% of the web. Your hosting is almost certainly already optimized for it.
- Insanely cheap to run — A solid LAMP server still costs peanuts compared to Node.js, Python, or Java equivalents at scale.
- Ridiculously fast development — You can go from zero to working prototype stupidly quickly. No compilation, no complex build steps.
- PHP 8.1+ is actually excellent — Proper types, attributes, enums, match expressions, fibers... it's a legitimately good language now.
- WordPress — Love it or hate it, it powers 43% of the internet. Knowing PHP deeply means you can tame the beast instead of fighting it.
- Maintenance reality — Most clients want something that a normal developer can pick up in 6 months when I'm gone. PHP wins here.
The Brutal Cons (I'm not delusional)
- Historical baggage (the "PHP is bad" memes are based on PHP 4/5 code)
- Inconsistent standard library (some functions are snake_case, some camelCase — it's chaos)
- Extremely easy to write terrible code (which most people do)
- The ecosystem has some... interesting characters
My Actual Philosophy
I don't use PHP because I think it's the best language.
I use it because it's the best tool for the job when the job is:
- Building websites that need to stay online for 10+ years
- Keeping hosting bills under $20/month
- Making something a normal human can maintain after I'm done
Modern PHP (8.x a/o November 2026) with strict types, proper OOP, and good architecture is genuinely enjoyable. The language got better. Most developers just never updated their opinion from 2008.
Bottom line:
PHP is like that reliable, slightly weird uncle who shows up with a toolbox and actually fixes your sink instead of explaining why you need a $400 smart-sink.