• Another interesting aspect of this retrospective: all the work was done in the open. You can go back and read all the issues and see the progress. If you’ve got @ZenhubHQ installed, you can even see how we broke down and tracked individual work items.

    • 2
    • 5
  • This is what my work on Vite Plugin Eleventy, Vite Plugin @PostHTML, and my (now scrapped) Vite Plugin Img were all building towards. Even some of the @workboxjs recipes work, too, was designed with these usecases in mind.

    • 0
    • 2
  • What started as an experiment over the summer finally just landed! We just finished migrating ChromeOS.dev to @vitejs_dev and @eleven_ty 1.0!

    Here’s a retrospective write-up on what we did and why we did it.

    chromeos.dev/en/posts/site-refactor-2022

    • 7
    • 50
  • @_developit I feel your pain; we had the same thing happen a month ago 😥

    • 0
    • 0
  • Actually, it’s worse than that. Trying to think how to calculate it by hand makes me uneasy, but I’ve got a real clear idea how to make a program to do it for me. My brain is literally pushing me to build a system to do it for me instead of just doing it. It’s very weird.

    • 0
    • 2
  • A really interesting consequence of me being a programmer at heart is me defaulting to building apps instead of doing things by hand. Right now, for instance, I’m building an app to calculate nutrition macros for me instead of just doing the math.

    • 0
    • 3
  • RT @jeffposnick: 📖 Preview the new @workboxjs docs! 📖

    It’s a walkthrough of everything you need to know before deploying to production, fr…

    • 0
    • 0
  • @patak_dev @ForSpareParts @workboxjs @vite_js @jeffposnick is the most likely person to know

    • 0
    • 1
  • @tropicadri Happy birthday!

    • 0
    • 1
  • Whoever is responsible for the Peacemaker opening credits should win every award.

    • 0
    • 0
  • In celebration of Eleventy hitting 1.0, I’ve updated my @vitejs_dev @eleven_ty plugin to 1.0 and moved it out of beta! Enjoy!

    npmjs.com/package/vite-plugin-eleventy eleven_ty/1480555290756059141

    • 2
    • 10
  • RT @AlphabetWorkers: Google relies on a 2 tiered workforce to deny the near majority of their workers the pay, benefits & rights they deser…

    • 0
    • 0
  • RT @AlphabetWorkers: All workers deserve the same level of treatment, pay, benefits & rights on the job for the work that they do.

    That i…

    • 0
    • 0
  • RT @eleven_ty: Official Eleventy v1.0 (stable) Release Notes:

    github.com/11ty/eleventy/releases/tag/v1.0.0

    Thank you to absolutely everyone in our lovely comm…

    • 0
    • 0
  • RT @smdiehl: This is the most basic argument against crypto that I tell all the people who call me. The tech doesn’t work, and the fundamen…

    • 0
    • 0
  • RT @GhosteTheDev: Sweet little co-operation between @TAbrodi @Snugug and me to get the section for mocking network requests with @vitest_de…

    • 0
    • 0
  • RT @passy: My favourite alternative phrase for Proof of Work is now “competitive coal burning”.

    • 0
    • 0
  • That said, thanks to @sveltejs and @vite_js, total download size to get to that homepage, including grabbing all the data to display it, is <400kb, which I’m going to call Good Enough™️ (most of that is Chart.js and Firebase deps)

    • 0
    • 0
  • Scatter chart is past 28 days of data, grouped by day, then grouped into two 14-day segments with an average for each group, and a description showing if it’s trending up or down.

    The ~140kb of JS was tough for me to include, but the data viz is already super useful, so it stays

    • 0
    • 0
  • This is what I’ve been doing w/the charting stuff; adding data viz to a little health PWA I’ve been building for myself. Donut charts, left to right, are below min, slightly above goal, above 2x goal, above goal, and within goal (water is blue, otherwise green). (1/2)

    • 0
    • 1
  • @jefrancomix @Firebase Thanks! I don’t think it’s that; I’m not getting that error. It’s not giving me any error, actually. just saying that there’s an error and it couldn’t deploy. I think it’s specifically an error updating to Node 16; redeploying w/Node 14 works.

    • 0
    • 0
  • Thanks for the rec’s all! Looks like Chart JS is the best right now, but building a line chart is still ~170kb of JS, which I don’t love. Chart CSS doesn’t appear to support code splitting r/n, and that’s 85KB of CSS, so I think I may need to go with JS.

    • 0
    • 0
  • Question for the web dev peeps: what’s a good, small, performance conscious graphing lib? Looking mainly for donut and scatter/line graphs. Animated not needed, willing to do CSS only, must be tree shakable if JS

    • 0
    • 2
  • @Firebase Are function deploys/us-central1 having problems? I’m trying to re-deploy functions onto Node 16, only change is engine/package-lock update, and getting errors trying to deploy.

    • 0
    • 1
  • RT @tmorello: Some of those that work forces apparently are indeed the same that burn crosses.

    • 0
    • 0