We’re just getting started. | The Spicy Web
Join a fabulous community of developers learning vanilla web specs like HTTP, HTML, CSS, JavaScript, & Web Components| The Spicy Web
Join a fabulous community of developers learning vanilla web specs like HTTP, HTML, CSS, JavaScript, & Web Components| The Spicy Web
I think the folks building Tailwind are talented and nice people. But at a pure technical level, I simply don’t like Tailwind. Whoever it was built for, it was not built for me.| The Spicy Web
Today I read Alex Russell's post The Market for Lemons and I found myself compelled to write a rebuttal. I am a big fan of Alex's work in general but not of this post in particular, which is very long, so allow me to attempt to summarize it: JavaScript-heavy single page apps (SPAs) are very popular The web is mobile-first and Android-dominated JavaScript-heavy apps do not perform well on mobile Android| seldo.com
A post by Zach Leatherman (zachleat)| Zach Leatherman
New web services are being built to a self-defeatingly low UX and performance standard, and existing experiences are now pervasively re-developed on unspeakably slow, JS-taxed stacks. At a business level, this is a disaster, raising the question: why are new teams buying into stacks that have failed so often before?| Infrequently Noted
On paper, Tailwind CSS sounds like a great idea. In reality, it suffers from the same problems that it tries to solve.| www.aleksandrhovhannisyan.com
While I love Tailwind for prototyping, I do not use it for production codebases. Where maintainability is key and there's time to document and enforce style workflow.| Shimin's Separate Concerns
