> That stress and the importance of the project were central to our struggles and the toxicity of the environment. Many design discussions became heated and two experts in their fields from competing corporations would fail to agree, convinced that their informed opinion was correct.
I work in the Wasm ecosystem, and I unfortunately also share this viewpoint.
I think that the toxicity from the beginning has transformed somehow the developers working on it for long and has leaked into other ways of managing disagreement within the Wasm ecosystem.
Before WebAssembly, I was working full time on GraphQL (a community that I deeply love and respect, where everyone was very friendly to each other) and I completely found myself lost when seeing how competing companies in the Wasm ecosystem, rather working towards collaboration paths, wanted to push each other down.
I have hopes though, that once things stabilize a bit, the ecosystem will recover :)
I work in the Wasm ecosystem, and I unfortunately also share this viewpoint. I think that the toxicity from the beginning has transformed somehow the developers working on it for long and has leaked into other ways of managing disagreement within the Wasm ecosystem.
Before WebAssembly, I was working full time on GraphQL (a community that I deeply love and respect, where everyone was very friendly to each other) and I completely found myself lost when seeing how competing companies in the Wasm ecosystem, rather working towards collaboration paths, wanted to push each other down. I have hopes though, that once things stabilize a bit, the ecosystem will recover :)