Having tried 10+ "IOT Frameworks," and still had to write our own because none of them managed to even boot on the most beefy MCU on the market without extra RAM.
Another example of something begging for a question "Do these people ever use their own software?"
Specific to the software discussed here: Bit weird criticism of software that obviously is not intended to run on end-devices with MCUs, but on a more powerful gateway. (But yes, there is overall too much focus on that part compared to the bits that run closer to the hardware)
The Web of Things direct integration pattern [1] (running a web server directly on a device) is not a good fit for MCUs, with a few very high end exceptions (e.g. ESP8266 and ESP32 for which the WebThings Framework works perfectly well).
For constrained devices like MCUs the gateway integration pattern is a better fit, which means using some other low power communications mechanism on the device itself and having a gateway bridge the device to the Internet and the Web of Things.
It's also within the charter of the Web Thing Protocol Community Group to explore a more lightweight CoAP+CBOR alternative to the default HTTP+JSON sub-protocol, which may help in some cases.
Another example of something begging for a question "Do these people ever use their own software?"