The site positions itself as advocating for simplicity and minimalism in web development—stressing plain HTML, CSS, and JavaScript—but then pivots into building the entire project using React. That’s a contradiction.
If the goal is truly "plain vanilla web," introducing React (with its build tools, dependencies, and abstraction layers) runs counter to that ethos. A truly minimalist approach would skip frameworks entirely or at most use small, native JS modules.
So yes, it's philosophically inconsistent. Want to dig into a better alternative stack that sticks to that principle?
No, they don't. We know this already. And failing student on that basis is just a very quick path to losing lawsuits which will shortly eliminate this question as a serious concern.
Only below the 1000px breakpoint for tablets. Suggested videos probably keep people on the site/app longer than comments. They should have shown 5 videos with a "show more" drawer for the rest. But we know they care more about money than our happieness.
Radical suggestion. Don't make your lander taller than wide. I'm the first to assume that the science nerds have thought of everything and that my uneducated self has nothing to say about it. But then I saw the lander. It looks very tippable.
So then here's my luddite take. Can't they just unfurl wider stabilizers from the legs that increase their footprint? At slow speeds in low gravity it seems like they wouldn't need to be heavy or strong.
To me, CSS frameworks break the whole point of CSS, generally add a lot of bloat, and aren't useful except in some instances where rapid prototyping is needed.
Tailwind exists largely because programmers don't like CSS. We no longer need frameworks for compatibility. The era of browser testing is over. And we don't need them to do things CSS can't do, as in the past couple of years nearly all browsers are handling the newer features.
My big gripe is simply that it makes a lot of sense to keep your structure, styles, and scripts separated. If something looks off I don't want to have to wonder whether it's classes, CSS, or scripts.
And ultimately, I don't think Tailwind does make things faster. I could come up with custom CSS helper classes AS NEEDED, and avoid all the problems I mentioned above. And the one I didn't mention is that this makes your code look like incomprehensible garbage. Tailwind HTML files using BEM are just not OK.
Keeping my html and CSS separate make everything I do faster and lighter. Most importantly, CSS is now mature and finally does all the things for all the browser that make the frameworks just enough less useful that they become bloat.
My two cents. I'm sure Tailwind is helpful for many. But I gotta preach the basics.
"A small team of [hero] web developers conspired to kill IE6 from inside YouTube and got away with it [saving us all from eternal wackness]. - There, I fixed it for you. :)