zachleat/table-saw: A small web component for responsive `table` elements.
Now, this is how you design a web component. It’s a progressive enhancement.
Wrap your existing table element inside table-saw and it will behave responsively. If anything goes wrong with the JavaScript, the fallback is the regular table that’s already in your markup.
I just wish the installation didn’t assume that you’re using npm …it’s not really “zero dependency” if it depends on that.
Responses
Jason Garber
@zachleat Thanks for the merge! 🙌🏻
I know it was unsolicited, but I happened to be looking at both the project and Jeremy’s post and had a spare minute.
Related links
Lived experience
I hold this truth to be self-evident: the larger the abstraction layer a web developer uses on top of web standards, the shorter the shelf life of their codebase becomes, and the more they will feel the churn.
How Microsoft Edge Is Replacing React With Web Components - The New Stack
“And so what we did is we started looking at, internally, all of the places where we’re using web technology — so all of our internal web UIs — and realized that they were just really unacceptably slow.”
Why were they slow? The answer: React.
“We realized that our performance, especially on low-end machines, was really terrible — and that was because we had adopted this React framework, and we had used React in probably one of the worst ways possible.”
Printing music with CSS grid
Laying out sheet music with CSS grid—sounds extreme until you see it abstracted into a web component.
We need fluid and responsive music rendering for the web!
Cameron Dutro on ruby.social
Here’s the inside scoop on why Github is making a bizarre move from working web components to a legacy React stack.
Most of what I heard in favor of React was a) it’s got a good DX, b) it’s easy to hire for, and c) we only want to use it for a couple of features, not the entire website.
It’s all depressingly familiar, but it’s very weird to come across this kind of outdated thinking in 2023.
My personal prediction is that, eventually, the company (and many other companies) will realize how bad React is for most things, and abandon it. I guess we’ll see.
Web Components Will Outlive Your JavaScript Framework | jakelazaroff.com
There’s a cost to using dependencies. New versions are released, APIs change, and it takes time and effort to make sure your own code remains compatible with them. And the cost accumulates over time.
This post is about more than web components:
If we want our work to be accessible in five or ten or even 20 years, we need to use the web with no layers in between. For all its warts, the web has become the most resilient, portable, future-proof computing platform we’ve ever created — at least, if we build with that in mind.
Related posts
Trust
I’m trying to understand why developers would trust third-party code more than a native browser feature.
Making the Patterns Day website
The joy of getting hands-on with HTML and CSS.
Media queries with display-mode
I never would’ve known about the `display-mode` media feature if I hadn’t been writing about it.
Progressing the web
Don’t let the name distract you—progressive web apps are for everyone.
A web font strategy
How I’m prioritising performance when it comes to typography on The Session.