Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fastly hires entire Wasmtime team from Mozilla

bytecodealliance.org

Post reply on HN
Print view View original

51–60 of 153 posts

Re: Fastly hires entire Wasmtime team from Mozilla

#51

Post by oefrha »

syrusakbary wrote: post #49
oefrha wrote: post #37

Earlier quoted context omitted.

Some context from that thread I find important (I’m a bystander not involved in any way): > We would need to work with a lawyer to determine the IP issues around this. It’s possible that just using the same policy as for the WebAssembly logo works, but I know that various organizations have grown more concerned about IP in this space since then. > This is in no small part because your company, Wasmer, attempted to re…

There is much more context to the "personal bias" statement than what is provided in the thread. But 100% agreed, it's essential to stay critical before making your mind on a given thing.

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 minutes ago”. That’s not cool.

Re: Fastly hires entire Wasmtime team from Mozilla

#52

Post by morty_s »

syrusakbary wrote: post #42
CJefferson wrote: post #36

Earlier quoted context omitted.

I'm replying here as a total independant, because you asked for a response :) Honestly, a logo for a project is both a huge thing, and a massive timesink. Your responses read that you just want to take over choosing the logo ("I'm happy to take on the responsibility of organizing it."). Then you seem to want to make this a whole issue encapsulating the problems with wasm (I am of course just reading one issue, not th…

Thanks for your response! Agreed that a logo is a not thing that should be taken lightly. Priorities in open-source communities are weighted differently by different members of it. We do care about accessibility, and the current logo have serious readability issues that affect disproportionally people with low-vision. IMHO a "welcoming" community should encourage improvements, rather than halting collaboration becaus…

>people with low-vision.

What does this mean? How does this relate to current logo? Is this a color blindness issue?

Re: Fastly hires entire Wasmtime team from Mozilla

#54

Post by [deleted] »

syrusakbary wrote: post #42
CJefferson wrote: post #36

Earlier quoted context omitted.

I'm replying here as a total independant, because you asked for a response :) Honestly, a logo for a project is both a huge thing, and a massive timesink. Your responses read that you just want to take over choosing the logo ("I'm happy to take on the responsibility of organizing it."). Then you seem to want to make this a whole issue encapsulating the problems with wasm (I am of course just reading one issue, not th…

Thanks for your response! Agreed that a logo is a not thing that should be taken lightly. Priorities in open-source communities are weighted differently by different members of it. We do care about accessibility, and the current logo have serious readability issues that affect disproportionally people with low-vision. IMHO a "welcoming" community should encourage improvements, rather than halting collaboration becaus…

[deleted]

Re: Fastly hires entire Wasmtime team from Mozilla

#55

Post by syrusakbary »

morty_s wrote: post #52
syrusakbary wrote: post #42

Earlier quoted context omitted.

Thanks for your response! Agreed that a logo is a not thing that should be taken lightly. Priorities in open-source communities are weighted differently by different members of it. We do care about accessibility, and the current logo have serious readability issues that affect disproportionally people with low-vision. IMHO a "welcoming" community should encourage improvements, rather than halting collaboration becaus…

>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

Re: Fastly hires entire Wasmtime team from Mozilla

#56

Post by marcinzm »

syrusakbary wrote: post #42
CJefferson wrote: post #36

Earlier quoted context omitted.

I'm replying here as a total independant, because you asked for a response :) Honestly, a logo for a project is both a huge thing, and a massive timesink. Your responses read that you just want to take over choosing the logo ("I'm happy to take on the responsibility of organizing it."). Then you seem to want to make this a whole issue encapsulating the problems with wasm (I am of course just reading one issue, not th…

Thanks for your response! Agreed that a logo is a not thing that should be taken lightly. Priorities in open-source communities are weighted differently by different members of it. We do care about accessibility, and the current logo have serious readability issues that affect disproportionally people with low-vision. IMHO a "welcoming" community should encourage improvements, rather than halting collaboration becaus…

They stated that a proper logo process would require too much of their time to devote to right now and they don't want a half-assed process. Also, to your proposal to manage the process, they clearly don't trust you after your company tried that trademark BS. So from their point of view anything you're involved with would actually require even more of their attention due to potential legal liability.

So it's not about not being a main member but rather about being basically seen as a bad actor to the community. Actions have consequences and the consequence for the trademark BS is being seen as an enemy of the community. The way to resolve that is to not annoy them about things while being as helpful as possible. Your comments on Github definitely are not that (they're adversarial, clearly annoy them with something they don't want to deal with, etc.) which simply cements their view of you being a bad actor.

edit: Your attitude is one I've seen before and it works in getting things from people who are forced to deal with you (service workers, employees, government officials, etc.). It does not work for people who can just walk away, block you or blacklist you since they will just do that.

Re: Fastly hires entire Wasmtime team from Mozilla

#58

Post by marcinzm »

PragmaticPulp wrote: post #17
ignoramous wrote: post #3

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…

In my experience, acqui-hires benefit the company far more than the employees who get moved to a different company. The first time I was acquihired, my compensation actually decreased because they kept my base salary and rewrote the bonus structure such that it was impossible to hit previous payouts. Meanwhile, my prior company received a large payment for the transfer of our team. Ironically, the new company was pay…

As I see it, there's no requirement for you to take the aqui-hire and it's on you to ensure you are fairly compensated (no one else). So take it, interview, get an outside offer and then quit. Or don't take it, get fired, interview and get an outside offer. An aqui-hire is an option and more options are always good as long as you remember that which option you take it solely up to you.

Re: Fastly hires entire Wasmtime team from Mozilla

#59

Post by syrusakbary »

oefrha wrote: post #51
syrusakbary wrote: post #49

Earlier quoted context omitted.

There is much more context to the "personal bias" statement than what is provided in the thread. But 100% agreed, it's essential to stay critical before making your mind on a given thing.

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 again.

Yeah, I know there is a spectrum of people that downvote my comments... and it's ok!

Re: Fastly hires entire Wasmtime team from Mozilla

#60

Post by marcinzm »

0xffff2 wrote: post #30
tpxl wrote: post #24

Earlier quoted context omitted.

In my opinion, the acquihire you went through was poorly implemented, and the pay reduction disrespectful.

That's somewhat irrelevant without data on what percentage of acquihires are poorly implemented.

Most aquihires are "take it" or "you're all unemployed." Since some money > no money the aquihire is inherently a benefit to the employee. You still have the option of not taking it and being unemployed. Or taking it and then looking for a new job. But you have more options and more income than if it didn't happen.
Post reply on HN