Software is slow because of bad design, not slow languages
Web page · https://seangoedecke.com/software-is-slow-because-of-bad-design-not-slow-languages
First seen by Oriel on .
AI summary
The article argues that software performance usually depends more on I/O and program design than implementation language, so profiling and redesign often outperform wholesale rewrites in C or Rust.
- Database queries, network calls, and disk access commonly dominate request time, limiting the gains from faster language execution.
- Higher-level languages often delegate expensive work to optimized native libraries, as Python does for machine learning and mathematics.
- The author lists caching, asynchronous work, parallelism, reducing SQL queries, and skipping unnecessary operations as effective redesigns.
- Rewriting can help rare CPU-bound hotspots, but the article recommends profiling first and notes that its claims about CRUD workloads reflect the author's experience.
- The author acknowledges exceptions, including CPU-intensive tools such as browser layout engines, 3D renderers, word processors, and neural networks.
#software performance #programming languages #profiling #system design
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 54, latest observation ; +53 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 78, latest observation ; +78 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | hd72yt | https://www.seangoedecke.com/software-is-slow-because-of-bad-design-not-slow-languages/ Read discussion |