Misko Hevery

@mhevery

CTO at , creator of , , , co-creator of

Saratoga, CA
misko.hevery.com
2008年5月加入
29 個相片或影片 圖片與影片

推文

你已封鎖 @mhevery

你確定要查看這些推文嗎？查看推文並不會將 @mhevery 解除封鎖

  1. 已轉推
    9 小時前

    What I find *really* interesting about this is he's not saying is near 0 JS. He's saying Qwik and *your app* is near 0 JS on initial load. Qwik is like partial hydration to the max. Very very interesting tech here.

    or, if you want to push to the extremes of speed and not afraid of early adoption, can serve any size/complexity of app with near 0 JS, and is worth a close look
    顯示此對話串
    5 則轉推 7 個喜歡
    還原
  2. 已轉推
    1月24日

    Stop hard-coding page layouts. Use API-driven UI to: - Decouple page updates from deploys - Schedule, a/b test, and personalize via APIs - Reduce code + increase composability Example below with :

    3 replies 10 則轉推 51 個喜歡
    顯示此對話串
    顯示此對話串
    還原
  3. 已轉推
    1月20日

    I have my reasons ok

    7 replies 27 則轉推 121 個喜歡
    還原
  4. 已轉推
    1月20日

    Enterprises can no longer afford to neglect . Thanks to , TTI now affects and app profitability. 💰 Learn how to get 💯 out of 💯 on Google PageSpeed in this session by and more, here:

    9 則轉推 8 個喜歡
    還原
  5. 已轉推
    1月20日

    So Partytown allows seamless main thread access from the web worker thread... but how? - Proxies browser globals to be available in the worker - Uses Atomics to run minimum tasks in main thread - Falls back to synchronous service workers for older browsers

    2 replies 10 則轉推 39 個喜歡
    還原
  6. 已轉推
    1月19日

    . is pretty magical, but where does it draw inspiration from? - Wiz - internal Google framework with smart hydration - React - JSX, functional components, hooks - Vue - simple, mutable state management - SolidJS - smart, unique JSX compilation

    9 則轉推 51 個喜歡
    還原
  7. 已轉推
    1月18日

    With Partytown, multithreaded JS has never been so easy - JS runs in the worker thread by default - Automatically hops to the main thread only as needed - Batches and caches values to reduce hops And it's all automatic, you just write normal JS, Parytown handles the rest

    3 replies 5 則轉推 47 個喜歡
    還原
  8. 1月14日

    Don’t be fooled by ’s familiar DX, runtime is the real innovation: 1⃣ Optimizer shreds your component into tiny granular pieces for hyper-optimized lazy loading (automatically!) 2⃣ Unique HTML serialization that enables your app to become interactive with 0 JS to start!

    1 replies 8 則轉推 50 個喜歡
    還原
  9. 已轉推
    1月13日

    What if you could edit components as JSON? You could: - create more rich tooling - visually create+edit for non-developers - deploy granularly (push one page w/o pushing others) that’s what we’re doing with Mitosis and , and it's getting really interesting

    16 replies 6 則轉推 63 個喜歡
    還原
  10. 1月13日

    . is innovative NOT in the way of how you code your app, but in how things happen under the hood. The end result is that streams portions of your app on an as-needed basis. Compare that to the current generation of FW that front-load the Javascript on page load.

    . is magical in requiring 0 hydration to load. But how? - Pure HTML is sent from the edge - User interaction hydrates components only as needed - JS is optionally prefetched in a worker
    3 replies 5 則轉推 29 個喜歡
    還原
  11. 1月12日

    Qwik Optimizer separates component code into: - initialization - rendering - listeners Level of granularity is not an island but individual operations. Rerendering a component does not force parent/children components to hydrate. Initialization runs on server => client.

    Why do we think is such a big deal? Because the cost of hydrating your app is very costly for performance and user experience, especially as your site/app grows Qwik solves this in a powerful new way, requiring 0 hydration to become interactive
    8 個喜歡
    還原
  12. 已轉推
    1月12日
    回覆給

    💯 - I spent years doing e-commerce sites, employing every perf trick in the book. But 100% of the sites I worked on were eventually ruined by 3rd parties. It was demoralising as a developer and made me ashamed to share my work with peers. Bravo for tackling this!

    2 則轉推 15 個喜歡
    還原
  13. 已轉推
    1月12日

    Why do we think Partytown is such a big deal? Because third party scripts are fighting your code for main thread resources, and your performance and user experience suffers Partyown solves this by offloading 3rd party scripts to a web worker in just a couple lines of code

    6 replies 31 則轉推 234 個喜歡
    顯示此對話串
    顯示此對話串
    還原
  14. 已轉推
    1月10日

    I am absolutely drooling over how is coming together - functional components with hooks (ala ) - mutable reactive state (ala /) - extreme performance (< 1kb JS to boot even the most complex site/app)

    6 replies 22 則轉推 119 個喜歡
    顯示此對話串
    顯示此對話串
    還原
  15. 1月6日

    I love working with and ! Nothing more fun than getting the 3 of us in the same room to discuss ideas. We all have different perspectives and ideas and approaches, and somewhere in the middle is magic! Thanks, for bringing us together!

    2 replies 1 則轉推 28 個喜歡
    還原
  16. 1月6日

    I ♥️ making things, ♥️ 3D printing, and ♥️ / , so I thought it would be cool to make it real! Check out the 3D model here:

    1 則轉推 12 個喜歡
    還原
  17. 1月6日

    I ♥️ making things, ♥️3D printing, and♥️, so over the holidays, I have made these for the team.

    2 replies 14 個喜歡
    還原
  18. 已轉推
    1月5日

    Honestly this is one of the most simple and magical ways to boost site perf in a couple lines of code, now available to the world to use!

    Toss the Confetti: Partytown is now in Beta 🎉 - Run third-party scripts from a web worker - Integrations for GTM and Facebook Pixel - Docs on how to integrate - Try it out and help us test!
    1 則轉推 6 個喜歡
    還原
  19. 已轉推
    1月5日

    Toss the Confetti: Partytown is now in Beta 🎉 - Run third-party scripts from a web worker - Integrations for GTM and Facebook Pixel - Docs on how to integrate - Try it out and help us test!

    3 replies 20 則轉推 91 個喜歡
    還原
  20. 已轉推
    1月5日

    And now we know the value that was causing the JSON.parse error

    5 replies 44 則轉推 246 個喜歡
    還原

@mhevery 尚未發表任何推文。

看來要一段時間讀取資料。

Twitter 可能已超出負載，或發生暫時性的小問題。請再試一次，或造訪 Twitter 狀態以取得更多資訊。

    你也可能也會喜歡

    ·