4 ms·
This is like the old Opera argument: Our browser obviates the need for most extensions, so why should we provide an API? In my example, a CMS for Pete's sake,
by teilo 17y ago
This is like the old Opera argument: Our browser obviates the need for most extensions, so why should we provide an API?
In my example, a CMS for Pete's sake, there is a very real and pervasive need for custom tags that are in no way obviated by Jinja2's architecture. Jinja2 is a great developer template library, but, as a previous poster noted, a very poor Designer library. I code my platform for Designers. So do a whole lot of other CMS programmers. So this line of reasoning, while accurate, is moot.
- shadytrees 17y agoThat wasn't piranha's argument though. The argument was that Jinja's tags API is more difficult to use because it provides structured access to the code whereas Django just gives you a string. That Opera analogy doesn't apply because the API clearly exists.