00:00:00 --- log: started forth/21.01.05
01:03:15 --- join: xek joined #forth
01:32:26 --- join: dave0 joined #forth
01:48:07 --- join: wineroots joined #forth
03:04:05 --- join: birdwing joined #forth
04:24:28 --- quit: xek (Remote host closed the connection)
04:24:52 --- join: xek joined #forth
04:38:58 --- quit: zolk3ri (Remote host closed the connection)
06:45:51 --- join: lispmacs joined #forth
06:54:02 --- quit: TangentDelta (Remote host closed the connection)
06:54:16 --- join: TangentDelta joined #forth
07:32:17 --- quit: birdwing (Ping timeout: 258 seconds)
07:50:22 <veltas> Is there an EFI bytecode forth?
07:59:49 <veltas> "https://members.uefi.org/events/EBC_Driver_Presentation.pdf" "JAVA and Forth - Rejected due to large libraries"
07:59:59 <veltas> That's a first lol
08:00:43 <veltas> EFI bytecode seems like a reasonable platform to write a forth on, then you can show intel how wrong they were
08:01:40 <patrickg> veltas: what they meant was "rejected because there's already an ecosystem that our partners had to compete in"
08:54:31 --- quit: dave0 (Quit: dave's not here)
11:03:10 --- join: WickedShell joined #forth
12:01:34 --- quit: spoofer (Quit: leaving)
12:16:16 --- join: spoofer joined #forth
12:32:12 --- quit: joe9 (Quit: joe9)
12:40:57 --- join: birdwing joined #forth
12:47:13 --- quit: birdwing (Ping timeout: 272 seconds)
12:58:11 --- quit: gravicappa (Ping timeout: 260 seconds)
13:00:29 <proteusguy> WTF?!?!? Forth too big?!?!? No wonder Intel is losing market share left & right.
13:04:30 <veltas> Also let's be honest, EFI and UEFI aren't exactly the smallest thing in the world
13:05:39 <veltas> CHAR16 annoys me no end, UEFI uses win32-style unicode everywhere but doesn't understand unicode
13:13:13 <proteusguy> Wow didn't know they were doing CHAR16 too... it is freaking windows.
13:40:55 --- quit: xek (Remote host closed the connection)
13:41:19 --- join: xek joined #forth
13:41:34 --- join: Zarutian_HTC joined #forth
14:16:38 --- join: joe9 joined #forth
15:03:06 --- join: dave0 joined #forth
15:07:45 --- quit: cantstanya (Ping timeout: 240 seconds)
15:12:12 --- join: cantstanya joined #forth
15:16:46 --- nick: jedb__ -> jedb
15:57:16 --- quit: Zarutian_HTC (Quit: Bye)
16:39:18 --- join: ptrkriz joined #forth
16:46:37 --- quit: dave0 (Quit: dave's not here)
17:38:35 --- quit: WickedShell (Remote host closed the connection)
18:43:34 --- join: boru` joined #forth
18:43:37 --- quit: boru (Disconnected by services)
18:43:39 --- nick: boru` -> boru
19:32:44 --- join: dave0 joined #forth
20:14:28 --- quit: sts-q (Ping timeout: 272 seconds)
20:22:37 --- join: sts-q joined #forth
20:39:13 --- quit: proteus-guy (Remote host closed the connection)
21:05:59 --- join: gravicappa joined #forth
22:15:09 --- quit: lispmacs (Remote host closed the connection)
22:21:04 --- join: lispmacs joined #forth
22:23:12 <siraben> Don't linux distros have a bootloader that runs Forth, or am I misremembering?
22:24:36 <siraben> Hm, they didn't give a reason why Forth libraries were large, my guess is that they're storing it as text and interpreting rather than compiling.
22:34:34 --- quit: Bahman (Remote host closed the connection)
23:59:59 --- log: ended forth/21.01.05