Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Is there too much CSS now?

css-tricks.com

Post reply on HN
Print view View original

121–125 of 125 posts

Re: Is there too much CSS now?

#121

Post by mumumu »

autoexec wrote: post #105
mumumu wrote: post #104

Earlier quoted context omitted.

In about:config you can enable or disable features individually. Recently they added ":modal" that will make paywalls harder to bypass. Most sites haven't implement yet, but I've already disabled this "feature" on config.

thanks for this! I've already got a huge list of changes I make in about:config on every install but it looks like it's time for an update

Every once and a while I have a look at the changelog of the FF dev. It is good way to find the flags to disable features and to have an idea how the web is changing overall.

The downside of cherry picking features is that your browser fingerprint becames pretty much unique.

Re: Is there too much CSS now?

#122

Post by Mikeb85 »

gbalduzzi wrote: post #118
Mikeb85 wrote: post #47

Nope. Flexbox makes it easy to just use plain CSS nowadays. No more SASS or any other preprocessor nonsense. Not even a fan of Tailwind (too much complexity for dubious benefit). CSS has never been better and now there's just the right amount of it. Also now that there's no more need for crazy JS hacks, you can have just a little bit of JS for interactivity and that's it. Front end development is finally pleasant aga…

Flexbox and grid are definitely not the point of the article though, it's all the newer things with much smaller use cases

Meh, still would rather have more features in CSS and supported by browsers so that's less that needs to be bundled in third party libraries...

Re: Is there too much CSS now?

#123

Post by kaba0 »

ghusbands wrote: post #119
naasking wrote: post #89

Earlier quoted context omitted.

Yes I know the difference, the point is that the original poster said CSS is faster because JS is interpreted. There is no way to intrepret that statement in a way that makes sense.

Sure there is - some people use interpreted to mean step-by-step, as in imperative. "CSS is faster because JS is imperative" is a charitable and correct reading.

But that is not correct, js is not interpreted/executed step-by-step in many cases (it is a bit more complicated, there are multiple interpreters and JIT compiler in the picture, it usually is started up by interpreting but then switched to JIT compiled native machine code).

The correct difference to make is the execution model, one being basically a Turing machine while the other is more similar to logic programming languages.

Re: Is there too much CSS now?

#124

Post by kaba0 »

ohCh6zos wrote: post #23

Yes, because the whole web has become infected with the server side dictating rendering for you instead of just delivering documents and letting the user render how they desire.

Yeah, I would definitely want to write a whole frontend for Facebook before being able to see my feed. But sure, I might as well read through a json response, how great that would be!

Re: Is there too much CSS now?

#125

Post by ohCh6zos »

kaba0 wrote: post #124
ohCh6zos wrote: post #23

Yes, because the whole web has become infected with the server side dictating rendering for you instead of just delivering documents and letting the user render how they desire.

Yeah, I would definitely want to write a whole frontend for Facebook before being able to see my feed. But sure, I might as well read through a json response, how great that would be!

That seems like a good deal compared to what we have now. That's effectively RSS without the syndication.
Post reply on HN