In my company I now have 3 browsers.

Chrome for company stuff that only works in Chrome.

Safari for company stuff that only works in Edge or Safari.

And Firefox for actual work.

🤡

Why do you subject yourself to DumpsterFireFox?

@iSwimInTheC To do actual work

@iSwimInTheC never had any issues with ff and it’s my favorite browser

I use LibreWolf for most things because it doesn't follow group policy so extensions aren't banned, Edge for things that require SSO and for debugging because it's the only one VS has good integration for, and Brave for YouTube and Messenger because Meta and Google sabotage their sites on Firefox-based browsers.

@lorentz holy crap! 😂

@Lensflare The UI tests are written for a proprietary selenium wrapper that only works with regular Firefox, but I don't have it because they also require a ton of other configuration so they live on one dedicated machine in the office and run once per day and before deployments.

@lorentz I don’t know about you but I'm kind of losing my trust in humanity when I encounter stuff that works in specific browsers only in 2025.

@Lensflare well, selenium also requires an external driver protocol which uses a combination of socket files and executables to work and at one point I think also supported DLLs using C ABI as a fallback, so it's annoying but not the least bit surprising that it doesn't work the same in every browser.

why the webdriver protocol isn't just a TCP protocol I will never understand.

LibreWolf FTW.

@lorentz youtube works perfectly for me on LibreWolf! I even have resistFingerprinting on.

@lorentz long live JS for loading a big ball of mutt so you cant just use an html parser to do shit. Back in the day I just wrote simple code to do test suite but due to often empty skeletons we are forced to use such annoying tools now. 🤡

@rootshell Yeah, actually, before server-side scripting you could just verify your static site visually, which was even easier. Clearly that was better, and new capabilities are inherently bad, because they have to be replicated in the testing environment.

@rootshell We're testing the correctness of features that were impossible to implement before JS.

@lorentz

I just hate the fact everything needs to be an "app" instead of a bloody website, we are forcing so much functionality in it with so much complexity that makes you question if it's needed.

But I think I'm becoming an old man yelling at the cloud. HTMX is starting to look much better, or maybe I go full back-end and checkout from the JS ecosphere atp.

@lorentz who using selenium 2025? Playwright or go home. The Ai driven version supports captcha solving out of the box. But it's very slow it has to. But I can look at that process for ages, it's so exciting. Recently I failed a captcha three times.

- Firefox,

- Waterfox,

- Opera,

- Opera GX,

- Vivaldi,

- Brave,

- Chrome,

- Comodo Dragon,

- Edge,

- Pale Moon.

Apart from Firefox && Opera, the rest are for some compat. testing.

@rootshell the only part of your criticism I don't get is why the technology and not the incentive is at fault for the abuse. At least JS can be combined with SSR via hydration. Flash, java applets, and VB extensions can't, they are just inherently poorly integrated, and before JS, developers just overused them instead. There is demand for this. The best we can do is make good practices easy with hybrid SSR frameworks.

@lorentz

I guess that is true.

Idk, I see whole ass websites with overly complex logic for what's essentially an webshop etc. I'm not saying the needs aren't valid, I'm just saying I see lots of website with overly complex front-end that needn't be so complex whilst still offering the same value.

@rootshell yeah, I think it's all just to secure billable hours and CV material for the dev.

@D-4got10-01 so you're purely using the old Firefox on snek to bully me? I'm stil on beach btw. It's getting quite dark.

@retoor Well... that was the work PC list.

Personal PC is as I had described it, so w/o updating OS... or rather buying a new one, can't really do anything about it.

But hey - at least I'm running the newest Firefox on Linux.

Hope you're having fun at the beach.

Apparently I have one some 3-4 h away from my location, but haven't felt the need to visit, yet.

@rootshell well, for what it's worth, webshops are actually not the easiest applications. There's a lot harder stuff, I know, but in many cases you're working on something easier then that. And ofc I'm not talking about deploying an pre-built webshop framework. But when I started programming it was common to write it from scratch within weeks. Those where the times stuff was still fun. It was like less testing, but I assure the quality wasn't worse. Bugs were less accepted back then and you were helt more responsible. Also, we did test manual very good in the end what appearantly beats the automated shit we have now. Just an observation. Work like I had, back in the like rakketakketak going batshit hard, I doubt if it still exists. It was SO MUCH BETTER. Would even vouch for the quality. Maybe it's not a good idea to rename all the vars because someone recommended it in a review what is very common. Just fuck you, I just tested, not worth it.