Fastly hires entire Wasmtime team from Mozilla

Post by nanagojo » Tue, Oct 27, 2020, 8:36 AM UTC

hansjorg wrote: post #129

nanagojo wrote: post #124

Earlier quoted context omitted.

Contradicts their announcement on new product focus https://blog.mozilla.org/blog/2020/08/11/changing-world-chan... And here is a 2013 post about the "next generation" engine (Servo) https://blog.mozilla.org/blog/2013/04/03/mozilla-and-samsung... > So they cut teams that a) weren't directly working on their core browser and b) doesn't make money for spending on their browser. Exactly, that means they do not see any v…

Several parts of Servo have been incorporated into Firefox (Stylo, Webrender, Pathfinder and more). I think Servo was branded as a research project pretty early on. That it would replace Firefox wasn't very realistic.

Post by bryanrasmussen » Tue, Oct 27, 2020, 9:14 AM UTC

marcinzm wrote: post #58

PragmaticPulp wrote: post #17

Earlier quoted context omitted.

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.

Post by whizzter » Tue, Oct 27, 2020, 9:56 AM UTC

fwsgonzo wrote: post #39

whizzter wrote: post #28

Earlier quoted context omitted.

Had an idea of trying to "script" things for games, the idea was to use a the WASM backend of a regular C/C++ compiler to generate code that could be loaded dynamically and share structures (ignoring sandbox for this) so that testing could be done seamlessly, sadly WASM seems to be 32bit for the time being (atleast for Clang, dunno about GCC but that has other issues), also looked at Risc-V and missing export/import…

Sounds awesome. I have some abstractions for making interfacing easier, but I don't have any auto-generated structures. https://github.com/fwsGonzo/rvscript I have done that here. Example: APICALL(api_math_smoothstep) { auto [edge0, edge1, x] = machine.sysargs (); x = std::clamp((x - edge0) / (edge1 - edge0), 0.0f, 1.0f); machine.cpu.registers().getfl(10).set_float(x * x * (3 - 2 * x)); return 0; } "machine" is an ar…

Post by nullifidian » Tue, Oct 27, 2020, 10:02 AM UTC

xuejie wrote: post #77

nullifidian wrote: post #69

Earlier quoted context omitted.

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.

Post by singemonkey » Tue, Oct 27, 2020, 10:43 AM UTC

syrusakbary wrote: post #121

CyberRabbi wrote: post #108

Earlier quoted context omitted.

Just curious, why do you have such a strong interest in the WASI logo? That seems tangential to wasmer’s concerns.

We use the logo in the wapm website [1]. Using a non-accessible logo that is hard to read provides a non-ideal experience for our visitors, so we can't really use it unless it becomes more polished. This forced wapm to use a different WASI logo than the "official" one, which is also a non-ideal experience (it adds fragmentation). That's why we believe is just better to push all along a bit more polished logo. Is such…