2026/03/04

Newest at the top

2026-03-04 01:11:39 +0100 <geekosaur> and in Haskell in particular, with its rather finely diced syntax… put soemthing in the wrong place by accident and the error messages would resemble C++ template errors ☺
2026-03-04 01:11:21 +0100Tuplanolla(~Tuplanoll@88-114-89-88.elisa-laajakaista.fi) Tuplanolla
2026-03-04 01:11:04 +0100 <chromoblob> that's why i used parentheses
2026-03-04 01:10:25 +0100 <geekosaur> and do remember that code is written to be readable by humans, not the computer. if we cared about the computer reading it we'd still be keying programs in in hex
2026-03-04 01:09:55 +0100 <geekosaur> even with escapes it was really hard to deal with; without, well, I'm sure you could get a lexer to handle it but $* help the reader
2026-03-04 01:09:48 +0100 <yin> x `w `f` z` y
2026-03-04 01:09:46 +0100 <EvanR> "abc "def" ghi"
2026-03-04 01:09:16 +0100 <geekosaur> (well, with escapes)
2026-03-04 01:09:08 +0100 <geekosaur> because those _did_ nest
2026-03-04 01:08:56 +0100 <geekosaur> go look at why the Bourne shell's backrticks were replaced with `$()`
2026-03-04 01:08:54 +0100 <EvanR> lol
2026-03-04 01:08:46 +0100 <EvanR> imagine if strings could be nested without escaping the "
2026-03-04 01:08:05 +0100 <chromoblob> why would it be a nightmare?
2026-03-04 01:08:05 +0100 <int-e> x ◖infix◗ y
2026-03-04 01:07:37 +0100 <yin> whitespace as application would be great too
2026-03-04 01:06:42 +0100 <geekosaur> plan 9 user? 😛
2026-03-04 01:06:26 +0100 <yin> i wish `f` was just 'f or even `f would be fine
2026-03-04 01:06:17 +0100 <geekosaur> consider string parsing
2026-03-04 01:06:05 +0100 <geekosaur> if they'd chosen a different closing character it would have been easier
2026-03-04 01:05:50 +0100 <geekosaur> chromoblob: not gonna happen, nightmare to parse those nested backticks and in general backticked expressions
2026-03-04 01:04:53 +0100 <lambdabot> LowercaseLetter
2026-03-04 01:04:52 +0100 <geekosaur> > generalCategory '𝐱'
2026-03-04 01:04:45 +0100 <chromoblob> heh
2026-03-04 01:04:35 +0100 <yin> scared me for a moment
2026-03-04 01:04:22 +0100 <chromoblob> different o's
2026-03-04 01:04:15 +0100 <yin> what
2026-03-04 01:04:10 +0100 <chromoblob> lol
2026-03-04 01:03:53 +0100 <lambdabot> 7
2026-03-04 01:03:52 +0100 <int-e> > let (ο,o,о) = (1,2,3) in ο + o + о + ο
2026-03-04 01:03:19 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-03-04 01:02:50 +0100 <yin> . o O ( APL )
2026-03-04 01:02:47 +0100 <chromoblob> i'm still waiting for the syntax "a `(b `c` d)` e"...
2026-03-04 01:02:28 +0100 <EvanR> ok there was the soviet programming language
2026-03-04 01:02:19 +0100 <EvanR> whoever heard of a variable not latin or greek
2026-03-04 01:01:57 +0100Sgeo(~Sgeo@user/sgeo) Sgeo
2026-03-04 01:01:35 +0100 <chromoblob> cool...
2026-03-04 01:01:33 +0100 <EvanR> are supposed to look like xD
2026-03-04 01:01:28 +0100 <lambdabot> -6
2026-03-04 01:01:27 +0100 <chromoblob> > let x ☉ y = -(x * y) in 2 ☉ 3
2026-03-04 01:01:23 +0100 <EvanR> it's fine because obviously variables like x y and z
2026-03-04 01:01:17 +0100 <geekosaur> it's kinda stuck without constructors
2026-03-04 01:01:14 +0100 <lambdabot> OtherLetter
2026-03-04 01:01:13 +0100 <int-e> > generalCategory 'ꙮ'
2026-03-04 01:00:55 +0100 <EvanR> but then I guess chinese would be stuck without variables
2026-03-04 01:00:49 +0100 <lambdabot> OtherSymbol
2026-03-04 01:00:48 +0100 <chromoblob> > generalCategory '☉'
2026-03-04 00:59:45 +0100 <lambdabot> OtherLetter
2026-03-04 00:59:44 +0100 <geekosaur> > generalCategory 'ש'
2026-03-04 00:59:37 +0100 <EvanR> s/green/greek/
2026-03-04 00:59:31 +0100 <EvanR> if you write out some computer text containing latin, green, chinese, arabic, and hebrew, some of these scripts will appear "big" and some "small"... that's how it should've been divided between types, ctors and variables xD