Sweet, very impressed.

To be really usable, for embedded and otherwise, a well documented and ergonomic C API for bindings is needed though.

The closest I could find was "If you need to add more predefined functions, add them in intrinsics.h." I will take a look though, this seems really promising

EDIT: Looks to be pretty easy to tack an external registration mechanism onto intrinsics.h. Good to go then ..

.. Only two SO comments at this point .. come on folks :-)

I wish premake could gain more traction. It is the comprehensible alternative to Cmake etc.

I'd rather everyone use CMake than have to deal with yet another build system. Wouldn't be so bad if build systems could at least agree on the user interface and package registry format.

Xmake[0] is as-simple-as-premake and does IIRC everything Premake does and a whole lot more.

[0] https://xmake.io/

Completely useless in an airgapped environment

Could you elaborate on that?

I'm guessing it needs internet for everything and can't work with local repositories.

Not really a fan of Meson but I doubt that that's the case as it is very popular in big OSS projects and distributions aren't throwing a fit.

No?

Oh yes. For one thing "hexdump -C ." would work out nicely in those days.

Isn't hexdump the modern punk upstart.

In my day we had to use od, and were happy to have it, now get off my lawn.

Full disclosure, I am one of those "modern punk kids" but my first boss was firmly in the od generation. and all his documentation referenced it as such. hexdump is ergonomic heaven in comparison.

I always found buildroot a lot easier to fathom and harness. And certainly flexible enough with the ability patch every included recipe and package.

I cut my teeth on Buildroot but greatly prefer Yocto now. Buildroot is fast and loose, where Yocto forces you to do the right thing.

I think it is easier. But for some projects it becomes harder to maintain.

Well said! I have met a few of these codesmells where the actual functioning is hidden behind a bewildering maze of facades, shims, proxies and whatnot.

I guess some has had an irresistible itch to use as many patterns from the GoF book as possible.

Smells like Ruby to me haha. I know is not the language, but for some reason the ruby code I've stumbled into are all like that.

To me it sounds like what I use Ruby to get away from.

It's rare to need facades, proxies, and shims in a dynamically typed language where the caller doesn't need to care about the type of the object they call.

In fact, most of the Gang of Four design patterns either make no sense in Ruby or are reduced to next to nothing.

Very impressed with ghostty so far, but: Main reasons for sticking with ITerm2 (for the moment at least):

- "Seamless" cut & paste with paste on "2 X right click" + "Trim trailing LF"

- Quadruple click "Smart selection"

- Brillant search with highlighting in text and scrollbar

- Support for OSC-1 "icon titles" in tabs, as opposed to OSC-0 "header title"

I connect to serial ports a lot in what I do, and never really understood why this should be handled by the terminal emulator. Much better done with eg. picocom, python serial.tools.miniterm or the like.

LuaRT is based on ZeroBrane, actually :-)

Alfred (https://alfredapp.com) has a snippet manager (and a _whole_ lot more kbd goodies)

You can: Help for bash 'history -s args': The args are added to the end of the history list as a single entry

Thank you. I must find the equivalent zsh command.