What are the tradeoffs (e.g. development speed, performance, scalability) between using various php frameworks, ruby/rails, or python/django? Is there any reason to choose one overwhelmingly over another?
27th November 2010
At this point, I’d argue that the decision between them comes down to programming language rather than framework—the frameworks have mostly converged on a very similar set of features.
All three solutions scale in exactly the same way (shared nothing architecture).
If you’re writing something for people to deploy on their own hosting plans, PHP is far more widely supported. For a service that you host yourself, you need to decide which language ecosystem is the best fit for how you like to develop.
Update 14 months later: I’d argue today that thanks to hosting platforms such as ep.io, Heroku and dotCloud PHP’s hosting advantage isn’t nearly as pronounced.
More recent articles
- Weeknotes: Llama 3, AI for Data Journalism, llm-evals and datasette-secrets - 23rd April 2024
- Options for accessing Llama 3 from the terminal using LLM - 22nd April 2024
- AI for Data Journalism: demonstrating what we can do with this stuff right now - 17th April 2024
- Three major LLM releases in 24 hours (plus weeknotes) - 10th April 2024
- Building files-to-prompt entirely using Claude 3 Opus - 8th April 2024
- Running OCR against PDFs and images directly in your browser - 30th March 2024
- llm cmd undo last git commit - a new plugin for LLM - 26th March 2024
- Building and testing C extensions for SQLite with ChatGPT Code Interpreter - 23rd March 2024
- Claude and ChatGPT for ad-hoc sidequests - 22nd March 2024
- Weeknotes: the aftermath of NICAR - 16th March 2024