> "Edge" refers to the fact the workload runs close to the customer either a few network hops away or on their browser.
But Wasmer Edge does not run close to most customers and does not run on their browser.
> Wasmer Edge are in an alpha release phase thus the edge network is kept purposely limited in this early pilot to take a careful approach to its expansion.
I think Edge is something where a limited pilot makes no sense. It would be like selling a database that is only available in the morning. If having very low latency is a key concern of mine then a service close to half my users is much less than half as useful as a service close to most of my users.
> Wasmer also have plans to build a hybrid environment between the browser itself and the edge network which will unlock some really exciting use cases thanks to WASIX.
If this isn't running in the browser than it has to be running in a server. By between the browser and the edge network I'm guessing you mean you'll purchase a large number of servers even closer to users than existing edge networks. That's hard, and your product so far doesn't suggest expertise in that area. I don't see how wasm will significantly help you get more servers closer to users than existing companies in this space.
> Ignore the troll reply... he is paid (or just sells himself for free) by the competition to discredit...
Based on your parenthesis I'm assuming that you don't actually know anything, you just assumed that because he's critical he's a troll?
> But Wasmer Edge does not run close to most customers and does not run on their browser.
It does run in the browser, that is what https://wasmer.sh uses to launch things published via the `wasmer publish` command. There are more plans to integrate these closer together into a hybrid system in the future with converged networking and transparent offloading work to servers, needs more work but its for sure possible with this foundation.
> I think Edge is something where a limited pilot makes no sense.
One does not just hit a button and servers appear everywhere in the world at once for free, all CDN's do the same thing, they run in racks of servwrs and expand their POP's based off real data and not just guess work. For instance, apparently Japan has a massive interest in WASIX, so perhaps the next POP should go there. Its also worth mentioning that if Wasmer Edge had been built on top of someone elses Edge (as others have done) then they would never be able to offer the cheap pricing.
> I think Edge is something where a limited pilot makes no sense.
It is a good point you make here about perception versus alpha relaity but with the architecture of the design and the huge amount of interest coming from the community the locations will expand quickly so it will be a growing pain of history fairly quickly.
> I don't see how wasm will significantly help you get more servers closer to users than existing companies in this space
No other company I am aware of are trying to build a distributed computer that lets developers write a program that runs in a hybrid setup of running in the literal browser of the user and connected to high performance compute in data centres. Honestly this is the bit that really excites me, imagine a program that runs in the browser but has real threads that also run in a data center. Exciting times.
But Wasmer Edge does not run close to most customers and does not run on their browser.
> Wasmer Edge are in an alpha release phase thus the edge network is kept purposely limited in this early pilot to take a careful approach to its expansion.
I think Edge is something where a limited pilot makes no sense. It would be like selling a database that is only available in the morning. If having very low latency is a key concern of mine then a service close to half my users is much less than half as useful as a service close to most of my users.
> Wasmer also have plans to build a hybrid environment between the browser itself and the edge network which will unlock some really exciting use cases thanks to WASIX.
If this isn't running in the browser than it has to be running in a server. By between the browser and the edge network I'm guessing you mean you'll purchase a large number of servers even closer to users than existing edge networks. That's hard, and your product so far doesn't suggest expertise in that area. I don't see how wasm will significantly help you get more servers closer to users than existing companies in this space.
> Ignore the troll reply... he is paid (or just sells himself for free) by the competition to discredit...
Based on your parenthesis I'm assuming that you don't actually know anything, you just assumed that because he's critical he's a troll?
> just downvote him.
Why don't you respond to their argument