Skip to content

Commit 228fc12

Browse files
phananchrisvfritz
authored andcommitted
Remove SystemJS mention from Riot comparison (#549)
1 parent 5dafb4e commit 228fc12

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/guide/comparison.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -324,6 +324,6 @@ Riot 2.0 provides a similar component-based development model (which is called a
324324

325325
- True conditional rendering. Riot renders all if branches and simply shows/hides them.
326326
- A far more powerful router. Riot’s routing API is extremely minimal.
327-
- More mature tooling support. Vue provides official support for [Webpack](https://github.com/vuejs/vue-loader), [Browserify](https://github.com/vuejs/vueify), and [SystemJS](https://github.com/vuejs/systemjs-plugin-vue), while Riot relies on community support for build system integration.
327+
- More mature tooling support. Vue provides official support for [Webpack](https://github.com/vuejs/vue-loader) and [Browserify](https://github.com/vuejs/vueify), while Riot relies on community support for build system integration.
328328
- [Transition effect system](transitions.html). Riot has none.
329329
- Better performance. [Despite advertising](https://github.com/vuejs/vuejs.org/issues/346) use of a virtual DOM, Riot in fact uses dirty checking and thus suffers from the same performance issues as Angular 1.

0 commit comments

Comments
 (0)