Why TanStack Start is Ditching Adapters
Building a modern web framework is hard work. Users expect to be able to write functions that execute on the server, event listeners that run on the client, and components that can possibly render on both.
Itās kind of a crazy task when you consider that aside from finding what you believe to be the best developer experience, you have to spend an enormous amount of time trying to manage bundling the application and have it run across the ever growing list of JavaScript runtimes.
Tanner Linsley (the Tan in Tanstack) breaks down the architectural choices made during development of Tanstack Start, the new full stack framework with deep integrations with other Tanstack pieces like Tanstack Query (aka react-query) and Tanstack Router.
I think itās actually a beautiful time in the JS framework world. Weāre less concerned over warring and trying to grab market share, rather focused on building a base set of tools everyone can use to ease the rather complicated parts like web servers, bundling, environment deployment. Tanner gives some insight onto how he found success, give it a read!
https://tanstack.com/blog/why-tanstack-start-is-ditching-adapters
React Query API Design ā Lessons Learned
If you know me and this reading list, youāll know me and TKDodo are tight (he has no idea who i am). I love reading the writings of Dominik, the maintainer of React Query, so it follows Iād be very interested in a presentation by him.
Learning from other peopleās design choices is one of my favorite ways to learn. I want to hear about the tradeoffs they considered, the difficulties discovered along the way, needles threaded, features dropped. All of it. Publicizing those also shows grace, humility, and maturity. Those can sometimes be lost in the world of software where lines of code contain the hubris of the developers who keyed the characters into place.
So grab a snack and watch Dominik talk about the teamās API design, and the lessons theyāve learned over the past few years.
https://gitnation.com/contents/react-query-api-design-lessons-learned
Donāt Use aria-label on Static Text Elements
Iām not gonna sit here and pretend like I know how aria-label works and frankly neither should you because anecdotally I think thereās probably only a hundred or so developers in the world who really know how accessibility in HTML works. Iām not even talking about the whole ādiv-soupā thing where you just write everything as a <div> because why use many tags when few tag do trick.
The lack of understanding actually manifests itself sometimes as a misapplication or over-prescriptiveness of aria- attributes. Yes, over-prescriptiveness can be a real thing. In fact MDN is kind enough to even mention when you donāt need to apply certain attributes (as I learned recently with aria-posinset).
Misapplication is when you think youāre helping by labelling or attributing but are actually just making it worse. Itās not your fault! It may be your code, but I ā Asim Shamim ā say its not your fault. The rules are kinda confusing.
So join Ben, and see what he has to say about labeling static text! Maybe one of the sins he lists out are some youāll see in a frontend codebase near you.
https://benmyers.dev/blog/dont-use-aria-label-on-static-text-elements/