Sijmen πŸ§‘β€πŸ’»

271 Followers
275 Following
707 Posts
Programming, retrocomputing

@itsfoss I find the "it's 30 year old C code" argument a bit shallow, if anything that means it's proven and tested code.

Then the argument that Rust draws young developers who make fresh choices like using Rust. That's a bit circular and also ageist.

A new article, this one about the application of Clausewitz's concept of friction to Software Engineering:

https://deadsimpletech.com/blog/friction_software_engineering

Understanding friction in software engineering | deadSimpleTech

That, in short, is how friction works in war: things start out organised, prepared and informed. Then the bullets start flying, and little by little, things go wrong and start to break apart. Co-ordination breaks down, people get tired and demoralised, and eventually what started out as a well-oiled, effective machine that was more than capable of achieving objectives ends up as a tired, worn-out blob that cannot fight any more or go any further. This seems simple, but as Clausewitz has it, "in war, everything is very simple, but the simplest thing is hard".

deadSimpleTech

There was an article about moving to Codeberg on the orange website yesterday, and out of interest to get an impression of what average programmers think of the idea of moving, I took at look at the comments. (Yeah, I know β€¦)

I’m going to write here my thoughts on a general impression of the comment thread as a whole. (Rather than respond to individuals.)

@rl_dane my 11th gen Intel CPU laptop does indeed not have BIOS compatibility

The project may be CSMWrap: https://github.com/CSMWrap/CSMWrap

I've been meaning to try it out, but if you don't have a hardware support, the emulated VGA BIOS apparently isn't suitable for games and such

GitHub - CSMWrap/CSMWrap: Get PC BIOS back on UEFI only systems.

Get PC BIOS back on UEFI only systems. Contribute to CSMWrap/CSMWrap development by creating an account on GitHub.

GitHub

@adw99 that's so cool! I envy the people who got to take classes from authors like him. Still sad in hindsight that I didn't go on to study proper CS under Tanenbaum and such.

Anyway from what I read WDM is still somewhat relevant, but my target is Windows 2000!

Time to curl up with a good book #Programming

New post: shell tricks that aren't exactly secret, but aren't always taught either.

Split into two sections: what works on any POSIX sh (FreeBSD, OpenBSD, Alpine...) and what's Bash/Zsh-specific. Because not everyone is on Linux with bash as their login shell.

Things like CTRL+W, $_, pushd/popd, fc, set -euo pipefail caveats, and more.

https://blog.hofstede.it/shell-tricks-that-actually-make-life-easier-and-save-your-sanity/

#unix #bash #shell #sysadmin #freebsd #linux #cli

Shell Tricks That Actually Make Life Easier (And Save Your Sanity)

Watch someone backspace 40 characters instead of pressing CTRL+W, and you’ll understand why this list exists. A collection of shell tricks-grouped by what works everywhere and what’s Bash/Zsh-speci...

Larvitz Blog
@jsbarretto one place where I did have noticeable search times was when working with pkgsrc on a HDD

So a more practical question then - 27" or 32" for a 4K monitor?

27" at 150% = ~109 logical DPI
32" at 125% = ~109 logical DPI
32" at 150% = ~96 logical DPI

So the 27" would be squinting for old software, comfortable for newer defaults. 32" could do either depending on scale factor, but it's biiggg

@mhd this screenshot is a good example I think. On the left PuTTY and Conhost, perfectly comfortable at 96 logical DPI, and sizing similar to classic desktop software.

On the right, Windows Terminal with default sizes. Perhaps this looks more reasonable on a 109 logical DPI desktop screen (like Apple's, or a 27" 4K screen at 1.5x), or from across the room, but on a regular 96 logical DPI screen it's ridiculous