4 ms·
This might be true for general purpose languages, but as a data point Django's templates suffer immensely by the implementers being unaware of how to write a fa
by rtpg 12y ago
This might be true for general purpose languages, but as a data point Django's templates suffer immensely by the implementers being unaware of how to write a fast compiler/interpreter.
- spullara 12y agoThis is true. Getting the performance that I do from mustache.java has a lot to do with using JIT techniques.
- obstinate 12y agoHowever, there are plenty of people who know how to write compilers. The question is why they weren't involved in making Django templates?
- chii 12y agobecause it's a relatively boring and uninteresting problem? The intersection of people who find a particular niche problem and also knows how to do parsing, compiling and optimizing well is pretty small.
- rtpg 12y agoWell when Django started out it was this small project for web developers, right? Anecdotally, I've found the compiler people universe and the web developer universe to be pretty disjoint for a long time.
- mseri 12y agoI think they would be happy is somebody points them in the right direction. Do you have any specific comment or suggestion?
- DasIch 12y agoThe problem isn't that the implementation is bad. The template language is designed in a way that makes a fast implementation impossible. There is no reasonable way of improvement. A problem that is solved in Django 1.8 by making it possible to easily switch template engines.