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

Spent basically the entire day (except for the mandatory walk) fighting with Pythonā€™s type hints. But, the result is that my widget toolkit now passes mypy --strict.

I really, really donā€™t want to write larger pieces of software without static typing anymore. With dynamic typing, you must test every code path in your program to catch even the most basic errors. pylint helps a bit (doesnā€™t need type hints), but thatā€™s really not enough.

Also, somewhere along the way, I picked up a very bad (Python) programming style. (Actually, I know exactly where I picked that up, but I donā€™t want to point the finger now.) This style makes heavy use of dicts and tuples instead of proper classes. That works for small scripts, but it very quickly turns into an absolute mess once the program grows. Prime example: jenny. šŸ˜©

I have a love-hate relationship with Pythonā€™s type hints, because they are meaningless at runtime, so they can be utterly misleading. Iā€™m beginning to like them as an additional safety-net, though.

(But really, if correctness is the goal, you either need to invest a ton of time to get 100% test coverage ā€“ or donā€™t use Python.)

#4yvgryq
prologic @twtxt.net
 (1d ago)

yes, yes thatā€™s right. Mu (Āµ) now has a built-in LSP server for fans of VS Code / VSCodium šŸ˜… You just go install ./cmd/mu-lsp/... and install the VS extension and hey presto šŸ„³ You get outlines of any Mu source, Find References and Go to Definition!

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

(#3egmgba) @movq@www.uninformativ.de Hehe. :-) This steep footpath connects a hiking parking lot outside the village and the edge of the village in a fairly straight line. Garden owners are allowed to drive their vehicles down from the village to their lots on this pathway and up again. These two poles are placed about a third up from the botton on a short, comparatively flat section to stop people from taking this shortcut to get down to the country road. Said road goes through the village but there are hairpins getting up and down. The road markings have been added recentlyish. I suspect to warn shooting down cyclists of the danger ahead. I havenā€™t seen something like this anywhere else either. :-)

#3ztjgba
lyse @lyse.isobeef.org
 (1d ago)

My mate and I went on a hike earlier. Yesterday, we had lovely 12Ā°C. But today, it was down to at most 4Ā°C. Oh well. At least the sun was out and and there was just a tiny bit of wind. We knew upfont that scarf, beanie and gloves were mandatory. Especially at the more windy sections like up top the hills. The view was absolutely terrible, but we made the best of it.

With the sun shining on us during our lunch break at a forest edge bench, we still enjoyed the lookout in 01. I brought some old carpet scraps to sit on and was happily surprised that they isolated even better than I had hoped for. Some hot tea helped us staying warm.

After five hours we returned just after sunset. Iā€™m quite tired now, completely out of shape.

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

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

So, are you guys up for an experiment?

Iā€™m really not happy with the domain ā€œuninformativ.deā€ anymore. Iā€™m going to switch to ā€œmovq.deā€ soon (or maybe something else if I get another fancy idea).

If I keep the url = field in my twtxt file, nothing should break, right? Right? šŸ¤£

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

(#qpsyz6q) Wow, as I anticipated, this is waaay out of my capabilities to really understand it. But Iā€™m quite happy to just have spotted a mistake in an explanatory comment in section 4.5.2 ā€œThe icode Arrayā€. Of course, it should be /e + tc + /i + ni + t\0. Letā€™s hope that my e-mail with the patch actually makes it into Briamā€™s inbox. I fear GMail just hides it in the spam folder.

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

(#hddm6pa) @prologic@twtxt.net Iā€™d love to take a look at the code. šŸ˜…

Iā€™m kind of curious to know how much Assembly I need vs. How much of a microkernel can I build purely in Mu (Āµ)? šŸ¤”

Canā€™t really answer that, because I only made a working kernel for 16-bit real mode yet. That is 99% C, though, only syscall entry points are Assembly. (The OpenWatcom compiler provides C wrappers for triggering software interrupts, which makes things easier.)

But in long mode? No idea yet. šŸ˜… At least changing the page tables will require a tiny little bit of Assembly.

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

(#hddm6pa) Iā€™ve only got a handful of syscalls working right now. Taking inspiration from the calling convention of the Linux kernel and even made the service/interrupt handler int 0x80h šŸ¤£ Iā€™ve only got read, write, alloc and exit working righ tnow šŸ„²

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

(#hddm6pa) Whohoo! šŸ„³ You have no idea how great a feeling this is! This includes the Mu stdlib and runtime as well, not just some simple stupid program, this means a significant portion of the runtime and stdlib ā€œjust worksā€ā„¢ šŸ¤£

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

Btw @movq@www.uninformativ.de youā€™ve inspired me to try and have a good ā€˜ol crack at writing a bootloader, stage1 and customer microkernel (ĀµKernel) that will eventually load up a Mu (Āµ) program and run it! šŸ¤£ I will teach Mu (Āµ) to have a ./bin/mu -B -o ... -p muos/amd64 ... target.

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

Took me nearly all week (in my spare time), but Mu (Āµ) finally officially support linux/amd64 šŸ„³ I completely refactored the native code backend and borrowed a lot of the structure from another project called wazero (the zero dependency Go WASM runtime/compiler). This is amazing stuff because now Mu (Āµ) runs in more places natively, as well as running everywhere Go runs via the bytecode VM interpreter šŸ¤ž

#lo7lumq