Also, possible blood clotting or stomach issues sound scary, but Aspirin has similar (opposite) issues. Pharmacists regularly push its combinations with Acetominophen (which has, of course, synergetic bonuses, but is not the reason) under multitude of brands with a hefty premium when people ask for either one. So in many situations you need to consider the added risks from Aspirin too.

Ideally, I'd like to have an optimized strategies of using all three of the aforementioned substances for common situations. Like, is rotating ibuprofen/acetominophen during the day safer than consuming just one?

Unless you're building a Blender or an Ardour or, I don't know, a trading platform or a game, an individualized GUI should be the last of your priorities.

Huh, someone's in it for the thrill of the hunt, I see...

I rarely do anything besides the basics (F5/F6) when managing files in MC, and for advanced stuff, like using rsync/rclone for moving files, I mostly use the usermenu.

Command entering is just one if the "modes", and not necessarily the default one.

If shortcuts are limited to special keys and combos, this frees plane input for commands, but I personally prefer list filtering by default.

Very rarely I use custom-filtered (brownish) noise to help with isolation. Perhaps some kind of Ambient or New Age would work too in such situations, but things I like in those genres require attention and not paying it would be absolutely disrespectful.

I listen to all kinds of music at my dayjob but only during specific activities that do not require much contemplation and I can mostly flow with the music and do the work in the background.

Though, I'm a musician and sound engineer, so my relationships with music in general might be a bit special.

Not everybody is Dijkstra.

Thanks for the list.

> ... CRDTs for version control, which is long overdue but hasn’t happened yet

Pijul happened and it has hundreds - perhaps thousands - of hours of real expert developer's toil put in it.

Not that Bram is not one of those, but the post reads like you all know what.

The crux of the matter is that there's nothing that protects an open project besides reputation, and nowadays in the digital space it can be cheaply farmed.

Laws could help, but they only work when you undertake purposeful actions to be covered by them, like register a trademark, and it's never cheap.

Imagine you're in a local band playing shows. It's 3 month old and you have no issued records. A second band tighter with venues takes your name and starts performing under your moniker. You have no money to take that to court and good luck making a case. You can't do anything besides screaming on the web or, don't know, kicking a few butts. You change your name.

If by AI you mean non-supervised, autonomous conscience (as I believe the term has to be reserved for), then the answer is again no, as it's as responsible for the quality of its PRs as humans.

If the thing writing code is the former, but there's no human or responsible representative of the latter in the loop, then the code shouldn't be even suggested for consideration in a project where any people do participate. In such case there's no point in storing any additional information as the code itself doesn't have any value (besides electricity wasted to create it) and can be substituted on demand.

Commit comments are generally underused, though, as a result of how forges work, but that's another discussion.

[1]: https://alexpasmantier.github.io/television/

Surprisingly, some of the projects such as AkelPad are still alive.

Win32 made things easier, as well as things like Delphi and Scintilla later.

Just checked my archives, and my own naive but functioning attempt measures whole whopping 36520 bytes, though not without the help of an executable packer, which was a fashion then.

Mostly works fine under Wine, though it is about the legal US drinking age.

The corrupt class is, of course, following the oppression guide, so graciously provided and field-tested by their northern neighbour, rather diligently.

It would be unwise to overstate their (elite's) autonomy, considering economical and cultural ties on all levels, though.

The Jakt -> Swift -> Rust pivots look like the same thing on a different level. The initial change to Swift was surely motivated by potential industry support gain (i believe it was a dubious choice from purely engineering standpoint).

It's awe-inspiring to see how a person can carve a job for himself, leverage hobbyists'/hackers' interest and contributions, attract industry attention and sponsors all while doing the thing he likes (assuming, browsers are his thing) in a controlling position.

Can't fully rationalize the feeling, but all of this makes me slightly wary. Doesn't make it less cool to observe from a side, though.