"Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
1–10 of 352 posts
Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#2Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#3Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#4Does anyone know what the consequences for this will be? WASM was what motivated me to learn Rust.
1 - https://github.com/bytecodealliance/wasmtime/graphs/contribu...
Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#5Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#6Does anyone know what the consequences for this will be? WASM was what motivated me to learn Rust.
Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#7Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#8Does Mozilla not make enough money to sustain long term investments?
Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#9Re: "Much" of the Rust/Wasmtime team hit by layoffs at Mozilla
#10Mozilla has decided to "throw the baby out with the bathwater" as a business strategy.
They should just focus on Chromium. It's going to win anyway. Mozilla has a small market share percentage and eventually the gap is going to be large enough they will have to abandon the FF code base anyway.
It's looking like they're going to focus more on the consumer market and building consumer products and less on infrastructure.
FF as needed back when all the browsers were proprietary.
Sure... Google can do evil things with Chrome but Chromium is Open Source - it can always be forked. There's nothing advantageous in maintaining FF as a dedicate code base. It's just duplication.
One of the major points of OSS is to prevent people from competing on things that are non-differentiating. If's OSS so they can fork it and make their own changes if they want.