Devon Govett

@devongovett

Full stack JavaScripter. Author of . Engineer . Previously and .

San Francisco
Vrijeme pridruživanja: kolovoz 2008.

Tweetovi

Blokirali ste korisnika/cu @devongovett

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

  1. prije 44 minute

    Parcel 2 now has automated nightly releases! If you wanted to try out the bleeding edge without building from git yourself, now you can. 🎉 yarn add parcel@nightly Thanks to for implementing it!

    Poništi
  2. 31. sij

    RIP my twitter notifications 😂

    Poništi
  3. 30. sij

    What I really want is a way to render static content with interactive islands built with React. A documentation site with inline examples shouldn't force the whole site to re-render client side. I know the React team is working on partial hydration. It can't come soon enough! 😀

    Prikaži ovu nit
    Poništi
  4. 30. sij

    I just found a Gatsby page downloading an 11MB JS bundle containing all of the data for the entire site, because it was "used" to render a static list of links to other pages. There is no reason to re-render that client side.

    Prikaži ovu nit
    Poništi
  5. 30. sij

    The worst part is how easy it is to create giant bundles without realizing. You don't just download the code to render the page again, you also re-download all of the data used to render it, even if it's completely static.

    Prikaži ovu nit
    Poništi
  6. 30. sij

    Unpopular opinion: React is the wrong tool for building content websites (blogs, marketing sites, documentation, etc.) today. SSR is not good enough. You end up downloading the content twice: once in the HTML, and again in the JS for hydration. How did this become so common? 😱

    Prikaži ovu nit
    Poništi
  7. 30. sij

    I, for one, welcome our Yarn 2 overlords. Turning on PnP by default, however painful in the short term, is the only way to ensure its adoption in the long term.

    Poništi
  8. 29. sij

    “Handoff” is perhaps the worst term in our industry at the moment. It implies that design and development are completely separate and that design can be “done”. Design and development are really a single collaborative process. Our tools need to unify to reflect that!

    Poništi
  9. 28. sij

    The goal for any documentation should be to be make it possible to use a library without reading the source. Otherwise, what's the point of the docs - just read the code! Users shouldn't need to understand the abstractions in the implementation in order to use it.

    Prikaži ovu nit
    Poništi
  10. 28. sij

    Instead, documentation should reflect the public API that a user would actually use. Rather than exposing all the abstracted types and generics in the docs, flatten them into something that a user would actually write in their own code.

    Prikaži ovu nit
    Poništi
  11. 28. sij

    Many documentation generators simply take in code, and output HTML pages based on the exact types in that code. This leads to the docs reflecting implementation details only relevant to the authors of the code, for example extended shared interfaces, generics, etc.

    Prikaži ovu nit
    Poništi
  12. 28. sij

    Let's talk about documentation. I'm starting to think that docs should NOT directly reflect the structure of the source code as many documentation generators do today. As type systems get more complex, and more types are abstracted, documentation gets harder to understand. 🧵

    Prikaži ovu nit
    Poništi
  13. proslijedio/la je Tweet
    27. sij

    So far, I've been demoing my visual React editor with Spectrum, the design system I work on, but the neat thing about it is that it works with any existing component library. No modifications needed! 🤩 Here's a demo using Chakra UI.

    Prikaži ovu nit
    Poništi
  14. 27. sij

    The only requirement at the moment is TypeScript definitions for the props, but theoretically it could support Flow or propTypes too. The goal is to make it as easy as possible to visually edit your existing production app, without forcing your whole team to change workflows.

    Prikaži ovu nit
    Poništi
  15. 27. sij

    So far, I've been demoing my visual React editor with Spectrum, the design system I work on, but the neat thing about it is that it works with any existing component library. No modifications needed! 🤩 Here's a demo using Chakra UI.

    Prikaži ovu nit
    Poništi
  16. 27. sij
    Poništi
  17. 26. sij

    I highly recommend that JS developers be open to learning other languages. It’s useful to have alternative perspectives and tools at your disposal. Tasks don’t need to be impossible to you if they are not available in a language you already know. Learning is easy and fun! 😊

    Poništi
  18. proslijedio/la je Tweet
    25. sij

    Incredible overview of non-standard web platform features that debuted in Trident, the engine behind good ol’ Internet Explorer: by

    Poništi
  19. proslijedio/la je Tweet
    24. sij

    Playing around with the inspector panel. Props are now grouped into categories with smarter editing controls for certain values (e.g. margins, borders, etc.). Event handlers can be added with a single click to create a function. Even auto imports and adds argument types! 🙂

    Poništi
  20. 24. sij

    Ah, again battling the many separate JS tools that should be one that work subtly different from one another. This time: documentation generators. does Rome have a doc generator? 🙏

    Poništi

Č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:

    ·