It’s to connect phone numbers to identities. Getting a physical sim in China involves going in person to a store where they keep your passport and a mugshot (you hold a paper with your number on it) in a database.
There’s no free WiFi without requiring a phone number. It allows the government to connect internet users to real identities.
Having things "just work" can be really appealing. I once had an issue where my Linux distro of choice was having a tough time with my monitor orientation. I got quite a few linux gurus involved and none could figure it out. I'm sure it eventually would have worked, but that's not an experience I'm particularly fond of.
And then software that does exist will often have bugs for Linux that are overlooked due to how small the market is.
Whenever I'm onboarded onto new codebases, I have a tough time finding my own debug logs when there are hundreds of logs from different systems all cluttering the terminal. It's hard to know where one log ends and another begins. It's just white text on a black background.
I started this a couple days ago, but it's already been useful for my work. After building it, I found out projects like this had already existed. There's a section on bottom of the readme comparing them.
I'm pretty sure he knows what Doordash is. I assume the thing that doesn't exist is ordering via a phone line, not an internet-based interface.
i.e. texting or calling a number in a specific way based on some standard tons of fast food places provide to make fast food orders without human interaction.
My previous understanding was that service would be stopped once you hit past the free tier.
Upon review, it does not look like this is the case. I have several very low traffic projects on which would have never been anywhere close to the free limit. However, if I get involved in a random spam attack, it seems I could be on the hook for several thousand dollars.
This is incredibly dangerous. Netlify is often used as a beginner friendly free tier for static hosting. Not as something that is cheap, but as something that is free. This is just an overall dangerous position to put people in.
I sunk a decent amount of time into WebAssembly over the past few months (I am the author of "watlings").
From my understanding, there are 3 answers here.
1. Most spaces do not need WASM. You don't necessarily see speed improvements since usually your JS and WASM (in the browser) are compiled into the same thing.
2. WASM is very good at bringing tools to new spaces. The biggest limitation here is in both tooling and education. It is not trivial to compile something like FFMPEG for the browser. Improvements to the WASI standard are helping here.
3. WASM is starting to see use in different spaces. For example, as a containerization format for efficient sandboxing.
Stackblitz did this with Node (aka their Web Containers).
You could make a new project very quickly and prototype an idea. When finished, download it off the browser and deploy it.