Why is that so? Because there are enough crazy people who cannot stop writing new web standards. For example, things like Shadow DOM and web components, that are not really necessary and can be implemented using existing specs.
Why is that so? Because there are enough crazy people who cannot stop writing new web standards. For example, things like Shadow DOM and web components, that are not really necessary and can be implemented using existing specs.
What?
http://www.linuxfromscratch.org/blfs/view/cvs/xsoft/chromium...
Chromium comes in at 120 SBU, which while large isn't impossible. That comes to about 3-4 hours on my laptop.
Building software is not some esoteric pursuit only high priests can perform. It's good practice for software you're familiar with, require performance from and esoteric options most people don't care about.
Ninja, by default, sets the number of jobs to the number of available threads. If your machine is memory constrained, with regard to number of threads, you should reduce the number of jobs by passing the -j# switch to the ninja command below. Plan for roughly 1.25GB per thread while linking WebKit to avoid out of memory errors.
My laptop is memory constrained, I have yet to build Chromuium from source. How much RAM on your laptop? I've been looking for a laptop with 32GB RAM.
you should reduce the number of jobs by passing the -j# switch to the ninja command below.
I have had builds of linpack back in the day taking 24h+ on tiny systems. Again, building software isn't rocket science and you don't need super computers for it.
unit for compilation work relative to a reference package.