Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

element.eleme.io

Post reply on HN
Print view View original

61–70 of 149 posts

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

#61

Post by Touche »

bpicolo wrote: post #60
WhitneyLand wrote: post #59

Earlier quoted context omitted.

I would disagree. ClojureScript is very cool, but unless you're adept at functional languages it's another big jump for someone new to front end development. Plenty of time to do CS a little later.

I mean, by that same metric if you aren't familiar with JS paradigms it's a leap on it's own, no? So I don't think that's the right metric on it's own. I also think that getting started with ClojureScript is pretty simple, even if you aren't super familiar with FP (though it will definitely stretch your brain a bit). ClojureScript gives you the opportunity to write code that's somewhat imperative, just with plenty of…

> I mean, by that same metric if you aren't familiar with JS paradigms it's a leap on it's own, no?

A smaller leap from a OO language to JS than to ClojureScript, surely you agree there.

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

#62

Post by Touche »

etimberg wrote: post #41
ergo14 wrote: 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 works very well for it's use case, but it is very difficult to make it work with tools like webpack. It ends up requiring what feels like a lot of hacks. SystemJS seems to be a bit easier to work with since there is a plugin for requiring the necessary HTML files. Polymer 2.0 looks to be much better.

I probably wouldn't let your build tool choice influence the UI framework choice. Other way around, actually. Polymer has an excellent build tool of its own.

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

#63

Post by Touche »

netforay wrote: post #55
ergo14 wrote: 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.

I mean, custom elements just shipped in Chrome a few months ago and are shipping in Safari soon. Firefox is in active development. So a bit too soon to say a technology's time has passed when it hasn't really had a chance up until this point.

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

#64

Post by Touche »

netforay wrote: post #52
lima wrote: 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…

I don't understand your point. Can Vue update ``? If so it should be able to update any custom element.

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

#65

Post by desireco42 »

netforay wrote: post #36

I have actually tried to use this to build an enterprise application. Here is what we found. * Most of the components they provide are very basic and does not actually require them to provide it. Couple of lines of wrapper on any CSS framework like bootstrap can make half of those components. * Most of the advanced components like DataGrid, DropDown Menus, etc are aither not available or buggy. You will get better su…

Thanks for writing this, as I was just browsing through and wondering how it would look/work in practice. I got impression that a lot of components really don't need Vue that much.

I am not against having things packaged like this, but like you said, Bootstrap, Foundation etc specialize in this, it seems like overkill not to use them.

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

#66

Post by bpicolo »

Touche wrote: post #61
bpicolo wrote: post #60

Earlier quoted context omitted.

I mean, by that same metric if you aren't familiar with JS paradigms it's a leap on it's own, no? So I don't think that's the right metric on it's own. I also think that getting started with ClojureScript is pretty simple, even if you aren't super familiar with FP (though it will definitely stretch your brain a bit). ClojureScript gives you the opportunity to write code that's somewhat imperative, just with plenty of…

> I mean, by that same metric if you aren't familiar with JS paradigms it's a leap on it's own, no? A smaller leap from a OO language to JS than to ClojureScript, surely you agree there.

Of course! That said, I think the typical use with ClojureScript/re-frame doesn't lead you into an academic or pedantic world of heavy FP. The benefits of being functional are largely abstracted away. You're mostly going to be writing some HTML in DSL-style reagent(1), and mapping over lists/maps.

That's largely why you can get productive reasonably quickly, even with the intimidation factor still present.

(1): https://github.com/reagent-project/reagent#examples

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

#67

Post by novaleaf »

progx wrote: post #40
netforay wrote: post #36

I have actually tried to use this to build an enterprise application. Here is what we found. * Most of the components they provide are very basic and does not actually require them to provide it. Couple of lines of wrapper on any CSS framework like bootstrap can make half of those components. * Most of the advanced components like DataGrid, DropDown Menus, etc are aither not available or buggy. You will get better su…

Did you use any library for example form validation, or did you do that on you own?

not vue, but I use ReactStrap + Bootstrap4 for that, and it works good.

Bootstrap 4 has some small rendering artifacts (like datetime inputs in inputGroups) but they are pretty fast about fixing them. (Though my input group example, the fix will be in the next release, beta1)

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

#69

Post by pas »

lima wrote: 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.

Frontends for tools -> dashboards, right?

https://github.com/akveo/ng2-admin

And to conjure it alive with data: http://stackoverflow.com/questions/39905586/how-to-consume-r...

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

#70

Post by Touche »

bpicolo wrote: post #66
Touche wrote: post #61

Earlier quoted context omitted.

> I mean, by that same metric if you aren't familiar with JS paradigms it's a leap on it's own, no? A smaller leap from a OO language to JS than to ClojureScript, surely you agree there.

Of course! That said, I think the typical use with ClojureScript/re-frame doesn't lead you into an academic or pedantic world of heavy FP. The benefits of being functional are largely abstracted away. You're mostly going to be writing some HTML in DSL-style reagent(1), and mapping over lists/maps. That's largely why you can get productive reasonably quickly, even with the intimidation factor still present. (1): https…

I think that's just a benefit of lisps in general, they don't focus on the academic "look at how smart I am" aspects of FP that the ML languages do.
Post reply on HN