ergo14

24 ms·

1. 211.▲
   by ergo14 9y ago

   Thats what web components aim to do, take Polymer - you get only minimal library on top of the spec, and with more browsers supporting the standard you just shed the polyfills for missing bits.
2. 212.▲
   by ergo14 9y ago

   You can use web components with redux. The implementer of that said "mini cart" can make all the decisions for you, but you will end up with reusable "mini framework" in the end.
3. 213.▲
   by ergo14 9y ago

   I like the KB on the dell latitude line.
4. 214.▲
   by ergo14 9y ago

   The next jquery will be probably Polymer (since it is a library). VueJS/Angular are bigger frameworks.
5. 215.▲
   by ergo14 9y ago

   https://www.google.com/patents/US20170221242 - The majority is probably wrong in this case, unfortunately.
6. 216.▲
   by ergo14 9y ago

   https://www.google.com/patents/US20170221242 - It event mentions React. So maybe we should stop using the word "potentially" when it comes to React patents.
7. 217.▲
   by ergo14 9y ago

   It is low level API to be non-opinionated. Or at least it makes sense for me to make it like that. Same as web assembly, service worksers and others - that is a step in right direction IMO. Same as for example Python providing WSGI - you do
8. 218.▲
   by ergo14 9y ago

   I think web components are low level and non-opinionated to give you freedom of implementation for higher level things. Thats what Polymer, Stencil, Svelte, SkateJS are for. Indeed WC API is not the nicest to work with to say the least, but
9. 219.▲
   by ergo14 9y ago

   I actually implemented React's UI Router in polymer, works the same as in Angular 1/2. The biggest issue with web components in general are problems with Shadow DOM support. Which means you need to do elements without shadow compo
10. 220.▲
    by ergo14 9y ago

    From index page "Polymer is a JavaScript library that helps you create custom reusable HTML elements". I'm using Polymer components same as as react's controller/view components. You don't need to reimplement
11. 221.▲
    by ergo14 9y ago

    Actually - the process of creating both is exactly the same, I created components in angular, react and polymer. No difference IMO (apart implementation details).
12. 222.▲
    by ergo14 9y ago

    I'm not talking about the API design, I'm more worried what happens if Evan dies, or just loses interest in it. Bus factor of 1.
13. 223.▲
    by ergo14 9y ago

    I like Vue, but one thing that worries me is that 99% of commits are being made by a single person.
14. 224.▲
    by ergo14 9y ago

    Hm, I believe that the templates will be inlined in your elements in build step. Or at least easly can be, since I also did components with separate preprocessed css, separate js and HTML template.
15. 225.▲
    by ergo14 9y ago

    How is this like PHP (didn't touch PHP in 8 years)? It is closer to hyperHTML or JSX with different syntax I think.
16. 226.▲
    by ergo14 9y ago

    IE11+ will work and everything modern. If you don't have native support things get polyfilled. Youtube nowdays runs on Polymer, web components and they support older browsers.
17. 227.▲
    by ergo14 9y ago

    Nothing wrong with that. In fact google releases quite a few projects like that - the important thing is what is inside the patents clause. Apache 2.0 also has one and no one argues against it.
18. 228.▲
    by ergo14 9y ago

    Yeah, as long as you have the polymer as dependency - it should work, you can mix it with vuejs, preact or angular 2+ already.
19. 229.▲
    by ergo14 9y ago

    React is not really interoperable with other frameworks, libraries. Thats probably one of its bigger drawbacks. It is not an issue if you create a react application, but when you want to provide reusable components it might be problematic.
20. 230.▲
    by ergo14 9y ago

    You will be able with Vue and preact, react has some issues (that hopefully will be adressed soon). https://custom-elements-everywhere.com/ check this site for more info.
21. 231.▲
    by ergo14 9y ago

    But thats exactly true, companies build solutions that solve their problems. No secret knowledge here.
22. 232.▲
    by ergo14 9y ago

    Basicly everything on par with IE11 and above (with polyfills or without).
23. 233.▲
    by ergo14 9y ago

    > WebComponents in general are a solution in search of a problem Maybe they don't solve your problem, but they certainly seem to solve Ionic's or Netflix's problems (or mine for that matter).
24. 234.▲
    by ergo14 9y ago

    Yeah, indeed it does look really nice, the API feels a bit weird though, not sure why lifecycle events are named after react.
25. 235.▲
    CEE – Making sure frameworks and custom elements can be friends(custom-elements-everywhere.com)

    1 points by ergo14 9y ago|0 comments
26. 236.▲
    Polymer Developer Summit 2017 – Live Stream Day 1(youtube.com)

    1 points by ergo14 9y ago|0 comments
27. 237.▲
    by ergo14 9y ago

    I think apple opposed is="" and its not implemented in their browsers.
28. 238.▲
    by ergo14 9y ago

    You can emit normal events (they bubble up normally), you can use a notification bus, redux, whatever you want. And your elements are visible in DOM normally like all other elements.
29. 239.▲
    by ergo14 9y ago

    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.
30. 240.▲
    by ergo14 9y ago

    https://hnpwa.com/ - check out how fast polymer version is.