Home
Why?
Rails’s current ActionView is a bit hard to read. Or, as a video game character says:
"Urgh... no more of this blasted magic. Let me rest for a while."And it’s not entirely clear whether ActionView is thread-safe.
What?
This fork attempts to address these problems. Highlights/goals:- Everything must be documented, including non-trivial private methods.
- There should be documentation that describe the internals, for plugin authors and/or template format implementors.
- Little magic. Code readability is more important than lines of code.
- Autoloading and lazy initialization support, so that commands in ‘script/*’ don’t have to load all of ActionView even when ActionView is never used. This improves startup time.
- Preloading support, for application servers that utilize copy-on-write.
- Mostly compatible with old ActionView. The design is made from scratch, but a compatibility layer implements backwards compatibility.
- Aggressive support for optimizations while not making the code hard to follow. For example, the new template format support system is designed entirely around the idea of compiling templates to a format that can be quickly rendered.
Recent edits
- Home by FooBarWidget
Seen Elsewhere
- Home in juanpare's fork
- Home in divoxx's fork
- Home in guan's fork
- Home in arunalangar's fork
- Home in timcharper's fork
- Home in crazycode's fork
Last edited by FooBarWidget, 3 months ago
Versions:
