In a project I work on right now I use no XML/HTML. I love HTML and it's great for static web pages/documents and for "old school" server side rendering. But for a SPA with real time and dynamic updates, it's the wrong tool. It's much faster appending the elements to the DOM. Lexical scope and closures plus being able to call functions that returns elements in JavaScript makes it fun.
Element – A Vue 2.0-based component library for developers, designers and PMs
81–90 of 149 posts
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#82Earlier quoted context omitted.
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.
The performance benefits of virtual DOM / DOM diffing are way, way overrated IMO. You can use that stuff with Polymer where you really need it, but I just use plain Polymer for everything and it's awesome. I think the time for React is gone :-P
Jesus, already? :-P
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#83Question 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 started a simple project a week ago. I use Vue and Semantic-UI. This combination looks very good for me so far.
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#84Question 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.
Of the 3 choices that you gave, I'd use Vue.
If you broaden the scope to 'let's use anything', then I'd suggest Ember since I like their model layer better.
The React ecosystem is a bit fractured at the moment, so jumping into it is a full-time job.
In a year or two, I expect it to settle down when some framework rises out of the morass and gains credibility amongst the majority of dev's.
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#85That ass http://element.eleme.io/static/banner-bg.75437e1.svg
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.
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#86Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#87Earlier quoted context omitted.
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 o…
[deleted]
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#88What 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".
the company that develops it is called "Ele.me"[0] [0] https://www.crunchbase.com/organization/ele-me
Interesting. Then the domain is not that terrible as I thought. Too many "eleme" in the names. :-)
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#89I 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…
So how was Vue for an enterprise application?
Re: Element – A Vue 2.0-based component library for developers, designers and PMs
#90I 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…
Was surprised on mobile that the InputNumber field doesn't spawn a dialer pad (tapping it brings up the alpha keyboard). There are some elements here, for sure, that just seem to be minimally skinned and not fully thought out. Bummer, because I have a lot of work based around enterprise design systems and I love seeing fresh takes on these types of components... not much depth in this library, unfortunately.