-
“In an ideal world, I believe a framework should go beyond developer experience value and provide concrete value for the people using our sites. Performance is just one part of that—accessibility and security both come to mind as well” timkadlec.com/remembers/2020-04-21-the-cost-of-javascript-frameworks/Permalink On twitter.com
❤️ 1 Favorite Mood 0
-
We’ve gotten all too comfortable with DX improvements negatively impacting UX. I’m so excited about a new gen of tools that do a lot more heavy lifting at compile time —like @sveltejs or CSS-in-JS approaches like 🍬Treat seek-oss.github.io/treat/ &👷♀️Compiled github.com/atlassian-labs/compiled-css-in-jsPermalink On twitter.com
-
I use emotion and styled-components in my personal projects, but in my professional career to date, it’s been options like CSS Modules, Vue’s built-in scoped CSS support, or even good old SCSS that has generally won out — introducing a run-time cost to users is a big trade-off.On twitter.com
-
CSS-in-JS wasn’t the main focus of the linked article — it just happens to have some excellent examples of tooling that achieves great things for both developer experience AND user experience AT BUILD TIME. I don’t have enough exp building with @sveltejs, but I like what I see!Permalink On twitter.com
-
Really hoping to see this trend continue over the next couple of years. Some FE Engineers will be concerned at increasing complexity, but for me this is where the “front of the FE” and “back of the FE” perspective is really useful. You don’t have to be an expert in everything!Permalink On twitter.com
-
Personally, I’m okay with the trade-off of increasing complexity in our build pipelines to improve the end-user experience. I’m much more comfortable with that then the opposite — negatively impacting the user experience to make things easier for developers 😔Permalink On twitter.com