|
|
@ -39,7 +39,8 @@ reasons: |
|
|
|
ability to build abstractions.** This is incredibly important in |
|
|
|
large applications. |
|
|
|
- "Logic" and "markup" are intimately tied, and are both part of the |
|
|
|
"presentation" layer, so we're not breaking separation of concerns. |
|
|
|
"presentation" layer, so we're unifying the presentation layer, |
|
|
|
not breaking separation of concerns. |
|
|
|
- Large projects usually don't use WYSIWYG editors for production |
|
|
|
code, so breaking apart markup from the code that creates it usually |
|
|
|
only introduces friction. |
|
|
|