Gregory's ServerAlso, CSS is completely different than it was even 5 years ago. I feel like I'm relearning it quite literally. All of the syntax and constructs are familiar. So I'm not starting from scratch. But I wouldn't solve anything in CSS the same way we used to solve it 10 years ago. There are way better tools that are less hacky and more performant. But we're gonna have to learn them.
https://social.polotek.net/@polotek/113012077825811153
|
Top-level
 7 comments
This is not a small thing. It's actually huge. Because even as we convince people that the current path is the wrong one, we have to contend with what it costs to change course. It means real, hard business conversations about when and how to pay that cost. For the record, I believe bundle and minify are still best practices in my mind. But I do think there are significant details that can shift. I think we're talking more about what JavaScript we're delivering in the bundles. I don't have strong recommendations yet. This thread is me realizing that I don't. But I will say that @b0rk convinced me that esbuild is simple and has nice defaults.  @polotek If it helps, I highly recommend using lightweight CSS support frameworks. Something like bootstrap. It helps provide some initial structure and tools and a launching point without boxing you in.  @polotek A few years ago, a friend wrote that he didn’t feel he had twenty years of web design experience; rather, he felt like he had five years of experience, four times. I think about that a lot.  |
I suspect that getting off the treadmill also means committing to revisiting all of the development practices we've so painstakingly developed over the last 5-10 years. That's going to suck.
If I was putting my manager hat on, I would say that we need to see this as a choice invest in a better future state. Because what I'm realizing is that in the short term, this transition is probably going to feel slower and more costly than the status quo.