A Quest for the Ultimate Template Engine
summary
Benchmarks use a Rails scaffold with 1000 records and 100 requests to compare engines and find Haml compiles into much larger Ruby output than ERB, yielding about 7% slower view rendering in that test; Slim and Temple-based engines trade syntax for speed, and a Temple-built experimental engine reports even faster results. A practical fix was attempted by creating hamlX fork to shrink generated Ruby and approach ERB performance, but parity is not fully achieved and the Temple rebuild is still experimental.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:40My personal story About Ruby template engines
- 6:36A Ruby committer The author of Net::HTTP, FileUtils, Ripper, Race, TMail, etc. The author of legendary Ruby book "Ruby Hacking Guide"
- 6:55History of Minero Aoki 1999: Became a Ruby Committer 2002: Wrote RHG while he was student ..2013: Had been doing something else, wearing suit 2013: Came back to the Ruby world as a Rails programmer
- 12:26We're Ruby programmers If you really care about the app's performance, your app should've written in What we should care is the balance
- 15:07Hello, World!
- 19:14the Ruby code
- 21:20eagle? tomato?
- 24:36Worth Trying This If you're really sure that your system's bottleneck lies in the template engine If you want to experience the world's fastest Template engine
- 25:14Developer Experience Syntax End User Experience Runtime Performance
