cross-posted from: https://lemm.ee/post/3376057
I held off on Windows 10 for as long as I could until my job required it. Now this nonsense. I hope this isn't the start of them joining on the web DRM bandwagon.
this post was submitted on 07 Aug 2023
1831 points (98.4% liked)
Firefox
17902 readers
23 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Nah, honestly I get this. They likely don’t let you run it in Safari either.
The problem is that each browser use different rendering and JavaScript engines. They all follow the same spec, but implement things differently, and at a different pace. Firefox tends to be really speedy with adding features.
Rendering is one thing, but for web apps the main issue is how they each implement JavaScript differently. Chromium uses the V8 engine, Safari uses JavaScriptCore, and Firefox uses SpiderMonkey.
Each one of these implementations handle certain JS features differently.
Array.prototype.sortis a good example.This means that when developing your application you need to keep track of what differences each browser has, and write/use polyfills or conditionals to ensure that your methods work as expected on all platforms.
This becomes cumbersome quickly, and easily leads to a messy code base and technical debt as the application grows.
It further complicates testing since you’ll need to test each release on each browser.
The easy cop-out solution is to just support a single platform, and direct people not on that platform to use the browser you’ve developed for.
The go-to choice there is obviously Chrome, since it has the most users. Photoshop Express is a free application developed with the hopes of hooking people onto buying a subscription. Thus they’d want as big a reach as possible. It would make no sense to develop for Firefox and push people to use that instead from a business perspective, most people wouldn’t just download a second browser just to use an app.
Edit: you can obviously spoof your user agent and bypass the check that way. Some features might be broken in Firefox though, and I wouldn’t expect a fix.
As a developer with 7+ years industry experience this is a very weak excuse to not support browsers.
Differences in features are usually down to bleeding edge stuff and I don't think your example of sort would apply because the end result is the same.
I know Adobe are more prone to using newer browser features but there really shouldn't be anything that's not simple enough to assure support across all browsers. Especially for a company as big as Adobe. It's inexcusable. We rarely have to use polyfills now, that was more a problem when I was starting out, mainly due to IE11 still holding out.
Sure, but it's a common excuse.
The company I work for doesn't test on anything other than Chrome because we have a relatively niche audience that uses corporate-provided computers, and Chrome is available on all machines. The app seems to work fine, but we don't spend any QA resources on it.
The last company I worked for was the same way, but with a little more diverse userbase. Testing on Firefox would increase our QA time, and very few customers cared, so we only supported Chrome. I would occasionally fix things for Firefox, so the app mostly worked fine, but at didn't spend any QA resources on it.
And so on. I'm guessing that's the case here as well. They don't want people complaining about things not working if it works fine on Chrome. Firefox may work fine, but they're not willing to spend QA resources proving it, and they don't want the support overhead from customers complaining if something doesn't work properly with Firefox.
Yeah sure, fine for the SME sized business and I've done it in the past for features like offline web behaviours (wasn't public facing). But tbh it's a shitty excuse even at that size and outright inexcusable for Adobe. I wouldn't get away with this at my current place which has significantly less resources than them. Don't make excuses for Adobe and it's a weak excuse at best.
I'm not making excuses, I'm describing what companies already do today. If they can get away with it, they just won't support multiple browsers.
If we had even one customer that used Firefox, I would be adamant that we support it at my company. But we don't. We know who our customers are because we're in a B2B relationship and we lock out everyone else (we make a niche product for a niche market in a niche industry; total users are in the hundreds).
Adobe doesn't have that excuse, but they have the brand recognition that people will go out of their way to use their products, so they can get away with not supporting Firefox. It's still stupid, but it's a viable strategy given their position in the market.
That's all I'm saying. I'm not saying it's good to target one browser, I'm saying it's practical, so a lot of companies do it. My response is to not use services that block me out, and to recommend alternatives to friends.