News for hackers. Stuff that matters.
Re:Explaining React's license by boubiyeah on Saturday August 19, 2017 @08:15AM (#15052968)
google is pretty bad at frontend frameworks from my experience :D Polymer is an experiment that should have stayed in that state.
Re:Explaining React's license by gramstrong on Saturday August 19, 2017 @01:50PM (#15054626)
I'd argue that google is pretty strong when it comes to frameworks, and that most of their criticism comes from people who aren't looking for a framework, but rather a library (like React).

And Polymer isn't even really either of those things, it's a polyfill for a native browser feature.

Re:Explaining React's license by ergo14 on Monday August 21, 2017 @09:48AM (#15064572)
Polymer is not a polyfill for web components - it is higher level library - something like "jquery for web components" - WC polyfill is separate project, in separate repo - you will need it with X-Tags, Svelte, SkateJS too.
Re:Explaining React's license by boubiyeah on Saturday August 19, 2017 @04:04PM (#15055290)
No, a polyfill has to closely mirror an API. Polymer is inspired by web components but went its own way for several features.
Re:Explaining React's license by Zenbit_UX on Friday August 25, 2017 @10:00AM (#15098450)
I'm guessing you're hating on Angular? Why? I'm a huge fan of 1.x & polymer, but I'm curious to know why you think it is not worth using.