Gentoo compilations are peanuts compared to the massive energy sucking hype that A.I. is.
Their overall impact is low because they're niche. It wouldn't be if Gentoo were more popular. Imagine all of the AWS EC2 instances running Gentoo. And all of the Docker container builds still compiling glibc over and over.
Fact is they still built a horrifically inefficient system for deploying software. It's a crazy hypocritical stance to take. AI at least provides benefit - something that can't be said of Gentoo's waste.
When you have multiple Gentoo machines, you compile soft once and distribute it. You would be mad to compile everything every time.
Swing and a miss.
There is a distcc/d for having compile hosts with cache, which directly links to just a binary package host - essentially set up flags once, compile everything to your liking, and download within your network.
You've missed my main point by so much if you're explaining distcc to me.
Their overall impact is low because they're niche. It wouldn't be if Gentoo were more popular. Imagine all of the AWS EC2 instances running Gentoo. And all of the Docker container builds still compiling glibc over and over.
Fact is they still built a horrifically inefficient system for deploying software. It's a crazy hypocritical stance to take. AI at least provides benefit - something that can't be said of Gentoo's waste.
When you have multiple Gentoo machines, you compile soft once and distribute it. You would be mad to compile everything every time.
Swing and a miss.
There is a distcc/d for having compile hosts with cache, which directly links to just a binary package host - essentially set up flags once, compile everything to your liking, and download within your network.
You've missed my main point by so much if you're explaining distcc to me.