My Thoughts on Using element-ui

Last week I built a service using vuetify. Fed up (?) with vuetify’s clutter (?), I then built a service using element-ui, which looks comparatively clean, and jotted down my impressions.

Pros

1. It’s pretty.
2. The documentation is remarkably neat and well done.
3. It’s as easy to learn as Bootstrap.

Cons

1. As of v2.5.4, Korean input doesn’t work well in forms when using IE (Internet Explorer) (!). Of course, this can be fixed by modifying element-ui’s source code; just refer to this post to fix it.
2. Compared to other UI frameworks like vuetify, there are a few missing components (such as a divider…).
3. The ecosystem is less rich than vuetify’s.
4. Surprisingly, the default language setting is Chinese. So to view the calendar in English, you have to set the language to English via i18n.
5. Unlike vuetify, you can’t install it with a Vue CLI command. Now you can install it (vue add element).

Overall

1. I’m not sure it’s good enough to have several times as many GitHub stars as other Material Design-family UI frameworks.
2. I’d be reluctant to use it in situations where you can’t control the web browser. After all, Korean input doesn’t work well in IE…

The end!