Even though unfortunate to loose support of good people like him, it would be in the interest of the foundation to honer the PM to make biggest impact for their efforts.
Buying a L4 car may be not possible. Because I don't even think they will start selling them initially. May be we can bet on number of L4 cars in operation after 5 years.
This is similar to what React.js or Vue.js does on the browser. I always thought of this, very nice to see it running.
I worry about the following..
1. How we do complex objects like Trees and Tables?
2. How efficient are these Native nodes over DOM nodes in Browser?
We did use in production. And it sucks to support it.
Problems..
* Dynamic components wont work with Vue. Lists etc.
* Loading individual html files for each component. Could not figure out how to bundle the components with Webpack.
If you still want to use it, use it without Vue or React.
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.
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.
We implemented our own. We don't need more than 10 different type of fields. So basically it will take couple of hours to create those base components to our requirements.
The main lession I learned in JS world is, when the requirement is small, better write it from scratch using code we find on net. Trying to integrate different incompatible libraries will just waste our time.
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 support from thirdparty Vue components.
* There are lot of silly components like footer and header etc. There is no need for defining them except to show that it is complete UI framework. Trying to be 'Complete UI Framework' is bad choice for any UI on Web. HTML is too flexible and requirements are too diverse that no one UI library can provide everything.
We finally replaced all Element Components with standard bootstrap code. Every thing works perfectly. And we get the benefit of 1000s people testing bootstrap.
Yes it is. Even though you are comparing two different libraries that does different things, vue.js is easy then jquery. Because it is much smaller in it's api. What it does is very simple and clear to understand.
I am using vue.js and vuex in some of my current projects. Only problem for me is that after adding Vuex and all it's getters, mutations and actions, my Vue component code now looks like lot of boilerplate code. Did any one else had that feeling. Is there any way I can directly connect vue template with vuex without intermediate component?
Yes, Hyderabad India. But still very less compared to market. Also because we are a money loosing product company :-).
At least in Indian market what most developers make is just based on luck. Mostly on what stupid interview question you can answer, and how long you are in job, how many times you switched jobs etc.
My entire company of 10+ developers combined earn less than those interns :-) It is okey, telling only for comparison. (BTW it is not like we are kids, we have multiple products which are like quickbooks and netsuite ERP).