131–140 of 149 posts
Earlier quoted context omitted.
Mithril is a very non-overwhelming framework. You can find a number of pre-built components for it at https://github.com/lhorie/mithril.js/wiki/Components but I bet you'll end up building your own. How familiar are you with JavaScript? HTML?
I've found Mithril to be a giant pile of crap. Buggy on most browsers and incredibly painful to use. Run, don't walk from this platform.
Earlier quoted context omitted.
I've never used Element, but I share your sentiment. For a library like Vue which doesn't yet (!) have the adoption of React, I tend to avoid 3rd party component libraries especially if they are full of fluff like footer/header components. I looked at using Vue 2 with bootstrap 4 this past weekend and it seems most Vue+bootstrap integrations are for Vue 1.x while the Vue 2.x bootstrap libraries are incomplete. Instea…
It all just seems like a massive wasted effort. I think many of us pursue new tech to ensure the chore of doing our work remains fun and engaging, the most important priority! Probably billions of dollars got spent last year just so startups could migrate between one pointless stack and another to entertain their developers instead of their users, and the punchline is the developers still aren't comfortable enough.
I was mainly referring to the wasted developer effort of making wrappers for bootstrap, foundation, semantic UI, etc. of varying quality for every framework (react, vue, ember, etc).
In addition, while I realize this isn't a realistic goal :) I wish that our choice in component library was independent of our framework of choice. For instance, it would be nice to use ionic with Vue without spending 2 years writing a vue-ionic wrapper.
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 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…
What is a DataGrid? A Table? I seriously don't know that
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…
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
Earlier 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.
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…
If you still want to use it, use it without Vue or React.