movq @www.uninformativ.de
 (14h ago)

More widget system progress:

https://movq.de/v/87e2bce376/vid-1767467193.mp4

I like the oldschool shadow effect. šŸ˜… Not sure if Iā€™ll keep it, but itā€™s neat.

The menu bar is still fake.

Had to spend quite a bit of time optimizing the rendering today. This can get really slow really quickly.

Unicode is Pain.

I might be able to start porting my first program (currently uses urwid) soon. šŸ¤”

#xtkev6q
lyse @lyse.isobeef.org
 (1d ago)

@movq@www.uninformativ.de I noticed that your feedā€™s last modification timestamp was missing in my database. I cannot tell for certain, but I think it did work before. Turns out, your httpd now sends the Last-Modified with UTC instead of GMT. Current example:

Sat, 03 Jan 2026 06:50:20 UTC

Iā€™m not a fan of this timestamp format at all, but according to the HTTP specification, HTTP-date must always use GMT for a timezone, nothing else: https://httpwg.org/specs/rfc9110.html#http.date

#vqu5wfq
prologic @twtxt.net
 (1d ago)

Mu (Āµ) is now getting much closer to where I want it to be, it now has:

  • A process stdlib module (very basic, but it works)
  • An ffi stdob module that supports dlopen / dlsym and calling C functions with a nice mu-esque wrapper ffi.fn(...)
  • A sqlite stdlib module (also very basic) that shows off the FFI capabilities

šŸ˜…

#n3vbeia
prologic @twtxt.net
 (1d ago)

(#w3qxekq) @movq@www.uninformativ.de What I wish for once on this miserable planet is for coporations one day ohave a different set of reasons to exist and thrive other than:

but since the only goal of that manufacturer is to make money, they do it

Life becomes very boring and uninteresting when your only goal in life is to ā€œmake more fucking moneyā€ šŸ’° Fuck šŸ¤¬ Fuck this Corporatocracy we live in šŸ¤¦ā€ā™‚ļø

#gpoo3oq
movq @www.uninformativ.de
 (1d ago)

(#voi7gxa) @eldersnake@we.loveprivacy.club

Steps to world domination:

  1. ā€œInventā€ ā€œAIā€ (by using other peopleā€™s data).
  2. Get people hyped about it and ideally hooked on it.
  3. Only provide it as a cloud service. But hey, if you want to, you can run it locally!
  4. Buy all hardware available on the market, so that nobody but you can build more systems.
  5. All PCs of consumers and competitors are too weak now and canā€™t be upgraded anymore.
  6. Everybody depends on your cloud service! Win!

All of that is possible because corporations donā€™t have a ā€œconscienceā€ in capitalism. Nobody forces the RAM manufacturers to sell all their stuff to just one or two buyers, but since the only goal of that manufacturer is to make money, they do it.

#w3qxekq
lyse @lyse.isobeef.org
 (2d ago)

(#tcz2koq) @movq@www.uninformativ.de Iā€™m pretty sure I know a bunch of people who love to blow up their money. :-(

Holy shit! :-O At least, the walls didnā€™t shake here. But we also had some very loud explosions, maybe they were far enough away. :-? Of course, the bangs continued last night.

Maybe some politicians need to be personally attacked with this sort of shit first in order to ban it once and forever.

#3jjzmca
movq @www.uninformativ.de
 (2d ago)

(#ex5vwtq) At around 19 seconds in the video, you can see some minor graphical glitches.

Text mode applications in Unix terminals are such a mess. Itā€™s a miracle that this works at all.

In the old DOS days, you could get text (and colors) on the screen just by writing to memory, because the VGA memory was mapped to a fixed address. We donā€™t have that model anymore. To write a character to a certain position, you have to send an escape sequence to move the cursor to that position, then more escape sequences to set the color/attributes, then more escape sequences to get the cursor to where you actually want it. And then of course UTF-8 on top, i.e. you have no idea what the terminal will actually do when you send it a ā€œšŸ™‚ā€.

Mouse events work by the terminal sending escape sequences to you (https://www.xfree86.org/current/ctlseqs.html#Mouse%20Tracking).

ncurses does an amazing job here. Itā€™s fast (by having off-screen buffers and tracking changes, so it rarely has to actually send full screen updates to the terminal) and reliable and works across terminals. Without the terminfo database that keeps track of which terminal supports/requires which escape sequences, weā€™d be lost.

But gosh, what a mess this is under the hood ā€¦ Makes you really miss memory mapped VGA and mouse drivers.

#eyfftcq
movq @www.uninformativ.de
 (2d ago)

(#wap76wa) @lyse@lyse.isobeef.org I havenā€™t spoken to a single person yet who was a fan of all this. Not even the more conservative family members.

Some people have detonated several really loud bombs yesterday. This wasnā€™t a ā€œBƶllerā€. It shook my walls, doors, windows. Family members in other parts of the country reported the same ā€¦ Is this a new trend?

#tcz2koq
lyse @lyse.isobeef.org
 (2d ago)

The only good thing about this absolute craziness is that I can restock my rocket sticks. I picked up twelve along the way. Unfortunately, it looks like 99.999% of ammunition is bombs instead of rockets. Some sections of my street look exactly like an arbitrary Pakistanian town that Iā€™ve seen online.

There was surprisingly much snow in the woods. Also, all ponds have frozen over. I didnā€™t expect that. Not at all. There were even illegal ice skating tracks in the natural reserve. We came across a large puddle and it was at least 10cm solid ice to the ground. Crazy!

https://lyse.isobeef.org/waldspaziergang-2026-01-01/

#wap76wa
prologic @twtxt.net
 (2d ago)

(#p43aoaq) @lyse@lyse.isobeef.org A ā€œHello Worldā€ binary is ~372KB in size. I currently have peephole optimization and deac code optimizations in play, and a few other performance related ones, but nothing too fancy. I have a test case that ensures fib(35) doesnā€™t regress too badly as I continue to evolve the language.

#y656lsa
prologic @twtxt.net
 (3d ago)

Opinion / Question timeā€¦

Do you think Mu (Āµ)ā€™s native compiler and therefore emitted machine code ā€œruntimeā€ (which obviously adds a bit of weight to the resulting binary, and runtime overheads) needs to support ā€œruntime stack tracesā€, or would it be enough to only support that in the bytecode VM interpreter for debuggability / quick feedback loops and instead just rely on flat (no stacktraces) errors in natively built compiled executables?

So in effect:

Stack Traces:

  • Bytecode VM Interpreter: āœ…
  • Native Code Executables: āŒ
#hagpelq
lyse @lyse.isobeef.org
 (3d ago)

(#2c6a7qq) @movq@www.uninformativ.de Well, just a very limited subset thereof:

  1. inline and multiline code blocks using single/double/triple backticks (but no code blocks with just indentation)
  2. markdown links using using [text](url)
  3. markdown media links using ![alt](url)

And thatā€™s it. No bold, italics, lists, quotes, headlines, etc.

Just like mentions, plain URLs, markdown links and markdown media URLs are highlighted and available in the URLs View. Theyā€™re also colored differently, similarly to code segments.

I definitely should write some documentation and provide screenshots.

#wtcmiaa