From 6612cf6ebd92b3d24acb923f79ac7501c3c348ab Mon Sep 17 00:00:00 2001 From: James Forbes Date: Thu, 30 Mar 2017 12:09:17 +1100 Subject: [PATCH] ES6 classes may require build tools. Instead of saying they won't need build tools, we can say that we only use native features of the language which usually makes for a simpler project. --- docs/framework-comparison.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework-comparison.md b/docs/framework-comparison.md index 96d9087f..cf8a3483 100644 --- a/docs/framework-comparison.md +++ b/docs/framework-comparison.md @@ -203,7 +203,7 @@ Vue | Mithril Vue is heavily inspired by Angular and has many things that Angular does (e.g. directives, filters, bi-directional bindings, `v-cloak`), but also has things inspired by React (e.g. components). As of Vue 2.0, it's also possible to write templates using hyperscript/JSX syntax (in addition to single-file components and the various webpack-based language transpilation plugins). Vue provides both bi-directional data binding and an optional Redux-like state management library, but unlike Angular, it provides no style guide. The many-ways-of-doing-one-thing approach can cause architectural fragmentation in long-lived projects. -Mithril has far less concepts and typically organizes applications in terms of components and a data layer. There's no need to install different sets of tools to make different flavors work, because all component creation styles in Mithril output the same vnode structure. +Mithril has far less concepts and typically organizes applications in terms of components and a data layer. All component creation styles in Mithril output the same vnode structure using native Javascript features only. The direct consequence of leaning on the language is less tooling and a simpler project setup. #### Documentation