Comment by stephbook

1 day ago

Believe me, I try all the time. But HTML and CSS are not made for the modern web.

Styling radio buttons, working date inputs, forms that POST automatically, typeahead and server-side validation (eg username already taken.)

You spend all your time reinventing the wheel and then it's buggy and looks like a dog. To say nothing of the inevitable poly fills and Cross-Browser issues.

6 comments

stephbook

Reply
_heimdall  12 hours ago

How does this relate to Tailwind though?

Tailwind does ultimately compile down to CSS. Anything you can do in Tailwind can be done in CSS.

zelphirkalt  21 hours ago

I have not run into cross-browser differences in a long time. That is differences, that actually mattered and for which I would have had to build any workaround. I have built several websites recently, using vanilla HTML and CSS and solved everything using server-side rendering.

What problems specifically do you see with server-side rendering?

  • BrandoElFollito  19 hours ago

    From a security perspective I greatly prefer a client-server approach: you have an unsafe frontend where you care about ergonomy and aesthetics, and a backend which provides an API which handles the security.

    Two different worlds and often two different kinds of developpers

    • zelphirkalt  19 hours ago

      I think we actually don't disagree there, but we have a different understanding of the term "server-side". Anything related to security must happen on the server since safety measures in scripts running client-side can be defeated.

      1 reply →