Hacker News Reader

Hacker News

Comment by Jiocus | Hacker News Reader

Parent Full thread

Jiocus

What necessary E2E API does Chrome provide?

View on HN

WebRTC Insertable Streams: https://www.chromestatus.com/feature/6321945865879552

The state of it in Firefox:

"Opened Apr 2020"

https://github.com/mozilla/standards-positions/issues/330

Then in October added "Insertable streams is worth prototyping"

Also: "I will remind people that this isn't the place for advocating for what gets implemented in Firefox. This is something that the media team needs to work out."

then "closed 26 Oct 2020"

But, hey, it's June 2021, you just got a new UI redesign which nobody wanted (I guess, except the managers who invented it), and which uses up more vertical space. (Hint: about:config browser.proton.enabled false helps at the moment).

Even the iOS version of Firefox got an UI redesign. One has to care for the priorities! The color of the shed is always the biggest impact a manager can bring!

Do you really think the people who implemented UI changes are the same people who could implement an end-to-end encryption API?

Do you think people who implement ui changes are paid with same money as those who implement encryption api?

The most money are paid to the same managers in both cases. The total company expenses in the same period mostly aren't dependent on the nature of the changes implemented. The managers just make their managerial decisions what to set as the goals.

And apparently the board thumbs that up. That's the scope of the problem: "look we make the UI changes" is the "color of the shed" easy to understand illusion of "something" being done.

If there wasn't one manager at Mozilla who said to himself maybe in the pandemic with all the working from home stuff being done. Maybe we should look in our webrtc, video codec stack just is sad. No excuse that's just plain bad management.

Money is fungible, employees are not. Whether others at Mozilla may be tasked with implementing this API or Mozilla (or someone else) contracts Igalia to do it, the employees responsible for and qualified to work on UI are still going to get paid and will still have other work to do.

As far as I know Mozilla is not a foundation for charity towards unemployed developers. So their goal is not finding work for their existing employees, their goal is improving the browser in meaningful ways. They're free to lay off and hire people to do this.

Also honestly any developer worth keeping could figure out the task at hand given sufficient time. So to talk about developers as if there's a developer who can only alter the rendering of tabs and what not is kinda silly.

firefox has serious performance issues, i had to switch to chromium.

i really want to support firefox in my development but their tooling is just not presented in a rational footprint. when i inspect a vue proxy object, i dont want to see all the setters and getters.

they are losing mind share because neight to user facing components normthe dev facing have a well considered presentation or pefformancd

After Chrome's RAM guzzling architecture and Firefox' Rust rewrite promises, reading this is so disappointing.

more ram is s one time investment while poor feature presentation and buggy implementations are difuse issues.

if i can solve a slow experience with another stick of memory, thats of a lesser probldm

Reply on news.ycombinator.com