top | item 44502457

(no title)

sprremix | 7 months ago

> All the functionality attached to Firefox's "Browser tools" sub-menu should be unceremoniously ripped out, banished to the developer's edition.

I hope this is some kind of sarcastic take I am not getting. What a weird thing to stand for.

discuss

order

Svip|7 months ago

Yes; it's obvious you include the full context:

> Did you know there's already a special developer's edition? No web designer is building on Firefox first any more. We're lucky if they even test on it. All the functionality attached to Firefox's "Browser tools" sub-menu should be unceremoniously ripped out, banished to the developer's edition.

Though, it would be more plain, if they wrote "could" instead of "should".

throw123xz|7 months ago

What's the benefit for Firefox and its users if dev tools are removed from stable Firefox and "banished" to the Developer Edition?

Dev tools are part of all browsers. Even Safari, which tries to keep things very simple, ships dev tools on the stable version. I really don't see the point in removing them.

eadmund|7 months ago

Why would anyone want to install another browser to use as a developer?

What the computing world needs is less separation of users and developers. Developers use programs all day, every day. And users should be able to write programs any time they wish. One of the most commonly used pieces of software in the world is a programming system: Excel.

One of my problems with iOS is the implicit assumption that users will not and should not extend the systems they use.

webstrand|7 months ago

What a strange take. I'm arguably a web designer, though its only one of many hats I wear. I design for Firefox first and then patch the places where chrome/safari break. If dev tools were only present on developer edition, which tracks the unreleased beta version, I wouldn't actually be able to test on Firefox that regular people are using.

Liquix|7 months ago

multiple people working on projects with web UIs at my org daily drive firefox. the author's arguments come off as hotheaded and poorly researched.

MrDresden|7 months ago

Even with the whole contex this did not read very clear to me.

kgwxd|7 months ago

As a developer who develops on Firefox, and only tests on other browsers just before deployment, I'd reconsider supporting it for end users if they're not going to be able to hit F12 to help me diagnose any issues that come up on their side.

bauble|7 months ago

It would be insanity. Even the most dedicated developers would switch to Chrome instantly.

JohnBooty|7 months ago

Well, that saved me a click on the article. This take is insane or a troll.

deathanatos|7 months ago

Some of TFA is more grounded. That particular paragraph though…

It exemplifies why beneficial change is so hard sometimes. The loudest voice in the room can go "here are the problems", we can all nod along in agreement, and then "and here's what we should do" … and it's just out there. I've seen this happen numerous times — borderline continuously — in politics.

Even ealier in the article, they (rightly, IMO) skewer Mozilla for laying off the Rust and Servo teams, but then TFA utterly undercuts its own thesis with,

> It shouldn't be trying to capitalize on [projects such as Rust or Servo].

What? What's the point of Rust, or Servo, then, if not to develop a better Firefox?