3 ms·
Coding... what? Coding on other retro technologies? I guess if you enjoy working on system software sure, but if I can't even allocate enough memory to hold a l
by Karrot_Kream 5y ago
Coding... what? Coding on other retro technologies? I guess if you enjoy working on system software sure, but if I can't even allocate enough memory to hold a large-ish JSON payload in memory, then I'm not going to be able to do much with the system. Only protocols like SMTP or NNTP are built around the ability to parse with minimal overhead (and even they can have large line lengths.)
- anthk 5y agoEh, wait a moment. I did several fun stuff with just CLI and C/tcl under the zipitz z2. Even with TLS. You understimate what we did in the 90's too with just 32 or 64MB of RAM. Jabber uses XML and I did it fine under a system daemon like Bitlbee AND an IRC client on top of that. 48MB overall on the Zipit z2, 32MB + compressed ZRAM. The total usage was about ~16MB with a tiny MUSL build, tmux, ash, bitlbee and sic. SMTP, NNTP, Gopher... are protocols for 16 and 8 bit architectured computers. Go figure. A Classic Mac with System 6 could do IMAP just fine, jcs wrote a client for it.
- Karrot_Kream 5y agoSure I'm not saying it's not possible. I did stuff in the 90s too. But usually you had to put a lot of effort into arena allocators and reusing pointers. Also lots of software then was pretty jank and would just segfault and errnos we're often not handled.
- bfuller 5y agoin the 90s i remember waiting 15-30 minutes to send an email. maybe revisiting some of these super low end devices would be worth it now that fiber is ubiquitous.
- anthk 5y agoThat's because of your ISP, not the client. You could send mail by telnet in less than a minute. If you meant early-mid 90's, that's true.
- anthk 5y agohttps://jcs.org/tagged/mac https://jcs.org/tagged/mac