54 replies

1. devolute 16 min later

   @zachleat This would be nice. Think of an unnecessarily obscure name for this approach and we might be on.

   1. Phil Sherry 27 min later

      @devolute @zachleat Spurtleclean? H/t @rich_harris

      https://home.social/@philsherry/110230958904146456

2. Zach Leatherman 17 min later

   Time to brand this method, y’all: what do you got?

   https://mastodon.social/@devolute/110374874708221432

   1. Matthias Ott 23 min later

      @zachleat BestPractices3

   2. Aaron Gustafson 26 min later

      @zachleat Making
      Adaptive
      Components
      &
      Creating
      Healthy
      Engineering
      Ecosystems
      Saves
      Everyone

      1. Zach Leatherman 38 min later

         @Aaron incredible

         my kids like it too

   3. Eric Eggert 28 min later

      @zachleat web4

   4. Bob Monsour 33 min later

      @zachleat Ummmmmm, WebC?

   5. Eric Portis 38 min later

      @zachleat The PaCStack (Pasteurized Components Stack)

      1. Zach Leatherman 40 min later

         @eeeps super PaC stack wait

         1. Eric Portis 52 min later

            @zachleat Good point, what about WebPaC—ok nope

            1. Zach Leatherman 56 min later

               @eeeps first of all, how dare you

      2. David McCormick 9 hr later

         @eeeps @zachleat UHTML

         1. Amelia Bellamy-Royds 22 hr later

            @dmc @eeeps @zachleat ⬆️ underrated comment

            (for anyone who doesn't get it: https://en.wikipedia.org/wiki/Ultra-high-temperature_processing)

            1. Eric Portis 23 hr later

               @AmeliaBR @dmc @zachleat wow TIL!

               1. Eric Portis 1 day later

                  @AmeliaBR @dmc @zachleat npm install a-web-component-with-no-dependencies

   6. Stuart Langridge 48 min later

      @zachleat It's a band and roadies model, isn't it? The band make something amazing and long-lasting, the performance and the music which is what people see and hear, but you also need the roadies who come along afterwards and plug everything in and scurry about invisibly backstage.

      1. ppk 🇪🇺 1 hr later

         @sil @zachleat Yes, I'd be fine with JS frameworks being called "roadies" from now on, doing their invisible DOM work backstage in support of the greater good.

   7. Christopher Kirk-Nielsen 57 min later

      @zachleat If you're not giving it a milk-adjacent name after that analogy… (Cross-Boundairy Component Development, or CBCD?)

      1. Zach Leatherman 59 min later

         @chriskirknielsen
         Whole Components
         2% Components
         Skim Components
         Lactose-free Components

         1. Elly Loel 6 hr later

            @zachleat @chriskirknielsen Or if you're extra hip:
            Oat Components
            Almond Components
            Soy Components

            1. Oliver 10 hr later

               @elly @zachleat @chriskirknielsen hola Components

   8. Nicolas Hoizey 1 hr later

      @zachleat WebC-4, an explosive new way to develop for the Web, difficult to master, not for the faint of heart.

   9. rem 1 hr later

      @zachleat "A Foundation Architect"

      Suitably wanky name for HR and bizdev to get excited about.

   10. Jon 1 hr later

       @zachleat 11x

   11. dan leatherman 1 hr later

       @zachleat base jumping

   12. Mike Aparicio 2 hr later

       @zachleat The peruvianidol Method. 😂

   13. Rustie 5 hr later

       @zachleat MinMax methodology. Minimum JS for what you are buildings. Learn to Maximise HTML and CSS for longer term reliability.

   14. Private reply 9 hr later
   15. tripleman, a 🇨🇦 in 🇩🇪 13 hr later

       @zachleat ShelfLife

   16. elle mundy 16 hr later

       @zachleat https://en.wikipedia.org/wiki/Progressive_enhancement 😎

   17. meduz' 17 hr later

       @zachleat My proposition for this: front-end development.

   18. Asbjørn Ulsberg 2 days later

       @zachleat Coincidentally, @slightlyoff recently linked to this blog post, which describes the method. As for a name? What about “Progressive Design System”?

       https://blog.almaer.com/building-a-modern-design-system-in-layers/

3. maxfenton 26 min later

   @zachleat Static-first

4. Stephanie Eckles 32 min later

   @zachleat yes pleeeasseeeee

   It's past time to value and promote IC who are uniquely skilled at this.

5. 👻 coogie 38 min later

   @zachleat Slow down there, Zach. If I do this, how am I going to rebuild my component library in `n` years?

   1. Zach Leatherman 39 min later

      @coogie *backs away slowly*

6. cthos 🐱 47 min later

   @zachleat I appreciate that you added the “unpasteurized” qualifier.

   1. Zach Leatherman 48 min later

      @cthos super pasteurized milk actually lasts a pretty long time 😎

      1. cthos 🐱 50 min later

         @zachleat I know! And it is shelf stable.

7. Cory 1 hr later

   @zachleat you're the gift that keeps on giving Zach

   1. Zach Leatherman 1 hr later

      @cory just between us I regifted this from myself

8. Charles Roper 1 hr later

   @zachleat Long-life components.

9. Ryan Mulligan 1 hr later

   @zachleat HTMilk and CookieSS, hi I would like to apply

10. motionsuggests 2 hr later

    @zachleat
    Call it Web Development 😉

11. Karl Oscar Weber 2 hr later

    @zachleat I’m currently going through this exact issue my current client. It’s All React and styled components, difficult to change any thing.

12. Mike-麥-Mai-v1.618 😎 4 hr later

    @zachleat Future Funk

13. catraxx 7 hr later

    @zachleat I keep saying this and it should be so easy to understand: CSS in JS means you are now tied to the framework. I still don't see the advantage either, it's two completely different things for me, they don't make sense together.

    Anyway. Yes.

14. Thomas Michael Semmler 10 hr later

    @zachleat I would love to. But how can we do that right now? How can we express components on a way that live natively on the web, as well as in spa flavored contexts?

    Everything I can come up with breaks as soon as a component relies on internal state management.

    1. Zach Leatherman 7 days later

       @nachtfunke maybe come up with a way to use a generic adapter for state management?

       1. Thomas Michael Semmler 8 days later

          @zachleat that sounds great, though I feel like it has been possible for a long time - or no? Here's where its apparent that I am just not too JS proficient to know these things :/

          I always thought though, that this topic is more about exploring why it hasn't been adapted by SPA flavours and Meta Framework companies who have a stake in lock-

          oh, hm...

          1. Zach Leatherman 8 days later

             @nachtfunke there is little incentive for framework authors to buy into this strategy, unfortunately 😬

15. Stephen Farrugia 10 hr later

    @zachleat bring back css specialists.

16. Kristoffer Lawson 2 days later

    @zachleat @autiomaa I feel #Javascript frameworks often just don't fit into my way of thinking, forcing me to code in their style, rather than my preferred solution for the issue. In addition they become bloated with layers upon layers.

    I built my own JS framework, #storkCore, to pretty much be the opposite of that. Slowly adding bits and pieces over the years.

    https://chiselapp.com/user/Setok/repository/storkCore/index

    Though I guess you could see that it, too, has its own philosophy. It fits my thought model, though.