On new Rails apps, that are not in production yet, I sometimes like to reorder my database migrations.
I recently built a new desktop gaming computer. Here are some pictures I tool along the way.
I wanted to learn to create a dynamically-named method inside a dynamically-named class in Raku. This is what I ended up with:
#!/usr/bin/env raku my $class-name = "MyDynamicClass"; my $method-name = "dynamic-method";
It seems fairly feature-complete, even with only a 0.1.x version number! https://martenframework.com/docs/.
About two days ago I built the “bookshelf” app described in the Hanami guide. Hanami is currently missing any sort of “model” layer, as well as any sort of “view” layer, as you might expect to be present from using Ruby on Rails or other MVC web frameworks.
I asked about these missing pieces on the Hanami forum and it was explained to me the missing pieces will appear in the 2.1 release, in Q1 2023, and in the meantime to please go look at two other projects, to learn by watching them being built. I looked at the two projects but saw no model or view layer code.
And as nice as I can think to say this, I don't understand how they got to a place where they decided a 2.0 version number was appropriate, given these basic components are not present, not even in some very basic form. Hanami presently seems more like a 0.5 version framework to me.
The Hanami homepage currently contains the words "full-featured". I have no idea why they would say that. "2.0" implies to me a second major version of an already completely fleshed-out framework. ¯\_(ツ)_/¯
I stopped looking at it for now. I don't want to invent all the missing pieces only to have my code become obsolete in 6 months.
I wrote a simple MP3 player:
Debug a Linux Kernel in QEMU