OK so slashdot has now eaten two attempts to reply to you!
GAH!!!!! I'm really annoyed now, but not with you.
The 12F675 has more than 64 bytes of code: it has has 1KiWord of 14 bit memory for the program. It's very much a Harvard architecture, so there's a lot more than 64 bytes of code.
Pretty much all uCs run code straight out of NOR flash.
I'm using a TI CC2541, which has the usual slew of integrated peripherals, a 2.4GHz radio, 8k RAM, 128k ROM (optionally 256K, and room for external flash) and is a 32MHz single cycle 8051 core. It's quite capable and able to run an entire bluetooth stack on board. You could easily fit a TCP/IP stack in there if you wanted genuine internet access, too.
It's more than capable of operating a dimmable lamp for example (smart lamps are a classic IoT example). My device has a dimmable status LED as a minor feature, and the uC also operates some other hardware and does some DSP on board. 8k/128k is more than capable of an awful lot of control and logging functionality.
The BLE113 (a module using this chip) dev board operates a whole slew of hardware including buttons, a two line alphanumeric display, accelerometers, an altimeter and some other bits and bobs, and operates this while doing two way comms with another bluetooth device (either as the client or server).
By comparison the 32MB memory device is huge. I can't think of many IoT uses for such a device which don't involve driving a reasonably high definition screen with full colour graphics. Quake II ran happily on a P133 with 16MB of RAM, so I imagine the device for this OS is very much more than capable of such graphics.