Frederik Wessberg

@FredWessberg

Developer at

Copenhagen
gitHub.com/wessberg
Vrijeme pridruživanja: travanj 2010.
2 fotografije ili videozapisa Fotografije i videozapisi

Tweetovi

Blokirali ste korisnika/cu @FredWessberg

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @FredWessberg

  1. 31. sij

    So, I'm in doubt here. I always publish scoped packages, because I think it's the right thing to do and most future-facing too (required for the Github Package Registry, is one reason). But I get requests and PRs to drop the scope from a few of my packages. What do I do here?

    Poništi
  2. proslijedio/la je Tweet
    27. stu 2019.

    [THREAD] and directive require for tracking. EU websites rely on IAB banner providers to implement consent, but what happens behind the cookie banner interface? Our study finds 54% of them are non-compliant. (1/11)

    13 replies 265 proslijeđenih tweetova 320 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  3. 27. stu 2019.

    Web Components is an umbrella term for a set of **evolving** web platform APIs. You don't _build_ "a Web Component". Here's why I think it truly matters that we change the narrative:

    There's some things I need to get off my mind in terms of how we define, think of, and refer to Web Components, especially on Twitter. I know I'm probably not changing minds here, but I hope to bring some perspective to the discussion. Starting with the definition:
    Prikaži ovu nit
    2 korisnika označavaju da im se sviđa
    Poništi
  4. proslijedio/la je Tweet
    26. lis 2019.

    I just looked for on Twitter to post this exact thanks message. It’s a very well-assembled polyfill and exactly what I was looking for to conditionally load in Safari <= 12 etc.

    I just wanted to say a big "Thank you!" I was looking for a Pointer Events polyfill - turns out, most don't support Shadow DOM - thank you for both supporting Shadow DOM and for explicitly stating so in your README! 🎉👏
    Prikaži ovu nit
    2 proslijeđena tweeta 8 korisnika označava da im se sviđa
    Poništi
  5. 25. lis 2019.

    FYI: For a while, combining object-fit + contain:strict broke in Chrome Canary. Thought it was just a canary thing, but it slipped into the stable build with Chrome 78. Not sure if this is intentional or if I should report it as a bug.

    1 reply
    Poništi
  6. proslijedio/la je Tweet
    22. lis 2019.

    I just wanted to say a big "Thank you!" I was looking for a Pointer Events polyfill - turns out, most don't support Shadow DOM - thank you for both supporting Shadow DOM and for explicitly stating so in your README! 🎉👏

    1 proslijeđeni tweet 2 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  7. proslijedio/la je Tweet
    22. ruj 2019.

    Shout out again to 's plugin! It's amazing and suuuuuuuuuper undervalued. - 🗒️ Excellent and huge docs - 🤓 Simple and good configuration - 🥳 Unique features: type gen + bundling

    1 reply 1 proslijeđeni tweet 3 korisnika označavaju da im se sviđa
    Poništi
  8. proslijedio/la je Tweet
    14. kol 2019.

    As unscientific as it is, I find Myers-Briggs super helpful in understanding others. I wish all my friends could read this section about how my type (ENTP) handles friendship. It's eerily accurate and knowing this could save a lot of misunderstanding:

    10 replies 2 proslijeđena tweeta 31 korisnik označava da mu se sviđa
    Poništi
  9. proslijedio/la je Tweet
    12. kol 2019.

    The is all the incredible work on by the way. He doesn't Tweet much, but he should 😁 One day soon is going to tell the story of how Rune's work has drastically improved developer ergonomics at Google.

    5 proslijeđenih tweetova 25 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet
    3. kol 2019.

    Been working on supporting assertions in control flow analysis...

    8 replies 65 proslijeđenih tweetova 275 korisnika označava da im se sviđa
    Poništi
  11. proslijedio/la je Tweet
    30. srp 2019.

    I've had some thoughts about the great ocean of web developers who we never talk about.

    67 replies 223 proslijeđena tweeta 582 korisnika označavaju da im se sviđa
    Poništi
  12. 24. srp 2019.

    I would hope that the critical voices will be used constructively in further standardization work rather than to flat-out dismiss the concept of a unified component model for the web and help fight baseless claims.

    4 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  13. 24. srp 2019.

    There are incredibly talented people in this community, some of whom are actively arguing against Web Components, but not all of the people who are following them on Twitter may understand entirely the many layers in this discussion.

    1 reply 2 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  14. 24. srp 2019.

    Such libraries work on DOM nodes and elements, and Custom Elements is just that - Elements! So, pointing out that you can't pass complex data to Custom Elements (read: Elements) is baseless, misdirected critique that I hope I've heard for the last time.

    1 reply 4 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  15. 24. srp 2019.

    The fact that you use a library such as React, Vue, or Angular doesn't change that. But these libraries provide ergonomics that abstracts that away and help you bind to properties rather than attributes declaratively.

    1 reply 1 korisnik označava da mu se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  16. 24. srp 2019.

    An example being that you can't pass complex data to your elements declaratively. That is not critique of Custom Elements, that's critique of HTML as a markup language since binding declaratively to properties is offered by other DSLs such as JSX, Angular HTML, or even lit-html.

    1 reply 1 korisnik označava da mu se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  17. 24. srp 2019.

    No one is arguing (I hope!) that we're there yet. Of course not, the web platform is forever evolving, as it should be. But - some of the critique is baseless and sometimes rooted in either not understanding how the DOM works or wanting to dramatically change that.

    1 reply 1 korisnik označava da mu se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  18. 24. srp 2019.

    And then something else. When I look at some of the pain points put forward, much of it is fair, constructive, and addressable. A few examples include declarative shadow roots, efficient rendering and re-rendering, HTML/CSS support for the module loader, etc.

    1 reply 2 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  19. 24. srp 2019.

    - Developers comparing DX and ergonomics 1:1 between CEs and equivalent library code. - Library authors implementing their own component models. - More "Why I Don't Use..." and less "Here's what I think we still need to work on..." blog posts.

    1 reply 3 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  20. 24. srp 2019.

    If we don't shift the definition of Web Components from this one into another one that treats it as a term for the specification work that makes up the ongoing effort to standardize and improve upon the component model for the web, we'll see:

    1 reply 1 korisnik označava da mu se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi

@FredWessberg još nije objavio nijedan Tweet.

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·