Inside a fast CSS engine

Re:Inside a fast CSS engine by taeric on Tuesday August 22, 2017 @02:57PM (#15075374)

I'm well aware of that. I also know that, in general, having to schedule things slows them down. If everything I'm running is trying to schedule something on my entire machine, it is giving my OS more work. Which will, by necessity, be harder to schedule and slow things down.

I'm not necessarily against all of this, but I'm also not eagerly embracing more crap to slow down my machine for no apparent reason.

[ Parent | on HN ]

Re:Inside a fast CSS engine by demarq on Tuesday August 22, 2017 @04:39PM (#15076160)

You are assuming that your OS scheduler is nearly at capacity, it isn't. And moreover your CPU is will spend most of it's life idle.

I could almost guarantee you this is not the bottleneck of any modern setup.

[ Parent | on HN ]

Re:Inside a fast CSS engine by taeric on Tuesday August 22, 2017 @05:58PM (#15076729)

I can guarantee you that I have jumped over to my browser when doing a compile that is definitely limited by my machine. I'm ok doing this knowing that I will only take up so much work on my machine. I do not go off and kick off another giant compile at the same time.

Now, if the browser becomes more and more consuming, hitting my browser could get closer and closer to kicking off another giant compile.

[ Parent | on HN ]