Tailwind CSS: From Side-Project Byproduct to Multi-Million Dollar Business

Re:Tailwind CSS: From Side-Project Byproduct to Multi-Millio... by chrismorgan on Monday August 03, 2020 @03:04AM (#24034899)

FYI, URL routing is broken on that site: if you navigate to /free-themes directly (such as following a link), you end up at /, and can only access the right page by clicking the link in the navigation in a JS-enabled browser.

[ Parent | on HN ]

Re:Tailwind CSS: From Side-Project Byproduct to Multi-Millio... by taphangum on Monday August 03, 2020 @03:15AM (#24034957)

Have just edited the link for now. It seems that adding a closing '/' seems to fix the issue. But will look into the cause on the site.

Thanks for the heads up!

[ Parent | on HN ]

Re:Tailwind CSS: From Side-Project Byproduct to Multi-Millio... by z3t4 on Wednesday August 05, 2020 @03:59PM (#24064916)

The problem is that devs stopped doing semantic elements. Its now a div and span fest. The layout however has become more simple due to mobile/smartphones. But the front end complexity has become exponentially more complex. You save one day of work by using a bunch of frameworks, then you have to pay every time a user visits - with less conversions due to a slow site. And then you have to pay every time you make an update - due to the extra complexity. Then you regularly have to pay over and over again to keep the frameworks up to date.

[ Parent | on HN ]