4 ms·
> Doesn't the question that started the thread imply the exact opposite? I'm asking about demographics here avoiding the discussions. People are leveraging web
by ergo14 11y ago
> Doesn't the question that started the thread imply the exact opposite?
I'm asking about demographics here avoiding the discussions.
People are leveraging webcomponents all the time, recently i saw job opening at slack for Polymer dev.
> Where's this "uptake" -- outside of Google, who can use whatever they want
I saw questions about webcomponents/polymer pop up all the time for aurelia and other frameworks (how to integrate nicely), github uses components too, salesforce. It seems that here is it treated like something that doesn't exist.
> The shadow-dom (and it's speed, predictability benefits)
React doesn't provide shadow DOM I think? Polymer does, i think it is the opposite?
> Being able to run on the server
This is cool and a nice selling point, I've been interested to do that multiple times but it appears that this is only possible if you build your app in node.js?
> React native
This is also awesome selling point, I still have reservations about PATENTS clause in all FB-related open source projects.
- coldtea 11y ago>I saw questions about webcomponents/polymer pop up all the time for aurelia and other frameworks (how to integrate nicely), github uses components too, salesforce. It seems that here is it treated like something that doesn't exist. I don't think it's only here (on HN) though. Check Reddit reactjs, polymer and webcomponents subreddits for example. The first has constant traffic everyday, the other have 1-2 recent posts, and get to month old posts on the first page. Same for tutorials and blogs. Polymer/WebComponents related ones are few and far between, React ones are everywhere. GitHub: polymer 14000 stars, react 37000 stars (and 4 times as many forks). Regarding the "shadown-dom", yeah, you're right, meant to write "virtual-dom" (a much lightweight dom copy, with faster access and the ability to diff to avoid doing costly work to the real DOM). >This is cool and a nice selling point, I've been interested to do that multiple times but it appears that this is only possible if you build your app in node.js? You can run it at any app server that can execute JS. So not just Node but also Meteor, and Java servers to (Java as of late comes with JS interpreter built in). And you can also fork out from any other framework and do the rendering part in a JS interpreter, e.g. like this: https://github.com/tildedave/universal-react-without-node https://github.com/tildedave/universal-react-without-node I'd say the most practical versions would be Node and Java though.
- ergo14 11y agoRight, I do python for living though... so I'm out of luck :P