The U and N in Uxn are silent, for people who were wondering.

@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?

@parnikkapore I think just having a complete collection of documented routines for people to copy-paste from would be a more useful thing maybe?

@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

@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

@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?

@parnikkapore exactly, I use those myself everyday across all my projects.
@neauoire And I used the snippets for writing my own stuff too 
@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