3 ms·
No one in 2025 should be allowed to criticize early 2000s web practices as we have come full circle in many ways. They were limited by tools and resources. Now
by schmuckonwheels 11mo ago
No one in 2025 should be allowed to criticize early 2000s web practices as we have come full circle in many ways.
They were limited by tools and resources. Now you'll just see some async "API endpoint error -32768 timeout" and 8,000 spinning pinwheels on the page instead of it simply hanging. Because now you need to allocate 650MB RAM so you can output Hello World in some buggy "stack" with "memory safety".
The smart ones were using Java 25 years ago and what needed some 80lb Solaris box could run off a mobile phone now.
- andrewmcwatters 11mo agoOne of the most popular API frameworks is called “FastAPI” but in any meaningful benchmark it’s one of the slowest commercially used pieces of web software the industry has adopted. There is no hope for large segments of the industry. We actively choose to make bad decisions all the time, and then people rationalize them.
- babylon5 11mo agoFast to develop, fast to run under modest to reasonable requirements. Few things need to scale further.
- phyrog 11mo agoIt may not have to scale, but being able to use the same hardware for more (different things) is nice nevertheless.
- georgeburdell 11mo agoFastAPI is the best combination of an easy and a flexible Python library for web servers, from my experience. If I need performance, I will rewrite it in Go.
- amypetrik8 11mo agothe slowest API i ever seen is FastAPI