*Screenception*

Visualizing programs with side-effects in a postfix shell with a live-updating text-mode environment. Built all the way up from machine code without any dependencies (except an x86 processor and Linux kernel).

archive.org/details/akkartik-2

Project page: github.com/akkartik/mu

More context: mastodon.social/@akkartik/1048

*Editing functions in the Mu shell*

archive.org/details/akkartik-2

Long delay since my last video. Printing floating-point numbers is *really* hard. I'm still half-assing it.

As a follow-up to merveilles.town/@akkartik/1053, I'm tightening focus to two threads:

a) These Mu shell experiments, and
b) An extremely skeletal OS to drop the Linux kernel dependency.

Deprioritized for now:
a) Other processors: RISCV, ARM, RPi, etc.
b) Graphics, mouse, etc. Device priorities for the OS are disk then ethernet.

*Towards running Mu without Linux*

All Mu really needs so far is to print to screen and read from the keyboard. Here's a 2-minute video about achieving that:

archive.org/details/akkartik-2

It seems such a small thing. But I needed lots of help, as you can see from the additions to my credits: github.com/akkartik/mu/compare

Merry Christmas to all! What a beautiful world.

Project page: github.com/akkartik/mu

More context: mastodon.social/@akkartik/1048

*Switching gears to pure graphics*

Until now Mu has followed classic Unix: stdin, stdout, pure text mode.

But giving up an OS kernel requires controlling the screen myself. Which requires various complicated probing for hardware. Then programs handling various screen sizes.

Easier: just always assume some common graphics mode. Say 1024x768 with 256 colors.

Interestingly, the default palette has far fewer than 256 colors. (Pic: 1024 cols each contain color `col%256`.)

akkartik.github.io/mu/html/bar

*2020: Flood-filling the Mu computer*

A year ago I had a prototype of a C-level programming language mapping 1:1 to Assembly that I _thought_ could be type-safe.

Since then, I:

* wrote an academic paper on it
* made it type-safe
* began a high-level language atop it
* got into video, with 15 2-minute screencasts
* and ran programs written in it on bare metal, without an OS, like, 5 years before I expected to.

❀️ to everyone who inspired, taught, debated, encouraged.

github.com/akkartik/mu

Follow

*Rendering text atop baremetal*

Mu can now render text atop baremetal x86.

Try clicking around from akkartik.github.io/mu/html/bar

The boot-up machine code reads a few sectors from disk, configures a keyboard handler, and loads a bitmap font (2KB for ASCII, with the option for more).

I use GNU Unifont. I believe that means Mu is now GPL v2. So stated. IANAL and I try not to think about software IP. But a font? Copyright seems reasonable there.

Next up: a text editor!

github.com/akkartik/mu

Β· Β· Web Β· 4 Β· 5 Β· 16

*A more international interface for rendering text*

New 2-minute video: archive.org/details/akkartik-2

You get just one fixed screen resolution: 1024x768, 256 colors. Widely available on modern machines, no drivers needed.

You get just one fixed-width bitmap font. No bold/italics, no anti-aliasing.

BUT it won't make assumptions about English and left-to-right order. I eventually want anybody to be able to customize it to their language.

Main project page: github.com/akkartik/mu

I've been trying to visualize the default 256-color palette I get on baremetal.

akkartik.github.io/mu/html/bar

To my eyes it looks like I can/should just live in the first 128 colors.

I built a game of "snakes", but it came out more like an etch-a-sketch πŸ˜„

akkartik.github.io/mu/html/bar

Play it on any non-windows:

```
git clone github.com/akkartik/mu
cd mu
./translate_mu_baremetal_emulated baremetal/ex7.mu
qemu-system-i386 disk.img
```

h/j/k/l to draw

It took a while, but I've finally ported a pre-existing Mu program to baremetal: an RPN calculator.

This was _hard_, purely because of cursor management. I have a greater appreciation for everything that display hardware and terminal emulators provide for text mode. Mu so far puts the onus on the programmer.

akkartik.github.io/mu/html/bar

In the end it's interesting to visualize the changes I had to make:

vim -d apps/rpn.mu baremetal/rpn.mu

They're entirely in `main`; the rest is unchanged.

I've been reimplementing my from-scratch live-updating postfix shell to _really_ from scratch (no more OS kernel), while at the same time rewriting the prototype with lots of tests and actually giving the language some sort of rigorous basis. No demos yet, but in the meantime here's Conway's Game of Life running on baremetal Mu.

archive.org/details/akkartik-m

Sources: akkartik.github.io/mu/html/bar

Main project page: github.com/akkartik/mu

The Mu shell is now off Linux

archive.org/details/akkartik-m

Starting point for the sources: akkartik.github.io/mu/html/bar

The architecture is now much cleaner. Functions contain lines, lines contain words, words contain gap buffers. Rendering a thing renders its constituent things. Render takes a top-left coordinate and returns a bottom-right coordinate. Each thing knows which constituent thing has its cursor, shows its cursor when rendering, redirects incoming keystrokes to it.

github.com/akkartik/mu

An experimental way to do control flow in the postfix Mu shell

The screenshot below shows an idea I've been playing with.

The conventional way Forth does control flow is a little confusing with words like `if` and `then` showing up at the end.

Factor uses quotations to put code blocks on the stack. But then you see a potentially complex chunk of code executing "all at once".

Main project page: github.com/akkartik/mu

Drilling into computations on the Mu shell

This was one of the more difficult things I've built, and yet all I've gotten working so far is some rudimentary tokenization. The reason is one little feature.. well, take a look for yourself.

archive.org/details/akkartik-2 (video; 2 mins)

As always, built all the way up from machine code, and designed primarily to be easy to build, easy to run, comprehensible to others. Also this time with lots of tests

github.com/akkartik/mu

Today was documentation day

Primitives available in the Mu computer when running without an OS: github.com/akkartik/mu/blob/ma

Primitives available when running on Linux: github.com/akkartik/mu/blob/ma

For starters I focused just on making things more discoverable. These files are optimized for opening in your text editor, jumping to definitions to see type signatures, etc. See github.com/akkartik/mu/blob/ma for a ctags configuration for Mu and SubX programs.

Main project page: github.com/akkartik/mu

Mu can now read from an ATA (IDE) disk drive on Qemu.

github.com/akkartik/mu/tree/ma

It wouldn't have been possible without the lovely folks over on . And the inspiration of ColorForth (merveilles.town/@akkartik/1059), though I still don't understand how that driver works.

The Mu computer now has drivers for disk and mouse.

Still extremely klunky. IDE disk drives only, and the mouse driver uses polling because configuring IRQ 12 is still beyond me.

Example programs (as usual memory safe and translating 1:1 to x86 machine code)

Disk: akkartik.github.io/mu/html/ex9

Mouse: akkartik.github.io/mu/html/ex1

Here's video of the mouse example. There's no pointer so you have to imagine me moving the mouse around.

Like I said. Klunky.

Main project page: github.com/akkartik/mu

What should the signature of a program look like?

Typed languages have a fixed signature for function `main`. A list of strings, a window context, or an IO monad.

Here's the signature on the Mu computer:

fn main screen: (addr screen), keyboard: (addr keyboard), data-disk: (addr disk)

A rudimentary, hokey capability system. No mouse yet. 'screen' is only used for text; pixel graphics currently go around it. 'data-disk' can't access code, and will eventually include finer-grained restrictions.

Mu's HLL is now Turing-complete, I think.

Things to notice:
* Wordstar-style menu at the bottom.
* List of available primitive functions in bottom left.
* List of globals on the left side that updates as I add definitions.
* Matching parens highlighted as I type.
* Drilling down into the trace to understand how the program was evaluated.

github.com/akkartik/mu/blob/ma

Main project page: github.com/akkartik/mu

Writing code _within_ the Mu computer

I tried and failed to implement Bresenham's line algo. Horizontal and vertical lines work.

No macros => lots of lambdas.

The computer keeps crashing because I type too fast (still can't brain interrupt handlers). It frequently saves to disk, but as an s-expression. Reboots lose indentation.

Ok, edit on host -> create disk image.

I have lots of little buffers. When they overflow the computer crashes. Without a call stack.

Thanks @tekknolagi for pairing!

Show newer

@akkartik i'm out of my depth sorry, but wondering do you have a pointer to how the video interface works without Linux?

@akkartik from the readme in baremetal "Pure-graphics video mode" what does this mean?

@vulkanized Yeah, for sure. Basically, I do graphics by initializing my card using a BIOS call and thereafter writing pixels to a region of memory that transparently sends them to the video card (memory mapping)

There's a wide variety of modes that a card can be initialized in, and they affect how the region of memory is interpreted. For example if you choose a monochrome mode each bit is a distinct pixel. If you choose 24-bit colors each pixel requires 3 bytes. Not all cards support all modes.

@vulkanized Some modes are text only. They implicitly load a font and therefore you only need a few bytes to represent each rect of say 8x8 pixels. Text modes also have some smarts in hardware for cursor management and scrolling, and so can consume less power (less for software to do)

Unfortunately, even though I'm mostly doing text, there doesn't seem to be a widely supported text mode. So I'm using 1024x768 with 256 colors and loading a FOSS font.

@vulkanized Feel free to ask more questions. I can point you at the specific lines of code as needed.

@akkartik so in theory you could boot this on an actual x86 machine and use it now as an independent os?

@jameschip Yeah, in theory. It works on both Qemu and Bochs, and it's just relying on a keyboard and screen, so I'm hoping any mistakes aren't too arduous to debug.

On the other hand, I'm a total noob on the OS/hardware side of things. I briefly tried booting it on a Thinkpad T420s a couple of weeks ago. I couldn't even get the boot sector to print text to screen using BIOS primitives. Any testing/advice most appreciated.

@akkartik I can’t offer any advice unfortunately. I, like you, am just an interested tinkerer. I once thought about doing something like this to boot on a raspberry pi but I didn’t have the time for the scale of the problem at the time.

This is impressive and interesting stuff though. Congratulations.

@neauoire They're separate words. Break skips remaining words until a `}`. There will be a similar word called `loop` to jump backwards to a `{`. And some conditional way to skip a word or word group surrounded in {}

@akkartik ah yeah! The way Forth does loop and conditional is one of the most awkward thing in the language I find. For Uxn I didn't want to have this since it felts infix in a way.

@neauoire Yeah.

I've basically been trying to plan out a series of code examples:

- factorial
- pushing n numbers starting from 1
- binary search over a sorted array (inspired by this screenshot from vimeo.com/36579366)

My examples are kinda square, like me πŸ˜„ Other suggestions welcome. For some corpus of examples I want to make it really nice to browse the intermediate states of the computation.

@akkartik Oh wow, that's like a Mu Rosetta! I'd love to browse that when it's live :maru:

@neauoire πŸ˜‚

I've been thinking of it as mulisp. Or maybe even just Lambda as the layer above Mu?

@akkartik I've been thinking about something, did you watch the talk s-ol shared about smalltalk running on top of lisp, from yesterday?

It has gotten me thinking about implementing a Uxn assembler in Uxn itself, so I could write/assemble uxn programs from within the system.

Do you have something like this in Mu? Is lisp going to be that intermediary language for you? Any suggestions/lessons on this topic you could share?

@neauoire Uxn assembler in Uxn sounds eminently doable! Now I'm interested.

A full Smalltalk/Lisp like in that talk is a _lot_ of work. The final complexity discourages looking under the hood. Which rubs me the wrong way. Maybe you too.

The very notion of 'language' tries to pretend there's nothing underneath, which might be counter-productive.

So I'm still feeling my way with Mulisp. Maybe it's going to stay a toy, a gateway drug for kids to get into the level below.

@akkartik fair enough, that's a good answer. I'm looking forward to see how it evolves then :) Good luck with mulisp ✊

@neauoire I got super interested in building languages and parsers in grad school. The idea of building one language in another (or itself) is like catnip for us programmers. Like with religion or the Singularity, we all have an escapist urge to work at higher levels. But higher level languages don't actually seem to reduce mess. The mess isn't out there, it follows us. HLLs just increase CO2 emissions.

HLLs are good for prototyping. Once that's done, shrink dependencies. Like you already do.

@akkartik yeah I agree, I always thought, well, why don't people make assembly languages that are fun enough to use that there's no need to build on top of it. Maybe there are problems there I haven't encountered yet.

Lisp as the first language above bytecode sounds fun enough that no other language needs to be build on top.

@neauoire Seems worth trying, anyway πŸ™‚ I had some ideas for removing parens and adding infix from a previous Lisp project: akkartik.name/post/wart. I'm planning to pull them in here for like a quick calculator mode.

I honestly don't think there's much for you to learn from "experienced" programmers. Trust your instincts ✊ The rest of us don't know what we're talking about.

Rereading your original question, did you want to build Uxn on mulisp or Lisp? That'd also be a neat prototype.

@akkartik No no, my original question was.. I was wondering if you had considered implement mu in mu itself, I'm curious to see if you're planning on writing mu from within mu itself, when you started working on a lisp a few days back it got me wondering what you needed metaprogramming for. But you answered that well saying it was just a fun direction to take this to.

Show newer
@akkartik @neauoire This looks a bit similar to i-expressions, sweet expressions or wisp; Were you aware of them or did you come up with your whitespace mechanism independently?
Show newer

@neauoire @akkartik do you mean "assembly" languages for actual hardware? or bytecode? the answer for the former seems obvious to me: since an assembler is meant to reflect accurately and completely on the hardware capabilities, the creation of the "fun" is in the hardware, and perhaps in the choices in representing the hardware words/macros- And the way these become not fun is through backwards compatibility, and "natural" growth trying to satisfy shifting performance requirements...

@neauoire @akkartik I used to have a lot of fun programming z80 assembler, essentially an ancestor of x86. But modern x86 processors have a lot of stuff in them that can only be effectively utilised by compilers- hand rolling is just not an option, and those choices were all done for performance.

Show newer
Show newer

@akkartik
it's all fun and games until your anonymous functions become a couple lines long ;)

although at least with lisp its trivial to print only e.g. one form deep to keep it short

@s_ol The hope is that anything with this visualization will be easier than without it. It admits skipping past the long forms to drill down to the critical places, which could be short.

Though pretty printing is also an option. It's fairly well-understood for Lisp (though not by me πŸ™‚)

Sign in to participate in the conversation
Merveilles

Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them.