Live data from Hacker News

"Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

twitter.com

161–170 of 352 posts

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#161
post #91

Earlier quoted context omitted.

I don't understand why they don't just create a patreon/github sponsors/bitcoin donations for core ff/rust/mdn teams salaries and call it a day. I'm sure they'll get more than enough contributions to make it viable.

Who wants to donate when their CEO makes 2.5million/year?

I'm very glad that after I bought a VPN subscription from them they only needed to have sold another 49,999 or so to pay for that.

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#162

Earlier quoted context omitted.

Apple, Microsoft, and Google: * Forbid alternative browser engines on their platform. * Bundle their browser in a leading operating system. * Use their massive Web properties to drive downloads of their own browser.

And in the case of Apple, who killed Flash to help the open web, have knee-capped PWA support on their mobile platforms to force developers to leave their cut of sales through the App Store. It's pretty anti-competitive. I believe Valve's been a bit on edge (no pun intended), about Microsoft forcing games through their store as well. Mozilla was helping us out of these walled gardens. There's even the SSB support the…

It would seem even the Chrome Web Store is being met with frustration too

https://www.digitaltrends.com/computing/google-chrome-web-st...

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#163

Earlier quoted context omitted.

> At a Microsoft sized company I'd get it because they can basically blow billions on that sort of thing It also helps that Microsoft is in the business of selling IDEs.

Interesting question: why isn't Mozilla in this business too? They've got a cross-platform desktop app toolkit sat right there , and big enough developer mindshare to be interesting. There's room for a Firefox-flavour web dev IDE in the market, surely? Firefox dev tools, only with edit-in-place and live debugging for server-side assets. Seems odd to me that they've never gone that way, given everything else they've t…

Indeed.

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#164
post #142

Earlier quoted context omitted.

Why call it corporate speak, when it's plain old lying?

Being more charitable, it's possible they changed their minds, rather than they were lying.

It wasn't a change of mind. This was the layoff blog post. They just didn't mention it.

Tuesday blog post: "Wasmtime is our future!" "We're going to be smaller across the board".

Thursday it becomes apparent that the Wasmtime was laid off on that Tuesday.

"... specifically, a much smaller future ..."

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#165

Earlier quoted context omitted.

I learned Swift several years back, but didn't see myself using it until SwiftUI came to be. I have my fingers crossed for RustUI.

I use Pascal With Lazarus is has a cross platform Desktop GUI

Lazarus actually is impressive considering lack of the non-swift alternatives out there and that React Native still doesn't have desktop support. I'm glad you shared, because Pascal is a language I never looked into before, but it seems like it was ahead of its time, but I wonder if there are any modern dialects?

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#166

Earlier quoted context omitted.

> contribute a little back Clang was certainly an in-house Apple project from the start, and it would be hard to claim that it hasn't been a project that has seen huge uptake outside of Apple.

This is not entirely accurate. LLVM was started by Chris Lattner before he was hired by Apple, which were probably spooked by gcc going GPLv3 by then.

LLVM and Clang are both projects started by Chris Lattner, but they are not the same project.

Do you mean that Clang leverages LLVM on the back end?

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#167

Earlier quoted context omitted.

My wholly unqualified opinion as forever firefox user: They are going to push their VPN, Pocket and Lockwise like never before. They are also going to focus on their incubator hoping for a big win. Firefox the browser will start to stagnate, and in five years or so they'll switch to WebKit. The focus is now not the browser or the browser engine. It's selling Fix-the-Internet type products that have a dash of security…

I can't find where I read this, but I remember seeing some article about how Pocket was essentially dead, i.e. nobody's really working on it.

Good. The partnership with, acquisition of, and integration of Pocket was an embarrassment.

It was also an indication of just how bad Mozilla's management are at trying to make money. We'll see a lot more business theater like this before the team are replaces with people who know what they're doing.

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#168
post #71

Maybe, donating to Mozilla would be nice, instead of giving to Wikipedia or other projects that don't need more money.

Donations to Mozilla go to Mozilla Foundation, the non-profit organization. These layoffs are in Mozilla Corporation, which doesn’t get the donated money and is mainly funded by the partnership with Google for the search engine setting in Firefox.

The foundation can totally fund the corporation at their leisure, so I'm not sure where this idea is coming from. Money is fungible, and if the foundation thinks the best use is funding e.g. dev-tools, they can either direct money to the corporation or how engineers themselves. (Usually the latter)

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#169

Firefox doesn't have the developer tools that Chrome does so developers use Chrome to develop with meaning their websites work better in Chrome so Firefox is playing catch-up or just plain looks worse keeping adoption of Firefox lower. Mozilla solves the problem by killing development of developer tools insuring Firefox is an afterthought. Is there anyone in Mozilla management that has a technical bone in their body?

Interesting - while the FF dev tools are not perfect, I find the Chrome tools much much much worse. I remember a few months ago searching where the !#$@ one can see POST request parameters for a networks request (I'm sure they are there, because it's such a basic functionality, but it took me 10 minutes to finally give up and replicate a bug in FF, where I could debug without problems).

So maybe, as someone who never switched to Chrome, I am simply used to the way things work and unconsciously avoid the traps, while in Chrome I fall right into them? And probably others are simply used to Chrome dev tools?

Anyway, I hope they manage to turn the boat around and make it profitable, while keeping the browser alive and privacy-focused.

Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla

#170

Earlier quoted context omitted.

> contribute a little back Clang was certainly an in-house Apple project from the start, and it would be hard to claim that it hasn't been a project that has seen huge uptake outside of Apple.

This is not entirely accurate. LLVM was started by Chris Lattner before he was hired by Apple, which were probably spooked by gcc going GPLv3 by then.

Yes for LLVM, but Clang was made entirely while Chris Lattner was employed by Apple[1]. Before Clang you have to use LLVM GCC frontend (llvm-gcc) to compile C code under LLVM, which was the default in Xcode until 5.x (although Clang was added in Xcode 4.x, I remembered it being quite unstable at the time).

[1]: https://lists.llvm.org/pipermail/cfe-dev/2007-July/000000.ht... (announcement)

Post reply on HN