Libraries over browser features
Jeremy Keith has noticed a trend towards libraries over browser features, & I think I know why!
Insightful post from Jeremy Keith today, about how many web developers seem over-keen to pull in dependencies without much critical thought—especially when those dependencies don't offer anything above & beyond what features are already natively supported by the web platform (that is, the browser).
Browser compatibility is one of the underlying promises that libraries—especially the big ones that Jeremy references, like React and Bootstrap—make to developers. When I decide to rely on a JS framework or a utility library, I know that it's going to give me headaches when I come back to the project in 6 months. I know that every dependency incurs technical debt. But I do it because I'm on a budget and I can't spend my time reading through the caniuse.com page for
MutationObserver. Lodash promises cross-platform compatibility right there at the bottom its homepage.
This approach isn't a sustainable practice, and I'm trying to do as little of it as I can. Jeremy is right to be suspicious of third-party code. Cross-browser compatibility has gotten a lot better, and campaigns like Interop 2022 are doing a lot to reduce the burden. It's getting better, but the exasperated I-just-want-it-to-work mindset is tough to uninstall.
Linear is a beautiful app with a thoughtfully designed and powerful interface that I just can't find a use for.
GraphQL introduces a new layer on the client → database stack that makes HTTP status codes sorta irrelevant, and I'm not sure how I feel about that.