considering there has been various degrees of interest from time to time regarding the uxn(https://github.com/hundredrabbits/awesome-uxn) platform/language.
Would it make sense/ would there be interest in trying to do a "let's learn uxn" thing here? Probably following the compudanzas guide, going day by day, or so? this would have motivational benefits as well as giving a place and time with critical mass for posting questions, etc.
timing might be annoying, 1:1 matching of days might make it hard for too many to follow but too slow and there's a high chance of disinterest to grow over time

https://github.com/hundredrabbits/awesome-uxn dumb closing paren

is there any purpose to learning uxn over say forth?

is there a decent forth that's somewhat understandable to even start with?
I've looked into a few forths (the collapseOS one and color forth to name the ones i can remember off the top of my head)
but i wouldn't say the collapseOS one is 'easy' to get into. i mean spinning up a qemu instance isn't hard or anything, but eh.
some of the people online say the best way to learn forth is to implement a forth yourself in some other language. which... i mean.. i guess?

uxn is nice in that it has a defined way to deal with graphics, sound, etc. forth doesn't do that, you have to deal with that on system by system level, hope you got memory mapped screen buffers on the host system, or write a vga or god forbid an x11/wayland middlelayer. altho, I may be misinformed on the subject. like with lisp, forth is at it's most core, very small, but something like gforth (or commonlisp on the lisp side) adds a ton of extra stuff to make it possible to actually use it for "real tasks" but that means the words it adds may not (probably won't) exist on other forths.

Uxn is an interesting idea and to some degree also a good implementation, but the specifications are proprietary, littered with stupid drawings and the people, who make it, are insufferable. If the people making it were just a little bit less retarded the project would be a lot better.
>>4

some of the people online say the best way to learn forth is to implement a forth yourself in some other language. which... i mean.. i guess?

It depends on what you want to achieve. You won't be a good Forth (or Lisp/Scheme/any other minimalist language) programmer overnight, just because you understand how it works internally. It's a "the thing is more than the sum of its parts"-kind of situation, where you will be still lacking a lot of knowledge that can only be learned by doing programming in Forth and actually building stuff with it, rather than building a compiler/interpreter, which will teach you more about compiler architecture than programming.

Can anyone please fucking explain to me what the fuck UXN is & about?
I doon't get it
What the problem it does solve?
It does seem to me like an esoteric LARP/ARG ORG

uxn is a virtual machine inspired by 8 bit computers. the project includes: uxntal (the forth like "asmbly" language, analogous to 6502 asm); the "processor" architecture, analogous to 6502 processor; and the varvara "console" which includes virtual devices, analogous to the NES.
it was created to solve the problem of xcode being a nightmare for doing any programing work in settings with highly intermittent internet connections (specifically on a boat in the ocean), and provide a platform-independent programing framework (write once run anywhere).
varvara has been or is being ported to pretty much everything, mac, windows, linux, 9front, javascript, nintendo 64, etc. so any uxn program can run on all those. but unlike something like java it's small, so it's entirely possible to understand everything about it - a design goal of human scale.
anyway more than anything it's neat.

the idea of uxn sounds neat, but it seems oddly convoluted in some spots for general purpose use
but a spec that you understand intimately and could rebuild completely from your notes on an arbitrary platform is deeply appealing