You know, I wish #C compilers had a super strict warning compiler flag, I know there's -Wall, but it doesn't actually turn on all warnings oddly enough.
C could probably be almost as safe as memory-safe languages if the programmer didn't have to pass 30 different warning flags, link with ASAN and UBsan, pass mysterious -f compiler flags, pass odd macro flags like _D_FORTIFY_SOURCE, etc.
Finally, a sensible take on #Wayland and #Xorg that isn't just "me tribe good, you tribe bad."
https://dudemanguy.github.io/blog/posts/2022-06-10-wayland-xorg/wayland-xorg.html
New blogpost, it's about how I became a #Slackware user, and how i've been using it for more than a year now lol
v2.1 of my #sh2exe script has been released. Now you can make it so the script won't open a console window, includes a few more utilities, and now includes a variable $SH2EXE_ARGV0 to get an $0-like variable. Useful for the one liner cd $(dirname $SH2EXE_ARGV0) || exit 1
Sneak peak of my sh2exe program in action ;)
So, I'm working on a project for #Windows, called sh2exe.
Basically, it'll let you distribute an executable that can run a standard shell script, with the capabilities of GNU Coreutils. The idea, is that this will lower the bar for entry to port a program over from #Unix-likes to Windows. The shell I chose ended up being the portable OpenBSD Korn Shell =). And the reason I chose GNU Coreutils is because i'm familiar with it, it's pretty small, and just works for the most part =P
So far, once that exe is made, it's only 1 megabyte in size!
So, I think i've come up with a good new name for my #dscip project: #pocid (POsix Continuous Integration Daemon). Pronounced: Paw-kid.
What do you guys think? Please boost as I want a range of opinions on this!
Link if your curious of the project: https://opencode.net/charadon/dscip
