[05:35:05] *** Quits: wolfcore (~wolfcore@unaffiliated/wolfcore) (Ping timeout: 250 seconds) [05:41:44] *** Joins: wolfcore (~wolfcore@unaffiliated/wolfcore) [08:08:54] *** Quits: robbyoconnor (~wakawaka@guifications/user/r0bby) (Read error: Connection reset by peer) [08:09:26] *** Joins: robbyoconnor (~wakawaka@guifications/user/r0bby) [19:09:54] I'm lovin this 1945 thread going on rn [19:10:54] sivoais, remember telephone switches too [21:48:59] hah [21:49:03] yeah, relays [21:50:26] one of things that I keep telling people is that the people in the past weren't slow or anything. They were working at that pace because doing those things in the first place is hard. [21:50:42] and there really were tight limits on what they did [21:50:57] yup [21:51:16] we're spoiled with our huge RAM. Back then ... all they had was what fit in our registers. [21:51:28] and computer science, or really computing science, really *was* theoretical. [21:51:34] and punch cards [21:51:56] You had to *invent* recursion! You couldn't just say: "I want a language that looks like C." [21:52:02] Good luck parsing that! [21:52:02] lol yup [21:53:21] and only just over 10 years later, lisp comes along [21:53:47] but of course nothing stock was even capable of running it until fairly recently [21:54:33] the reason they used parens was because that was the *easiest* way to parse it. They wanted to write an algebraic notation (M-expressions) as well, but everyone started using S-expressions. [21:54:34] running it with today's performance expectations, that is [21:54:53] Yeah, they had to have special machines to run Lisp. Lisp on a home computer was a pipe-dream. [21:55:26] same with Prolog. Prolog used to have hardware specifically implementing a Prolog WAM. [23:01:33] *** Quits: robbyoconnor (~wakawaka@guifications/user/r0bby) (Ping timeout: 244 seconds) [23:14:37] *** Joins: robbyoconnor (~wakawaka@guifications/user/r0bby)