I got an idea: firefox is slow and bloated, eats up 100% CPU while browsing so why not use some small webkitgtk browser?
Sounds good for old thinkpad with 32 bit CPU, right?
Turns out, it has took already 8 hours to compile this fucken webkitgtk library. Browser itself should be small though when I get into compiling the browser.
>firefox is slow and bloated
source: your ass
why not try it yourself with 1GHz CPU smartass
get a real computer and stop using gentoo
Webpage scripting was a mistake, we should have stopped at linked hypertext markup language documents
>Firefox
I hope you're building from RAM with ccache, otherwise enjoy 8 more hours.
You must be really retarded OP. Why do you think firefox is slow and bloated? Might that be because of the webkit engine they use? Then why the fuck do you switch to a different webkit-based browser.
>8 hours
Nothing worth mentioning, my friend compiled just one package (of course, on a thinkpad) for more than 24 hours
I don't know what model it was, but it is certainly older than me (I'm 18)
>using extremely outdated hardware with up to date demanding software
>le bloat and slew
kill yourself homeless poorfag
ccache doesn't work for firefox, most of its parts now use rust.
Use chromium if you want to utilise ccache. It works
>old hardware slow
HUUURRRRRRRR
increasing insanity of extending web standards extinguished all alternative lightweight browsers
As Luke Smith once said, "A bloated web requires a bloated browser."
>eats up 100% CPU
kodi
pulseaudio
chromium
systemd
qbittorrent
please stop botnet and don't install it
>he fell for the gentoo meme
ok but really, it is
Well, you can kinda still use netsurf.
Gentoo has -bin packages for the browsers because actually they're bloat incarnate rather than Gentoo being a meme.
And if you need to compile these monstrosities regardless, it's not like that will be faster with a distro other than Gentoo.
>adding a bunch of crap that nobody cares or uses
>not the definition of bloat
My browsing experience is literally the same as it was 10 years ago
Building in RAM seems to be the biggest influence for Firefox in my experience.
Maybe it's changed since they've migrated a lot ot Rust. I have't built it in some time.
Used to build on tmpfs from the FreeBSD ports tree. With ccache and distcc at the time.
A tmpfs workspace saved the most time on compiles on my slow machine.
I think firefox 3.6 was the last version that ran decently on old hardware. If memory serves me right it was running fine on coppermine celeron.
use netsurf you worthless nigger cattle
>gentoo on a laptop without a server running distcc
How fucking stupid are you? Really.
>falling for the webkit meme
>hello world eats 1gb ram
>lol your hardware's shit for CURRENT YEAR Demanding(tm) Software
not even chrome with a couple tabs including youtube open eats 1GB ram
stop pulling shit out of your ass and buy a proper computer
>catch up to the times grandpa
>implying hardware is made for software
>implying software must require all available resources
>implying anyone who has any computer older than 5 minutes is a troglodite boomer living in the past
>what is cross compiling
>older than 5 minutes
>1GHz, probably one or two cores
pick one, faggot
you probably meant older than a decade
>t. not 18
Midori dropped Windows support and I'm sad.
>older than a decade is not older than 5 minutes
dang you got me
also checked
>implying webkit is in any way fast or light