6 ms·
i'll reply in more detail later but for the moment i just want to clarify that i'm not za3k, although i've been collaborating with him; his priorities for the z
by kragen 2y ago
i'll reply in more detail later but for the moment i just want to clarify that i'm not za3k, although i've been collaborating with him; his priorities for the zorchpad are a bit different from my priorities for the zorzpad
you said:
> I think it's the primary use case like Java Applets and Flash preceded JS as iterations of sorta-portable and low efficiency tools which make up for it with sheer volume of high-familiarity material.
i wasn't able to parse this sentence. could you unpack it a bit?
you said:
> If you'd like, I can provide more specific suggestions.
yes, please! even if our priorities aren't exactly aligned i can surely learn a lot from you
- pushfoo 2y ago> 'll reply in more detail later np! I'll comment now in case it gets weird about a double-comment on the same parent by the same user. > > I think it's the primary use case like Java Applets and Flash preceded JS as iterations of sorta-portable and low efficiency tools which make up for it with sheer volume of high-familiarity material. > i wasn't able to parse this sentence. could you unpack it a bit? Software that doesn't care about being well-made or efficient. It doesn't matter because it's either fun or useful. > > If you'd like, I can provide more specific suggestions. > yes, please! even if our priorities aren't exactly aligned i can surely learn a lot from you This is a long topic, but some of it comes down to Decker[1] vs Octo[2]'s differences: * Decker can be used to make and share things that process data * The data itself can be exported and shared, including as gifs * Octo can't really, but it does predate the AI commnity's "character cards" by shoving game data into a "cartridge" gif * Octo has LISP Curse[3] issues I'm serious about the LISP curse thing. In addition to awful function pointers due to ISA limitations, everyone who likes Octo tends to implement their own emulator, tooling, etc and then eventually start down the path of compilers. I haven't gone that far yet, but I did implement a prototyping-oriented terminal library[4] for it. Since Gulrak's chiplet preprocessor[5] is so good, I didn't bother with writing my own. > i just want to clarify that i'm not za3k Ty for the reminder. On that note, the larger font sizes you brought up are seeming more important in this moment. I don't think I can deal with 4 x 6 fonts on tiny screens like I once could. HN's defaults are already small enough. [1]: https://github.com/JohnEarnest/Decker https://github.com/JohnEarnest/Decker [2]: https://github.com/JohnEarnest/Octo https://github.com/JohnEarnest/Octo [3]: https://winestockwebdesign.com/Essays/Lisp_Curse.html https://winestockwebdesign.com/Essays/Lisp_Curse.html [4]: https://github.com/pushfoo/octo-termlib https://github.com/pushfoo/octo-termlib [5]: https://github.com/gulrak/chiplet https://github.com/gulrak/chiplet
- kragen 2y agowith respect to software that doesn't need to be efficient, sure, there are lots of things that are usable without being efficient. but in rek and devine's notes on working offgrid, which are part of the background motivation for uxn/varvara, they say: > Computers are generally power-sucking vampires. Choosing different software, operating systems, or working from machines with a lower draw (ARM) or even throttling the CPU, are some of the many things we do to lower our power requirements. The way that software is built has a substantial impact on the power consumption of a system, it is shocking how cpu-intensive modern programs can be. so uxn/varvara is not intended for software that doesn't need to be efficient, very much the contrary. so, from my point of view, the fact that logic-intensive programs running in uxn consume 20× more energy than they need to is basically a mistake; rek and devine made choices in its design that keep it from meeting their own goals. which isn't to say it's valueless, just that it's possible to do 20× better what i mean by 'logic-intensive' is programs that spend most of their time running uxn code doing some kind of user-defined computation, like compilation, npc pathfinding, or numerical integration. if your program spends most of its cpu blitting sprites onto the screen, well, that's taken care of by the varvara code, and there's nothing in the varvara definition that requires that to be inefficient. but uxn itself is very hard to implement efficiently, which creates pressure to push more complexity into varvara, and varvara has ended up fairly complex and therefore more difficult than necessary to implement at all. and i think that's another failure of uxn/varvara to fulfill its own ideals. or anyway it does much worse according to its own ideals than a better design would how much complexity does varvara impose on you? in https://news.ycombinator.com/item?id=32219386 https://news.ycombinator.com/item?id=32219386 i said the uxn/varvara implementation for the nintendo ds is 5200 lines of c, so roughly speaking it's about 20× more complexity than uxn itself and that's what i mean by 'and it's not that simple'. in the comment i linked above, i pointed out that chifir (the first archival virtual machine good enough to criticize, which is a somewhat different purpose) took me 75 lines of c to implement, and adding graphical output to it with yeso required another 30 lines of code. you might reasonably wonder how much complexity i'm sweeping under the carpet of yeso, since surely some of those 5200 lines of code in the uxn/varvara implementation for the nintendo ds are imposed by the ds platform and not by varvara. the parts of yeso used by my chifir implementation compiled for x-windows are yeso.h, yeso-xlib.c, and yeso-pic.c, which total 518 lines of code according to either sloccount or cloc. still, uxn, even with varvara, is much better than anything else out there; like i said, it's the first effort in this direction that's good enough to criticize i don't understand what you mean about octo vs. decker but possibly that's because i haven't tried to use either one you definitely can't deal with a 4×6 font on the ls027b7dh01 display i'm using. it's 35mm tall, including the pixel-less borders, and 240 pixels tall. so 6 pixels is 0.88 mm, or a 2.5 point font. even young people and nearsighted people typically need a magnifier to read a 2.5 point font.
- kragen 2y agocorrection! > although i've been collaborating with him; his priorities for the zorchpad should be > although i've been collaborating with them; their priorities for the zorchpad