Hacker News Reader

Comment by andybak | Hacker News Reader

> Remix.run gives us the best of both worlds. Still writing your site predominately with JavaScript. [...]

This point is stated as if it's a widely accepted truth. Is that really the case?

I still labour under the misapprehension that one should aim to use as little javascript as possible.

Also, TFA praises Tailwind CSS as "solving CSS", and as great as it may be, I guess that statement lacks a bit of nuance.

I hear so many people recommend Tailwind but every time I look at examples it reminds me of an entry for the 17th Annual Esoteric Programming Language Competition.

Maybe you get used to it but hell it looks hard to parse visually.

Tailwind is definitely a Marmite framework (either you love it or you hate it). Yes it can be difficult to read. And it can be difficult to debug and fix something where you make a small change and it cascades 'upwards' somehow. But... the problems I have with Tailwind are no different to the ones I had with CSS and all the various magic methodologies that were supposed to "fix" css - things like BEM & SMACCS). But the big difference is that I can solve those problems in a fraction of the time with Tailwind. As a last resort you can just strip out all the classes of the elements in question and start over. If I had to do that with normal CSS, it would almost definitely break something somewhere else. With Tailwind, you are working in a highly localised area and can see everything you need on one screen. That, to me, is the power of Tailwind.

Yes. The true test of a CSS framework is how easily you can change it without breaking shit. I haven’t found a better solution than Tailwind in that regard. Emotion comes close but it also encourages you to componentize everything, which can cause change issues. In Tailwind I found my components disappear because I didn’t need them.

There's something about Tailwind (which I use, love, and evangelize to all who will listen and many who won't) that makes me think of the phrase "You can't fire me, I quit!"

All CSS is hard to parse visually.

Unless you follow very strict development guidelines, you do not really know anything unless you look at the computed styles in a debugging tool.

I think Tailwind does help wrangle some of that cognitive overhead with its naming system.

I kind of agree with the author that Tailwind is the best thing to happen to CSS. But yeah he definitely oversteps when he says that CSS is solved.

It most certainly is not a solved problem lol. UI still feels way fucking harder than it should, in all kinds of ways.

The advantages given in the CSS section are really around:

- utility classes

- theme system

Neither of which are unique to Tailwind (which is great in itself), yet the article paints it like it's the only thing out there solving for it.

TFA ?

https://www.urbandictionary.com/define.php?term=TFA

>I still labour under the misapprehension that one should aim to use as little javascript as possible.

Well, this is so 2005.

You say that like it's a bad thing?

I'm saying it in jest, but also as an observation. The TFA writer takes it for granted, but then again, so do many (most?) today.

Maybe that makes it even more important to repeatedly raise the possibility that this assumption is wrong.

Yeah, some JavaScrit can be nice, but if your website stops working with all javascript being blocked, you should probably make a native program instead.

This is particularly important so that web scrapers and other automated tools that the Web relies on can work. Also accessibility tools.

On the remix.run site it says

>Remix is a seamless server and browser runtime that provides snappy page loads and instant transitions by leveraging distributed systems and native browser features instead of clunky static builds. Built on the Web Fetch API (instead of Node) it can run anywhere.

I found no mention of the blockchain here or anywhere else. Why are they touting their own horn so much if they are clearly not Web3 ready?

Reply on news.ycombinator.com