>nearly 2020
>this fucking thing still has screen tearing in linux
They deserved to lose to Google.
>>55564023
Yeah it is really horrible. But i just deal with it.
It doesn't though.
>>55564023
That would be the least of its problems
>nearly 2020
>it's still slow as fuck and chugs
Why would anyone use it over chrome,
chrome beats it in everything
>>55564158
Except not gobbling your ram, not being full of botnet, being customisable. Plus chrome is only faster because it pre-fetches the fuck out of everything.
Wow IE really is the best browser out there now who would have guessed
It doesn't. Sort your compositing manager out and make sure hardware acceleration is on. We are still using X server for christs sake, which is older than most of /g/.
>>55564023
it doesn't have sandboxing or ASLR
>>55564124
NO U
>>55564124
How do you make it not? I've fucked with every setting turned on/off hardware accel/smooth scrolling, etc.
It might sound trivial but it really makes it unusable.
>>55564181
Because botnet
>>55564023
Learn to Compton mah nigga
>>55564023
>turning on hardware acceleration still causes bugs
>glib turning your cpu into a housefire every time you save an image
i hate it but i use it anyway because i can be bothered to "sudo apt- get install chromium-browser"
>>55564267
What's the point of this? LIke Compiz? I use i3.
>>55564023
poorfag detected.
let's laugh at him for not having the money to buy a computer that is able to run a browser.
>nearly 2020
>using linux
>>55564338
You mean the kernel, desktop OS or android?
>>55564370
the browser
>>55564338
>nearly 2020
>not using linux
>>55564023
>nearly 2020
>Linux still has fucking screen tearing
They deserved to lose to Apple.
>>55564263
This is your compositor, it's nothing to do with firefox.
>>55564256
But it DOES have sandboxing :^)
I'd just like to interject for moment.
>>55564429
>>55564305
Not OP, but I have this issue on a $12,000 workstation.
>>55564237
Don't be an edgelord.
>>55564496
>$12,000 workstation
lel wut
>>55564496
Reading that makes me happy.
>>55564431
Just installed/ran compton to test it out and it still does it.
>>55564600
Sure you did
>>55564614
.. I did. Even tested some fag's config
http://pastebin.com/S8m1jnY3
and the only result is my screen looks worse.
>>55564633
what in the world
Yeah I'm not surprised it didn't work for you.
>>55564675
that was after vanilla. I don't know why you're being such an apologist for Firefox.
>>55564023
what gpu/drivers?
>>55564741
I don't know why you're the only person in the world who can't fix screen tearing with compton. So yeah, I'm calling bullshit.
I bet you are on Linux 16
>>55564748
nvidia 750 ti/whatever the most recent drivers from their site are
>>55564023
>he blames the browser not the terrible platform it runs on
works fine for me on windows and mac, OP. Sounds like you didn't compile something right.
>>55564972
Works fine on linux for me, sounds like OP is a fucking retard shill.
>>55564853
kek
>>55564023
In less time than it would take to find out what you're probably doing wrong. Not meaning to be insulting but it's just how things go. Install mint and run ff on that. You'll likely find works just fine.
>>55564023
I don't have tearing issues, but Firefox really became shit in the past few years. I think the code is too old or something. I was an advocate of using Firefox on Windows (since Chrome is best for Android), but I've switched to Chrome few years ago. Firefox is too shit these days.
>>55564741
what's your hardware
reminder of how firefox fags go into damage control of their shitty browser
>buy a better machine with at least 16GB RAM, i7 processor, and SSD
>16GB RAM
kek
>>55564023
>2016
>Still not a proper browser without memory leaks which is supported, maintained and has extensions.
>>55566899
>16 GB
>tfw u falled for it
>>55566948
you need 16GB of RAM because that's how much firefox uses
>>55564023
>only firefox
X is fucked up in it's entirety
I still remember the exact update firefox started lagging and being choppy. It was update 3.68 in 2009 or something
Youtube videos would pause for 4 seconds while the audio was still running, then continued, and then it happened again.
That's when I never went back to it
>>55567009
epic
>>55567021
epic? it was a disaster, I liked the monkey thing
>>55564023
>nearly 2020
no wonder they haven't fixed it, they have no hindsight.
>>55564023
Just wait for Mozilla Servo.
It beats Chrome in every way!
So what excuse is there to have screen tearing in the first place?
>>55567087
X11 has no way to prevent it.
>>55567193
So shitty software.
>>55567597
Use GNOME with Wayland.
>>55564181
>>55564263
>botnet
Why not use Chromium?
>>55564023
I use midori and icecat and have no problems but in windows I use firefox an seamonkey and they make me angry cause dont give 64 bits suport but edge does.
