Devine Lu Linvega
The U and N in Uxn are silent, for people who were wondering.
Nov 17, 2022 at 1:06amWeb
Show threadDevine Lu LinvegaNov 17, 2022
Thanks to everyone who tuned in for the talk, it was fun to explain the process out loud for the first time.
Show threadTIMESCANNERNov 17, 2022
@neauoire I listened in. I enjoyed what I understood!
Show threadDevine Lu LinvegaNov 17, 2022
@TIMESCANNER glad to hear ^^
Show threadwakest likes your bugs ⁂Nov 17, 2022
@neauoire just finished watching it. was really lovely to hear your thoughts in your own voice as opposed to just text!
Show threadDevine Lu LinvegaNov 18, 2022
@liaizon cheers :)
Show threadnfgrepNov 18, 2022
@neauoire your talk was lovely! I’ve really enjoyed learning some of the motivations behind uxn. I plan to play around with it soon, would love to get it running on my GBA.
Show threadBad DiodeNov 18, 2022
@nfgrep let me know if you decide to test uxngba and if you have any issues with it :)
Show threadnfgrepNov 18, 2022
@bd yup, uxngba is what I’m going to try!
Show threadBad DiodeNov 18, 2022
@neauoire just watched on the archive! Really nice talk, well done :)
Show threadDevine Lu LinvegaNov 18, 2022
@bd cheers!
Show threadKototamaNov 18, 2022
@neauoire @bd I concur :-). The nerd in me got triggered by the "Lisp creates garbage" things though ;-).
Show threadVE0HAKNov 18, 2022
@kototama @neauoire @bd garbage by design made me chuckle too. Very nice talk!
Show threadDevine Lu LinvegaNov 18, 2022
@kototama @bd I made enemies all over, but to be fair, i also trash talked all the other languages too ;)
Show threadKototamaNov 18, 2022
@neauoire @bd i think it's a bit unfair since all languages creates "garbage" just some collect it automatically. But the term "garbage collection" and the concept comes from John Mc Carthy so its a bit funny also :-).
Show thread~ParnikkaporeNov 19, 2022
@kototama @neauoire @bd I'm pretty sure they meant "don't allocate more and more memory unless absolutely necessary", and set-c*r! isn't really part of idiomatic Lisp.
Show threadıƞıᵹєƞɑ // ɪɴꜰᴏᴛᴏхɪɴNov 17, 2022

@neauoire

/'x/ , got it.

Show threadHaelwenn /элвэн/ Nov 17, 2022
@neauoire And the x is pronounced /x/?
Show threadAlexander ShendiNov 17, 2022

@neauoire

Now I wonder if the X is also silent.

Show threadstyNov 17, 2022
@alexshendi The first rule of uxn is, you do not speak about uxn.
Show threadAlexander ShendiNov 17, 2022

@sty

Well I didn't, just about the X.

Show threadstyNov 17, 2022
@alexshendi the X is silent though, you can't talk about it
Show threadAlexander ShendiNov 17, 2022

@sty

Did you ever hear me talking about it?
Nobody has denied that it has a *written* representation?

#X

Show threadstyNov 18, 2022
@alexshendi shhhh, better be silent or they will hear you
Show threadAlexander ShendiNov 18, 2022

@sty

The X is silent, how can THEY hear me?

Show threadstyNov 18, 2022
@alexshendi oh yeah that's clever
Show threadThomasorusNov 17, 2022
@neauoire I refuse to acknowledge this information, it will always be hue ixe aine to me.
Show thread▼ Reimu Ukkorei (Cute-under-Ukraine) Nov 18, 2022
@thomasorus @neauoire Like axon but u instead of a.
Show thread~ParnikkaporeNov 19, 2022

@neauoire Just finished watching the talk; nice to hear about the motivations and journey behind uxn (which I had pronounced similarly to "oxen")!

I had been thinking about building a library tree for uxn, so that you can import slen, mcpy etc. and have them update whenever someone comes up with a better implementation. I'm pretty sure this would go against the "understand the stack" spirit of uxn though, so maybe I shouldn't do that?

Show threadDevine Lu LinvegaNov 19, 2022
@parnikkapore I think just having a complete collection of documented routines for people to copy-paste from would be a more useful thing maybe?
Show thread~ParnikkaporeNov 19, 2022

@neauoire That would be the uxn way of doing it, yeah.

"A complete collection of documented routines" is indeed the main value here. It's just that I'm imagining ~-importing the routines instead of copy-pasting them 

tbh I'm thinking about building higher and higher levels of abstraction on uxn (say, some kind of balanced tree); at which point being able to not see nor care about the routines at the bottom of the file becomes more and more important. But that might go against the spirit of uxn too so

Show threadDevine Lu LinvegaNov 19, 2022

@parnikkapore the "spirit of uxn" is what we choose to make it, there might be a level of abstraction that's more suited to deal with specific problems, and that would still be on message. :)

Have you seen this page? https://wiki.xxiivv.com/site/uxntal_library.html

XXIIVV — uxntal library

Show thread~ParnikkaporeNov 20, 2022

@neauoire I've seen it, and I would've included those in the tree as well 

This is a "collection of routines that people can copy-paste", right?

Show threadDevine Lu LinvegaNov 20, 2022
@parnikkapore exactly, I use those myself everyday across all my projects.
Show thread~ParnikkaporeNov 20, 2022
@neauoire And I used the snippets for writing my own stuff too 
Show threadDevine Lu LinvegaNov 20, 2022
@parnikkapore  awesome, if you wanna add something to that list until we collect those in something more practical to use, lemme know, I'll add 'em up