News for hackers. Stuff that matters.
Re:Update on Mozilla WebThings by lloydatkinson on Monday September 21, 2020 @07:30AM (#24542085)
I have since removed my plan of using WebThings in my house, right after Mozilla started it's self imposed suicide starting with firing Firefox devs.
Re:Update on Mozilla WebThings by gostsamo on Monday September 21, 2020 @07:56AM (#24542255)
The strange thing is that as far as I get, Mozilla didn't fire a single ff dev. Servo - yes, mdn - yes, but they actually want to focus on FF and transfered people from the servo team to the core product.
Re:Update on Mozilla WebThings by calpaterson on Monday September 21, 2020 @09:02AM (#24542806)
My understanding was that some Firefox teams were cut.

https://arstechnica.com/information-technology/2020/08/firef...

Do you know different?

I also think that cuts to servo are de-facto cuts to Firefox as that browser was supposed to be the source of faster components.

Re:Update on Mozilla WebThings by gostsamo on Monday September 21, 2020 @09:39AM (#24543247)
They were not very clear on where the cuts are, but here is the quote from the linked article:

"In order to refocus the Firefox organization on core browser growth through differentiated user experiences, we are reducing investment in some areas such as developer tools, internal tooling, and platform feature development, and transitioning adjacent security/privacy products to our New Products and Operations team," Baker wrote.

The article prepends the paragraph with another sentence to impose its own interpretation on it, but the way I read it is that the browser division is reorganized around the user experience and everything else is moved in products and operations. Not sure how to highlight the words "browser growth".

Regarding Servo, the project is killed and part of the people had been kicked out, but the rest were merged with the core engine team. My understanding is that Mozilla decided that even Google is not doing two browser engines at the same time and decided to move the old one to rust the evolutionary way.

Did they fired someone from the ff team? Maybe, but I don't think that it is because the browser is no longer important for them. The fact that they moved there best rust devs to it testifies that at least they are not giving it up so far.

Re:Update on Mozilla WebThings by calpaterson on Monday September 21, 2020 @09:45AM (#24543321)
I agree completely that Mozilla have been (almost deliberately) unclear.

The article seems to be quoting from this:

https://blog.mozilla.org/wp-content/uploads/2020/08/Message-...

I think the sentence you've quoted makes it clear that cuts have happened to certain Firefox teams.

Now, we can argue about what the effect is of this cuts is but at least you have to accept that some Firefox teams have received cuts and likely those people have either been moved or dismissed.

When you say they moved their best Rust devs onto Firefox, yes but in part that is possible because they have made cuts to the Rust toolchain teams.

Re:Update on Mozilla WebThings by ptx on Monday September 21, 2020 @10:24AM (#24543841)
From their message, it's not clear to me how COVID-19 is to blame for the layoffs. Especially in Taiwan, since Taiwan has been among the best in the world[1] at handling the pandemic and is doing relatively well.

Did Google reduce their payments in the new search deal because people search less when they work remotely due to COVID-19?

Did Mozilla reduce investment in tooling because developers' need for tools is reduced by COVID-19?

[1] https://www.cdc.gov.tw/En

Re:Update on Mozilla WebThings by calpaterson on Monday September 21, 2020 @10:34AM (#24543953)
I think what they're referring to is that COVID has damaged the advertising industry from which Mozilla receive royalties but in fact the problem is much more likely to be that only a small minority continue to use Firefox.
Re:Update on Mozilla WebThings by gostsamo on Monday September 21, 2020 @10:12AM (#24543685)
The teams were downsized, but I'm not sure what happened to the people because it was bundled with the products and operations team. This is what I meant. Not a hill worth dying for though. It will be most clear if someone knows what the Taiwan office were doing because they were hit the hardest as far as I get.

Regarding the rust toolchain, all the FAANG are using rust one way or another. The project is healthy and Mozilla is not key there already. I'd even say that it would've been ugly if a non-profit corporation had to pay for the development of tools that trillion dollar companies are using.

Re:Update on Mozilla WebThings by dralley on Monday September 21, 2020 @09:19AM (#24542995)
The only parts of Servo that could realistically be ported into Gecko within the next couple of years have already been ported. Servo's DOM engine would be the last major remaining piece, but that would be a very, very long-term project.

According to your link, developer tools and internal tooling/infrastructure teams took a cut. The effects will mostly be indirect.

Re:Update on Mozilla WebThings by calpaterson on Monday September 21, 2020 @09:51AM (#24543420)
Internal tooling and infrastructure teams that work on Firefox are still Firefox teams though. If you work on the build pipeline you still count as a Firefox development in my book.
Re:Update on Mozilla WebThings by floatingatoll on Monday September 21, 2020 @11:04AM (#24544267)
Are DNS and email both components of the build pipeline, in your view?
Re:Update on Mozilla WebThings by benfrancis on Monday September 21, 2020 @07:51AM (#24542213)
Sorry to hear that and I'm very sad about the recent layoffs at Mozilla too, which included lots of people I know. What would convince you to give WebThings a second chance under its new management?
Re:Update on Mozilla WebThings by aesh2Xa1 on Monday September 21, 2020 @09:29AM (#24543123)
For me, what would do it is a complete product that is not niche. A Chromecast competitor that supports the big platforms and content providers out of the box (Android/iOS, Spotify/Netflix, Alexa/Google/Siri) would be ideal. This already exists in the Chromecast, except it's not open. Ideally, it'd just be software on a Raspberry Pi or any hardware.
Re:Update on Mozilla WebThings by benfrancis on Monday September 21, 2020 @09:44AM (#24543313)
Interesting. That's very different to what WebThings provides today but that's something I'd like to see too and have toyed with building in the past.

Chromecast was once very close to being an open platform by implementing the DIAL protocol (although DIAL also had some centralisation issues), but is now a proprietary platform built on the Google Cast protocol, and is creeping towards morphing back into Android TV.

There was once a project to build a Firefox OS based TV stick called Matchstick which could have been great (B2G is still used on current Panasonic smart TVs believe it or not), which unfortunately got embroiled in a debate regarding DRM and never made it to market.

The digital signage platform I'm currently building at Krellian (https://krellian.com) could be adapted to consumer use cases like Chromecast and I'd be interested in building that in a standards-based way (e.g. using the W3C Second Screen Protocol), but the challenge would always be getting support from the big content providers, and of course the issue of DRM.