mrkite

I would fix that bug but the complete rewrite that management has had me working on for the past two years will make it obsolete anyway.

Oracle users are masochists.

It was definitely DDJ.. back in the early 90s, right? I once asked Walter Bright (creator of D) if they were related and he told me it was just a naming coincidence.

I prefer using the command line.. but it is nice to be able to use a TUI to select the staging files, so this works out perfectly.

One of the people reverse engineering the M1 GPU for Asahi Linux is a catgirl vtuber: https://www.youtube.com/asahilina

The problem is that if you send a message just blindly, you can be tricked into sending spam to millions of addresses. I do one thing that prevents that, but does violate the standard, I verify there's only 1 '@' in the address.. this technically prevents people with '@'s in their name, but they probably find it impossible to do anything with that address anyway.

If you're going to do a text adventure, don't deprive yourself of using the most English friendly dsl ever, inform 7.

State machines always make me think of the Disk II controller on the Apple II. It uses a state machine to implement reading and writing sectors to disk.

https://www.bigmessowires.com/2021/11/12/the-amazing-disk-ii-controller-card/

Depends on your language.

https://flutter.dev/

https://fyne.io/

https://slint.dev/

https://github.com/ocornut/imgui

What are you talking about? Compilers can and do flag undefined behavior as errors. I recommend you read up on the documentation of any compiler.

And I recommend you read Chris Latter's essay on UB.

https://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html

Where he gives plenty of examples of UB resulting in the compiler optimizing away safety and introducing security vulnerabilities silently. In part 3 he discusses the efforts clang has made to improve on this.

He then went on to make Swift and says this: "Undefined behavior is the enemy of safety, and developer mistakes should be caught before software is in production."

and

"UB is an inseperable part of C programming, […] this is a depressing and faintly terrifying thing. The tooling built around the C family of languages helps make the situation less bad, but it is still pretty bad. The only solution is to move to new programming languages that dont inherit the problem of C."

It violates the principle of least surprise. You don't expect the compiler to delete your bounds checking etc.

The way c and c++ define and use UB is like finding an error at compile time and instead of reporting it, the compiler decides to exploit it.

Back before it was awful, sourceforge required your code to be in CVS and then later svn.