[raxi]

~20 years ago there have been websites running on 8-bit chips consuming 400 bytes of ROM and 32 bytes of RAM (e.g. http://web.archive.org/web/20050601082859/http://www-ccs.cs...., an open-source clone: http://web.archive.org/web/20010109144200/http://www.chat.ru...)

A 32-bit CPU is very rich

[strags]

I remember that PIC project. I don't know if source was ever released, but I recall a lot of folks being very dubious about the claims made.

Quote: The PIC has 1024 words (12-bits) of program ROM, ~256 bytes contain a hand-crafted RFC1122-compliant implementation of TCP/IP including.

HTTP/1.0 and i2c eeprom Filesystem, using 3 to 99 instructions. TCP and UDP protocol stack, using 70 to 99 instructions. ICMP [supports upto ping -s 11], using upto 14 instructions. IP - Internet Protocol, v4, using 68 to 77 instructions. SLIP - Serial Line IP packetisation, about 76 inst Fully buffered UART, upto 115200 bps, using 38 to 56 instructions. Operating system: RTOS with Rate Monotonic Analysis, using 3 to 15 instructions.

[HelixEndeavor]

Well, given that the modern web has a lot more requirements for security to even permit most browsers to view a site, it makes sense that the base hardware needs have increased noticeably.

[raxi]

Exactly those PIC18 devices, still in production and on sale, w/o any changes during the years: http://utronix.se/

Of course, no https, but.. it is not a platform limitation, just an undemanded feature: how would you get a https cert for 192.168.0.1 or a similar intranet address where those device suppose to work? They are just not for cloud datacenters

[russdill]

There's a big difference between http and https

[hermannj314]

I'm not really sure I've drunk the kool-aid yet on why my static blog needs to be served securely over HTTPS.

Edit: wow. Some people are super sensitive about what ports I serve text on. Good luck to you all in life.

[Kevcmk]

You'd be a bad parent