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

51–60 of 149 posts

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

#51

Post by WhitneyLand »

Desktop only framework seems like a bad idea.

- How can you be sure you won't be asked for a mobile or responsive version down the road? People change requirements all the time.

- If you want to ever work on other type of projects you now have to learn two when one may have sufficed

- Community size is a huge factor for contributions and momentum, and desktop only limits your community size

For this framework it would be more useful if they offered a single component for a data grid. That's more work than the rest of the framework combined.

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

#52

Post by netforay »

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

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 does not know this. Once the Dom for parent tag is created, Vue assumes its work is done. And if data change mean while it will remove it or update it. But Life Cycle of prevously create Polyermer component may still in progress...and you will get lot of exceptions in console.

How to burn your fingers and see this problem..?

Try to use OnsenUI Polymer components with Vue.JS. Mainly any List and Table tags with dynamic children bound to data.

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

#53

Post by aczerepinski »

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.

React. If you're new to the front end, it makes sense to choose the most popular tool that has way more documentation, blog posts, stack overflow answers, etc than anything else.

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

#54

Post by WhitneyLand »

coldpizza wrote: post #34
deallocator wrote: post #30

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

"it's for desktop apps" haha can you imagine if desktop users had different resolutions and aspect ratios on their screens? oh wait...

It's an excellent point. This one response from the team is enough for me to lose confidence in the project.

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

#55

Post by netforay »

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

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.

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

#56

Post by weka »

pdxandi wrote: post #28
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.

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 to understand in chunks and each part of webpack serves a purpose to better optimize and structure your workflow.

[1] https://webpack.github.io/docs/tutorials/getting-started/

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

#57

Post by weka »

overcast wrote: post #44
LeoNatan25 wrote: post #26

What does "eleme.io" even mean? How sad of state are we that everyone feels compelled to use these nonsense "io", "me", "to", etc. domains just because they are "hip".

It means the domain squatters own just about every single word of every TLD at this point.

I can attest to this fact. Many domain squatters sit on four, five and even six letter premium .com/.org./.net domains waiting for their payday that never comes because no one will ever pay that much money when the alternative is to use another domain name.

And of the people that CAN pay that money, what happens is they send a notice of their newly-established IP being used in a domain and they get it with the help of the registrar.

It's ridiculous to expect a person pay $1000+ for a domain when they go 'oh, we'll just use another domain name!'

People are dumb.

edit: spelling

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

#58

Post by netforay »

lima wrote: post #45
simooooo wrote: post #5

Earlier quoted context omitted.

I've been using Vue for a similar purpose this last week or two and I've found it very simple and easy to follow. I'd recommend that.

What component library to use?

Depends on which components you need. Normal HTML with Bootstrap CSS will mostly cover the basics.

And there are other individual Vue component libraries like VueTable etc.

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

#59

Post by WhitneyLand »

bpicolo wrote: post #22
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.

If you want it to feel more like backend development, give clojurescript a whirl. Best way to do that is start with this template: https://github.com/Day8/re-frame-template Which is based on this library: https://github.com/Day8/re-frame ClojureScript is fantastic. Being immutable as a baseline makes it work so much better in the React world of things. That said, if you haven't used any Lisps it can be a bit intimida…

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.

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

#60

Post by bpicolo »

WhitneyLand wrote: post #59
bpicolo wrote: post #22

Earlier quoted context omitted.

If you want it to feel more like backend development, give clojurescript a whirl. Best way to do that is start with this template: https://github.com/Day8/re-frame-template Which is based on this library: https://github.com/Day8/re-frame ClojureScript is fantastic. Being immutable as a baseline makes it work so much better in the React world of things. That said, if you haven't used any Lisps it can be a bit intimida…

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 extra parentheses.

Post reply on HN