3 ms·
You're correct, and that's the same excuse Ruby and Python advocates use when developers complain about performance. Frankly, it's bullshit. Take Rails as an e
by rlander 10y ago
You're correct, and that's the same excuse Ruby and Python advocates use when developers complain about performance. Frankly, it's bullshit.
Take Rails as an example. In 2006 we were told that Ruby's slowness didn't matter since web apps spend most of the time waiting for IO, processors were getting faster, yada yada yada.
Guess what? 10 years later and Rails is still slow. Django is also slow. Template rendering is slow. I've written enough Erlang, Clojure and OCaml apps to know that no, I don't need "russian doll caching" in a fast language. Hell, I rarely need caching at all. My database layer is fast enough. /rant
- meric 10y agoI'm Django developer and I agree with you. We've ditched Django templates entirely. We use it as our API platform only - most of the computation time is spent in json and in Postgres.
- raverbashing 10y agoDjango is slow sometimes, true (the worse is when it's slow when it doesn't make sense, that is when you don't expect) There are tricks and things that help (if you want to shoot your DB performance in the foot use multi-table Model inheritance) Try Jinja2 for templates