Live data from Hacker News

Fastly hires entire Wasmtime team from Mozilla

bytecodealliance.org

71–80 of 153 posts

Re: Fastly hires entire Wasmtime team from Mozilla

#71
post #51

Earlier quoted context omitted.

If there’s more context you’re certainly not communicating it very well and all we see is some company attempting to trademark something they neither invented nor owned and crying discrimination with little to no supporting evidence. Also, did you delete your downvoted comment then post the same thing in a new one? I saw your comment posted a while ago, in the gray, then when I refreshed before responding, bam, “0 mi…

No doubt. It clearly seems that I'm not communicating well enough. But just to be clear: is not in Wasmer intent to own the Wasm trademarks (as stated in the Github issue). And to answer your question: yes, I deleted the comment because I thought it was going to start a non-productive discussion (it had 1 point at the moment of deletion). Then I realized deleting could provoke some other issues, and decided to repost…

> But just to be clear: is not in Wasmer intent to own the Wasm trademarks (as stated in the Github issue).

Then why register?

Re: Fastly hires entire Wasmtime team from Mozilla

#72
post #68

Earlier quoted context omitted.

Is this a post from the 90s ? Who is working in a team worth acquihiring and then plans on being on unemployment benefits or has trouble finding a new job ? And I can't remember the last time someone asked about referrals ...

Anecdotally I have 5 years professional experience and every time I'm looking for work people have always asked for at least 1 referral

I've always been asked, too. And I'll ask as well.

Re: Fastly hires entire Wasmtime team from Mozilla

#73

Earlier quoted context omitted.

No doubt. It clearly seems that I'm not communicating well enough. But just to be clear: is not in Wasmer intent to own the Wasm trademarks (as stated in the Github issue). And to answer your question: yes, I deleted the comment because I thought it was going to start a non-productive discussion (it had 1 point at the moment of deletion). Then I realized deleting could provoke some other issues, and decided to repost…

> But just to be clear: is not in Wasmer intent to own the Wasm trademarks (as stated in the Github issue). Then why register?

"Our lawyers made us".

Lawyers can't make you do anything. They can advise. They can't act without your consent.

Re: Fastly hires entire Wasmtime team from Mozilla

#74
post #52

Earlier quoted context omitted.

>people with low-vision. What does this mean? How does this relate to current logo? Is this a color blindness issue?

There is a color accessibility issue with the current logo. I've explained it here: https://speakerdeck.com/syrusakbary/wasi-logo-proposal

It's a logo not a paragraph of text. The overall image is supposed to convey the brand and not just a piece of it. Even W3/WCAG agrees and logos are exempt from the contrast requirement. So your whole argument of citing WCAG is irrelevant as it explicitly doesn't apply to logos.

Re: Fastly hires entire Wasmtime team from Mozilla

#75
I'm out of the loop, I knew they were in trouble but Mozilla is carving up the talent pool?

I really wish we could come up with sustainable models for not for (much) profit tech companies that was beyond our current systems of volunteer and "strategic partnerships" (as in, it's a side effect of a larger business strategy).

Basically in this model, engineers would make maybe 80-160k. No options, no equity, no "going public". No fancy offices or amenities. Just a reasonable pay, a mission for the public good, and sincere dedicated people.

I've looked hard and searched for jobs like that. Maybe wikimedia and internet archive. But yeah, can't get my emails returned so maybe that's not who they are.

Re: Fastly hires entire Wasmtime team from Mozilla

#76

Earlier quoted context omitted.

No doubt. It clearly seems that I'm not communicating well enough. But just to be clear: is not in Wasmer intent to own the Wasm trademarks (as stated in the Github issue). And to answer your question: yes, I deleted the comment because I thought it was going to start a non-productive discussion (it had 1 point at the moment of deletion). Then I realized deleting could provoke some other issues, and decided to repost…

> But just to be clear: is not in Wasmer intent to own the Wasm trademarks (as stated in the Github issue). Then why register?

We registered the trademarks as part of other process that we were not super diligent with.

We also course-corrected as soon as we realized of it, much before it came public a few weeks ago.

Re: Fastly hires entire Wasmtime team from Mozilla

#77
post #8

Earlier quoted context omitted.

There's always RISC-V :) Nothing wrong with it, or anything preventing it to be just as fast. The only thing it doesn't have yet is a standardized vector-extension, but it's probably pretty close. We just need JIT support for an embeddable RISC-V emulator, and we're golden. Does it matter what the host language is these days server-side? I suppose there's a higher chance that the WebAssembly standard will adopt some…

RISC-V is from a significantly differing category. A category for WASM doesn't really exist yet, there is nothing else like this -- a relatively low level bytecode language with high-level features such as nominal types, garbage collection, modules.

IMO such a category existed for quite a long time, JVM and .NET all falls into this category. Yes WASM has its fame for becoming a browser standard, but fundamentally, there is very little difference between WASM and JVM.

Re: Fastly hires entire Wasmtime team from Mozilla

#78

I have mixed feelings about this. In one side, I'm happy that some of the people affected by the Mozilla layoffs have now secured a job. On the other side, now almost all the power of the WASI standard is concentrated into the Fastly corporation (with wider penetration thanks to the WASI integration in Rust). The main and only player of the Bytecode Alliance becomes Fastly as well (as Mozilla is out of the server-sid…

>The Bytecode Alliance has been biased since their inception, blocking any attempt of collaboration from Wasmer based on personal bias (I work at Wasmer) and other external entities out of their control

Their persona bias seems to be summarized as (from the github issue):

>The rejection from the Bytecode Alliance was based on a history of behavior that isn’t compatible with the BA codes of conduct—both the individual CoC and the organizational CoC.

Which seems a lot less like personal bias and a lot more like both you personally and your company have crossed too many lines to be considered good members of the community. Given your response was to lash out everywhere rather than take it as constructive criticism to grow with I suspect your behavior beforehand wasn't much better.

Re: Fastly hires entire Wasmtime team from Mozilla

#79

My money was on Cloudflare to have hired them wholesale. Regardless, congratulations to everyone involved! This deal has got me thinking... whether a right way to "lay-off" a supremely talented bunch is to actually see if other companies are willing to offer them jobs? Kind of how player transfers happen in Football (soccer). Either the team goes to the newer company wholesale or you help find your engineers suitable…

There's a lot of various anti-compete reasons why this doesn't happen. In most cases, the people most interested in hiring these people are competitors. I love the idea in theory, but in practice it's way too easy for companies to abuse in ways that are anti-employee.

Re: Fastly hires entire Wasmtime team from Mozilla

#80

Earlier quoted context omitted.

> But just to be clear: is not in Wasmer intent to own the Wasm trademarks (as stated in the Github issue). Then why register?

We registered the trademarks as part of other process that we were not super diligent with. We also course-corrected as soon as we realized of it, much before it came public a few weeks ago.

What other process?
Post reply on HN