home.social

#uxn — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #uxn, aggregated by home.social.

  1. @jason123santa o wow interesting handheld! it could probably run #uxn as it is a GBA clone?

    Tic80 has open source version and has less constraints. I love constraints but some pico8 ones feel to "fantasy" for me, which is why uxn is my sweet spot.

    pico8 apps are immediately distinguishable as being made in pico8 though.

  2. @jason123santa o wow interesting handheld! it could probably run #uxn as it is a GBA clone?

    Tic80 has open source version and has less constraints. I love constraints but some pico8 ones feel to "fantasy" for me, which is why uxn is my sweet spot.

    pico8 apps are immediately distinguishable as being made in pico8 though.

  3. @jason123santa o wow interesting handheld! it could probably run #uxn as it is a GBA clone?

    Tic80 has open source version and has less constraints. I love constraints but some pico8 ones feel to "fantasy" for me, which is why uxn is my sweet spot.

    pico8 apps are immediately distinguishable as being made in pico8 though.

  4. @jason123santa o wow interesting handheld! it could probably run #uxn as it is a GBA clone?

    Tic80 has open source version and has less constraints. I love constraints but some pico8 ones feel to "fantasy" for me, which is why uxn is my sweet spot.

    pico8 apps are immediately distinguishable as being made in pico8 though.

  5. @jason123santa o wow interesting handheld! it could probably run #uxn as it is a GBA clone?

    Tic80 has open source version and has less constraints. I love constraints but some pico8 ones feel to "fantasy" for me, which is why uxn is my sweet spot.

    pico8 apps are immediately distinguishable as being made in pico8 though.

  6. @almet
    Et si tu cherches de la stimulation intellectuelle en informatique sans se dire que ça va être utilisé pour concevoir des armes de guerre ou être exploité par les ia llm, il y a tout l'écosystème autour du #permacomputing qui a une réflexion globale qui n'est pas dans la fuite en avant comme la plupart des domaines en informatique :

    Exemple avec #uxn que j'aime particulièrement :
    General :
    100r.co/site/permacomputing_10
    100r.co/site/weathering_softwa
    Ecosystem:
    100r.co/site/uxn.html
    Virtualmachine:
    wiki.xxiivv.com/site/varvara.h

  7. @almet
    Et si tu cherches de la stimulation intellectuelle en informatique sans se dire que ça va être utilisé pour concevoir des armes de guerre ou être exploité par les ia llm, il y a tout l'écosystème autour du #permacomputing qui a une réflexion globale qui n'est pas dans la fuite en avant comme la plupart des domaines en informatique :

    Exemple avec #uxn que j'aime particulièrement :
    General :
    100r.co/site/permacomputing_10
    100r.co/site/weathering_softwa
    Ecosystem:
    100r.co/site/uxn.html
    Virtualmachine:
    wiki.xxiivv.com/site/varvara.h

  8. @almet
    Et si tu cherches de la stimulation intellectuelle en informatique sans se dire que ça va être utilisé pour concevoir des armes de guerre ou être exploité par les ia llm, il y a tout l'écosystème autour du #permacomputing qui a une réflexion globale qui n'est pas dans la fuite en avant comme la plupart des domaines en informatique :

    Exemple avec #uxn que j'aime particulièrement :
    General :
    100r.co/site/permacomputing_10
    100r.co/site/weathering_softwa
    Ecosystem:
    100r.co/site/uxn.html
    Virtualmachine:
    wiki.xxiivv.com/site/varvara.h

  9. @almet
    Et si tu cherches de la stimulation intellectuelle en informatique sans se dire que ça va être utilisé pour concevoir des armes de guerre ou être exploité par les ia llm, il y a tout l'écosystème autour du #permacomputing qui a une réflexion globale qui n'est pas dans la fuite en avant comme la plupart des domaines en informatique :

    Exemple avec #uxn que j'aime particulièrement :
    General :
    100r.co/site/permacomputing_10
    100r.co/site/weathering_softwa
    Ecosystem:
    100r.co/site/uxn.html
    Virtualmachine:
    wiki.xxiivv.com/site/varvara.h

  10. finally pivoting back towards deluge (sorry network device fans),
    i am reminded of just how messy it is…

    file includes all over the place! scope definitions based on file paths! method call shorthands! yuck :(

    there's some good ideas in there though, maybe i'll add a feature or two to my drifblim fork :D


    #uxn #uxntal
  11. finally pivoting back towards deluge (sorry network device fans),
    i am reminded of just how messy it is…

    file includes all over the place! scope definitions based on file paths! method call shorthands! yuck :(

    there's some good ideas in there though, maybe i'll add a feature or two to my drifblim fork :D


    #uxn #uxntal
  12. finally pivoting back towards deluge (sorry network device fans),
    i am reminded of just how messy it is…

    file includes all over the place! scope definitions based on file paths! method call shorthands! yuck :(

    there's some good ideas in there though, maybe i'll add a feature or two to my drifblim fork :D


    #uxn #uxntal
  13. I just now realized its been over a year since I've discovered #uxn , which indirectly got me on the path of joining merveilles and getting myself back into teaching :>

  14. I just now realized its been over a year since I've discovered #uxn , which indirectly got me on the path of joining merveilles and getting myself back into teaching :>

  15. I just now realized its been over a year since I've discovered #uxn , which indirectly got me on the path of joining merveilles and getting myself back into teaching :>

  16. I just now realized its been over a year since I've discovered #uxn , which indirectly got me on the path of joining merveilles and getting myself back into teaching :>

  17. I just now realized its been over a year since I've discovered #uxn , which indirectly got me on the path of joining merveilles and getting myself back into teaching :>

  18. I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.

    Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.

    It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.

    "Let's try to go slow, and fix things."

    Priceless.

    100r.ca/site/uxn.html

  19. I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.

    Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.

    It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.

    "Let's try to go slow, and fix things."

    Priceless.

    100r.ca/site/uxn.html

  20. I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.

    Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.

    It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.

    "Let's try to go slow, and fix things."

    Priceless.

    100r.ca/site/uxn.html

  21. I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.

    Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.

    It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.

    "Let's try to go slow, and fix things."

    Priceless.

    100r.ca/site/uxn.html

  22. I'm not gonna lie, #uxn is the cutest damned thing I've seen in a while.

    Someone made a custom portable virtual machine called the #Varvara and wrote code for that machine while following vintage design patterns.

    It can run on any platform, including the browser and is a machine agnostic system. You can make applications, desktops - and it isn't limited by traditional hardware constraints.

    "Let's try to go slow, and fix things."

    Priceless.

    100r.ca/site/uxn.html

  23. @[email protected]

    @neauoire may I propose: varvara touch input, as an extension of the mouse device

    additions:

    • one byte for touch id (0 means no touch i.e. mouse input)
    • one byte for touch pressure (>0 is down, 0 is up)

    xy coordinates will reuse that of mouse device

    as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)

    so if I use noodle with a touchscreen, it'll treat my touch input as the mouse

    but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!

    wdyt ^^


    #uxn #varvara
  24. @[email protected]

    @neauoire may I propose: varvara touch input, as an extension of the mouse device

    additions:

    • one byte for touch id (0 means no touch i.e. mouse input)
    • one byte for touch pressure (>0 is down, 0 is up) EDIT: upsize to short for better fidelity

    xy coordinates will reuse that of mouse device

    as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)

    so if I use noodle with a touchscreen, it'll treat my touch input as the mouse

    but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!

    wdyt ^^


    #uxn #varvara
  25. @[email protected]

    @neauoire may I propose: varvara touch input, as an extension of the mouse device

    additions:

    • one byte for touch id (0 means no touch i.e. mouse input)
    • one byte for touch pressure (>0 is down, 0 is up) EDIT: upsize to short for better fidelity

    xy coordinates will reuse that of mouse device

    as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)

    so if I use noodle with a touchscreen, it'll treat my touch input as the mouse

    but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!

    wdyt ^^


    #uxn #varvara
  26. @[email protected]

    @neauoire may I propose: varvara touch input, as an extension of the mouse device

    additions:

    • one byte for touch id (0 means no touch i.e. mouse input)
    • one byte for touch pressure (>0 is down, 0 is up) EDIT: upsize to short for better fidelity

    xy coordinates will reuse that of mouse device

    as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)

    so if I use noodle with a touchscreen, it'll treat my touch input as the mouse

    but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!

    wdyt ^^


    #uxn #varvara
  27. @[email protected]

    @neauoire may I propose: varvara touch input, as an extension of the mouse device

    additions:

    • one byte for touch id (0 means no touch i.e. mouse input)
    • one byte for touch pressure (>0 is down, 0 is up) EDIT: upsize to short for better fidelity

    xy coordinates will reuse that of mouse device

    as for pointer emulation, the varvara impl can fill in state/scrollx/scrolly as appropriate (e.g. one finger means leftclick, two finger means rightclick)

    so if I use noodle with a touchscreen, it'll treat my touch input as the mouse

    but if I use a rom that supports touch, it can detect touchid>0 and handle my touch input accordingly!

    wdyt ^^


    #uxn #varvara
  28. @d6 hello!

    I've been working with your audio examples and and studied the synching so I wonder if a different timer port could be considered for #uxn tty?

    As any other devices that needs timing depends on the screen device vector, or could fall back to 1 sec resolution with the time device.

    Another alternative could be to implement the Screen vector in uxntty, but just call it Timer or something like that.

    This would allow TUI games! :)

  29. @d6 hello!

    I've been working with your audio examples and and studied the synching so I wonder if a different timer port could be considered for #uxn tty?

    As any other devices that needs timing depends on the screen device vector, or could fall back to 1 sec resolution with the time device.

    Another alternative could be to implement the Screen vector in uxntty, but just call it Timer or something like that.

    This would allow TUI games! :)

  30. @d6 hello!

    I've been working with your audio examples and and studied the synching so I wonder if a different timer port could be considered for #uxn tty?

    As any other devices that needs timing depends on the screen device vector, or could fall back to 1 sec resolution with the time device.

    Another alternative could be to implement the Screen vector in uxntty, but just call it Timer or something like that.

    This would allow TUI games! :)

  31. @d6 hello!

    I've been working with your audio examples and and studied the synching so I wonder if a different timer port could be considered for #uxn tty?

    As any other devices that needs timing depends on the screen device vector, or could fall back to 1 sec resolution with the time device.

    Another alternative could be to implement the Screen vector in uxntty, but just call it Timer or something like that.

    This would allow TUI games! :)

  32. @d6 hello!

    I've been working with your audio examples and and studied the synching so I wonder if a different timer port could be considered for #uxn tty?

    As any other devices that needs timing depends on the screen device vector, or could fall back to 1 sec resolution with the time device.

    Another alternative could be to implement the Screen vector in uxntty, but just call it Timer or something like that.

    This would allow TUI games! :)

  33. Finaly trying to do something with the #uxn #varvara audio device.

    Thanks to @d6 for this awesome Tetris soundtrack example!

    git.phial.org/d6/nxu/src/branc

  34. Finaly trying to do something with the #uxn #varvara audio device.

    Thanks to @d6 for this awesome Tetris soundtrack example!

    git.phial.org/d6/nxu/src/branc

  35. Finaly trying to do something with the #uxn #varvara audio device.

    Thanks to @d6 for this awesome Tetris soundtrack example!

    git.phial.org/d6/nxu/src/branc

  36. Finaly trying to do something with the #uxn #varvara audio device.

    Thanks to @d6 for this awesome Tetris soundtrack example!

    git.phial.org/d6/nxu/src/branc

  37. Finaly trying to do something with the #uxn #varvara audio device.

    Thanks to @d6 for this awesome Tetris soundtrack example!

    git.phial.org/d6/nxu/src/branc

  38. @evgandr This really does seem like a key to unlocking Emacs. Once you understand that you can introspect any part of the API and mutate as you like at runtime, something sort of clicks.

    This is a big one for me with respect to the 'bloom' in the title. The idea is that you simply need to be aware of the 1 fact (that you can introspect the API effortlessly), then you have access to the full, beautiful universe of every function / variable / macro etc....

    I need to check out #uxn !

  39. @evgandr This really does seem like a key to unlocking Emacs. Once you understand that you can introspect any part of the API and mutate as you like at runtime, something sort of clicks.

    This is a big one for me with respect to the 'bloom' in the title. The idea is that you simply need to be aware of the 1 fact (that you can introspect the API effortlessly), then you have access to the full, beautiful universe of every function / variable / macro etc....

    I need to check out !

  40. @evgandr This really does seem like a key to unlocking Emacs. Once you understand that you can introspect any part of the API and mutate as you like at runtime, something sort of clicks.

    This is a big one for me with respect to the 'bloom' in the title. The idea is that you simply need to be aware of the 1 fact (that you can introspect the API effortlessly), then you have access to the full, beautiful universe of every function / variable / macro etc....

    I need to check out #uxn !