still easy enough to target, and with the added benefit of non-stop internecine wikipedia arguments + the marketing depts of these firms edit pages + potential lawsuits
Uber kept fares artificially low while simultaneously paying high bonuses to drivers to build a massive network. After burning through roughly $30+ billion over its first decade, Uber then pivoted its business model by raising rider fares, increasing restaurant fees on Uber Eats, and cutting driver pay.
There is a wat (s expression) syntax for the component model. The problem with the wat syntax for both Wasm and the component model is they’re a reflection of a binary format, and therefore are terrible for writing by hand. They’re designed to be written by tools, and the text format is just to help you understand the binary format.
I’ve written Wasm and component model wat extensively over the last decade to develop tests for Wasmtime, and even for an expert it’s a bad experience.
Wit syntax is easy to read and write by hand. There are high quality parsers that can transform it to and from the binary or wat format as needed, and code generators for a wide range of languages. It’s a way, way better experience in every way to deal with wit compared to the wat format.
Seconding this. Writing .wast files by hand is kind of fun as a novelty, but it's in no way something I'd want to maintain interfaces in.
Declarative interfaces via the WIT format are so much more readable in comparison; I'm really happy that's the direction we took for the component model.
reply