Live data from Hacker News

Element – A Vue 2.0-based component library for developers, designers and PMs

element.eleme.io

91–100 of 149 posts

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#91
post #37

Earlier quoted context omitted.

I would suggest Polymer. Web Standards based - has comprehensive library of elements and polymer itself is a tiny library. I've had very good experience with it - if you know html/JS you will feel at home. As for being "feature complete" - it has probably best implementation of material design elements and you can find a ton of other element on https://www.webcomponents.org/ . It is also interoperable with other solu…

Polymer is built for the world without Vue.js or React. They are slow and heavy weight compared to very very optimized DOM operations done by Vue.js or React. I think the time for Polymer is gone, and it is better to forget that it exists.

Interesting - the benchmarks prove otherwise - it is as fast as other new solutions. So i think you never actually used it in production at any scale.

If angular 1.5 was OK for thousands of devs over recent years then Polymer that is comparable to ng2 or react is more then enough.

Not to mention that for a world without polymer - some of biggest enterprises in the world are betting on it (and I don't mean just google here).

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#93

Earlier quoted context omitted.

This adds nothing to the discussion and is frankly in poor taste.

Actually It adds a lot to the discussion; It shows their views on women, which I guess are "things" with big asses and boobs; maybe in the next version they can have the male developer spraying her down with a hose, while she chugs some beer.

Holy crap. I am dying rofl.

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#95
post #46

Earlier quoted context omitted.

Can I use Polymer components with Vue.js?

No you can not. Telling from experience. Here is the reason.. Vue is optimized to create/update your DOM elements based on data. Polymer does create a DOM node and internally implement lot os JS to create their own shadow DOM. Each Polyer component can have different life cycle (for Example and Table Component can actually creat TR,TD elements after some time of creating your Custom Table Polymer component). And Vue…

Weird, vaadin made a compat layer for polymer/angular and it works well. I would expect vuejs would also work reasonably well with proper compat. shim, there is one for vue 1.x.

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#96
post #2

Question for HN: I'm a systems developer and want to play a bit with frontend development (writing frontends for custom tools I built). What framework + feature-complete component library is recommended in 2017? React? Vue? Polymer? Plain JS with intercooler.js? I feel a bit overwhelmed.

As a back-end developer who recently made a trip up to frontend worlds I would recommend vue.

Big advantage of vue, that you can just include vue, some component library (like the above, or vue-mdl in my case) and start building stuff. You don't need learn 5 new transpilers and build tools to get the simplest thing done like described in https://hackernoon.com/how-it-feels-to-learn-javascript-in-2... .

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#97

I really like Element but it's a shame they don't it responsive, when I tried contributing to make things responsive they actively denied the PR saying it's for desktop apps. Actively refusing pull requests that make the framework responsive is a bit of a downer for me, but overall I like what the author(s) did

They have their own mobile ui https://github.com/ElemeFE/mint-ui

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#98

I like that this one has a tree component, it seems like most widget sets (SemanticJS and Bootstrap and everything Material included) forget about the tree.

Actually, I have seen multiple libraries aimed for desktop UI that implement trees. Seems that trees somehow were lost in the transition to web applications.

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#99

For anyone looking for a lightweight responsive library, Bulma http://bulma.io/ is a great option. It pairs with Vue quite well since it's a CSS only library. Note: I'm not affiliated with them, just using them on my latest project.

It's looking good, one thing that bothered me as it's css only is that form elements like checkboxes and radio buttons need to be styled separately (https://github.com/jgthms/bulma/issues/44)

Re: Element – A Vue 2.0-based component library for developers, designers and PMs

#100
post #56
post #28

Earlier quoted context omitted.

I agree that it depends on your project, but I've used all the frameworks you listed and Vue.js stands out to me. The documentation is top notch, the ecosystem is flourishing, and using the framework feels intuitive. Drop one script into your project and you have a fully reactive front-end at your disposal (or you can use a more complex build system like Webpack). I'd suggest reading the official 2.0 guide here: http…

Let us dispel the notion that webpack is 'complex'. webpack works extremely hard to make its documentation [1] and overall tool easy to read and use. The community is ever-growing and it has one of the most helpful and enthusiastic maintainers I've ever seen a JavaScript OSS project have. Ever. (Look at you Larkin!) From egghead.io to online documentation, you will see that while webpack has a lot to it, it is easy t…

Webpack is complex in the same way that all build systems are complex – they take time to understand and configure. In the context of this thread, where a systems developer is feeling overwhelmed by front-end development options, Webpack is certainly an added complexity regardless of how well it's documented (which, I agree, have significantly improved).

I understand where you're coming from (Webpack initially got a bad reputation as being complex and folks are working hard to improve it) but my note about complexity was relative to simply dropping a script in the page to get Vue.js up and running.

To all the Webpack maintainers, and to all contributors of open-source projects, I can't thank you enough for your efforts. You open doors and expand the minds of developers like me and I'm forever indebted to you.

Post reply on HN