Firefox is not a “chrome alternative”. Firefox is a better browser. Even if we completely keep the chromium privacy out of question, Firefox is still faster and Firefox devtools are still waaaay superior.

I disabled javascript in my browser. Amount of shit loading to read shitty article is insane.

I opened chrome devtools and it was 300 requests and 10MB to read 500 words.

Another news portal 250 requests 7MB to see 300 words.

WTF ?

And they’re fighting with internet traffic by lowering movie quality ?

I just add I have pihole with lots of wildcard filters filtering half of internet and fucking adblocker and those numbers are after those filters.

Are you fucking out of your mind ?

Fucking hypocrites.

I can troll all day by opening Devtools on a browser and change <input type=“password“> to <input type=“text“> they think i hacked google, facebook and their email acoount

“Huddles don't work in safari 🤡,” Slack said.
Develop → User Agent → Google Chrome.
Boom, huddles suddenly work in Safari, and my today's huddle went absolutely fine.

Yep, I switched to Safari as my default browser. Previously, I didn't use it solely because YouTube's full-screen mode acted weird, but now I quit watching YouTube altogether.

Safari is a stellar browser. First, it wipes the floor with everything, even including Thorium, in the performance department (on Apple Silicon at least). Second, it's really beautiful with its new inline tab panel, where you have just one line of icons on top, instead of having two (tabs and url bar). DevTools are amazing. It can also connect to my iPhone's Safari via Wi-Fi and inspect the opened page — a must-have for heavy layouts. Plus, if my website works fine in Safari, it sure as hell will work fine everywhere. Safari is a great hack detector, as it won't tolerate dirty hacks. Works wonders for your code discipline.

One thing that's been pissing me off about browser devtools lately is that they hide certain requests, like 301s, pretending they didn't make it, but if I look at my Nginx log I see there was in fact a 301 sent. OMFG, I hate this, it has caused me many hours lost on debugging.

font-family expects a comma-separated list. Fonts haven't been displaying on my blog for months because of this issue.

Why could NONE of the browsers I tested this on give me a real syntax error instead of "invalid property value" which could mean literally anything.

Edit: Actually, why can't the CSS plugin for VSCode tell me that I'm making a syntax error in the value of a well-known property?