I _really_ wish I'd read @kragen's https://dercuano.github.io/notes/forth-assembling.html before I built SubX.
I took a stab at reorganizing Mu's directory tree. It had gradually sprawled from old stuff at the top-level to new stuff in sub-directories. Now the top-level contains what I want people to see first, and build tools for each directory are in a sub-directory.
Building a disk image before: `./translate_mu_baremetal baremetal/life.mu`
After: `./translate life.mu`
Building an ELF binary before:
`cd linux; ./translate hello.mu`
Emacs/Org pipe dream
Idea I have not put enough thought into: adapting my workflows to lower-powered devices could mean finding/building some kind of Minimum Viable Org... Reducing Org and reducing Emacs to the absolute bare minimum.
Not just to make it lighter, but to focus it in a way. What are the essential primitives of a text-based outlining/writing/whatever-Org-is system?
If Plan 9 was an evolutionary step after Unix, what is *that* but for Org?
Have you cloned the Mu repo and tried to make sense of it? Do you have any suggestions for improving the directory organization? I'm starting to revisit it, so would appreciate any thoughts you have. (Even if this gets you to clone the repo for the first time.)
@ndpi Definitely on my mind a lot lately. I'm watching for PC-sized (i.e. more than a few KB of RAM) boards and curious to see what choices they make w.r.t. peripherals and firmware. I'm not an expert here.
I can scroll through the memory and change the code and sprites of the running computer.
I'm redrawing the cursor pointer sprites and various characters in memory.
``The m suffix means specifically a "pymalloc" build of Python, and it may mean that the ABI of 3.7 on your platform is not the same as the ABI of 3.7m. Extension modules must be built for the specific ABI in question. This means that 3.7 extension modules won't work with 3.7m and vice-versa.''
Sigh. I felt that it would not be easy.
I have not yet internally accepted the blatant in my opinion incompatibility 2.7 and 3.5, but here they have already come up with some letter modifiers :(
@xuv Working as designed! Slots in your OPML are cheap. What's expensive is your attention, and an unused feed uses none.
@syntacticsugarglider @dogstar @eris Restructurable feels like a realistic goal, but I'm not so sure about composable. Composable systems are few and far between. Forth is infinitely composable, but Forth programs I write are extremely unlikely to be composable.
Aiming simultaneously for ephemeral and infinitely composable is like wanting to have your cake and eat it too. A golden mean may be to start from a composable foundation -- but not build too high above it! Give others space to explore.
@dogstar mhm! the tough part is ideas and getting started, honestly. current hardware isn't built for throwing away the software stack at a moment's notice. it's too adapted to preconceptions.
Promiscuous dependencies are the root of all evil.
Merveilles is a community project aimed at the establishment of new ways of speaking, seeing and organizing information — A culture that seeks augmentation through the arts of engineering and design. A warm welcome to any like-minded people who feel these ideals resonate with them.