unsafecast

Sounds good! I don't use either anymore so I wouldn't know.

What about having it listed with the actual name, but when you're viewing it in the program launcher you have a hint in gray? Something like this:

- Okular Document Viewer

If I have two PDF viewers, should both be called "PDF viewer"? Gnome seems to love hiding the actual names (the gnome document viewer is actually called evince).

Why does it alternate between 2023 and 2013?

I end up using a checkers piece, since pretty much every board I've played on has them.

You say underpromotion, but something people are surprised by is making a second queen ime. People sometimes assume promotion is actually "taking a captured piece back".

Indeed, we're being too kind to you.

Also at http://om-language.org

Hah, I thought I was the only one who lifts shift too late and gets :Wq.

> Technically, int32_t is bad in that way, but we are not fooled by it.

Meaning? On my system int32_t is directly typedefed to unsigned int, absolutely no hidden pointers or conversions.

What order are the bytes in 0xabcd intended to be used in? I don't see how making it 0x[ab, cd] would be ambiguous, it's the same assumption of reading left to right.

I think the iBooks were made like that.

That applies to GLSL in general. I tried once to emulate that using C unions, but quickly realized that there's no solution for v.xz, v.xw, v.yw, etc.

You can write functions like xyz(v) and that works well enough. Even better if you have ufcs or methods.

That's such a perl/raku thing, and I mean it in the best way possible.

Of course it does - endianness interferes with any sort of numeric literal. Doesn't matter if it's hex, decimal, underscored, whatever.

Not for them :)

Okay but why _not_ use go? You never gave a reason.

You missed a backslash before your asterisks :)

From what I can tell, sd has a feature that reads a comment or something from your scripts and displays them in the tab completion. So 'sd <tab>' would show a summary of commands and apropos.

> Edit: Actually since it's a structure, the calling convention is to memory allocate it and pass a pointer, doh. So it should actually compile the same.

Depending on calling convention, the structure may be spread out into registers.

Sublime.

This is the reason why I love it. Yes, it's not pretty, but you can hack anything into it really quickly. The fact that it's so 'informal' is the reason why it works so well imo.

In my own experience, it's just as fast if not a tiny bit faster, but what it's _really_ good at is customisability. With sublime I tried once to write a small plugin for gofmt and go vet (I don't remember what was wrong with the existent ones), and I gave up because it was more complex than I anticipated. With Lite XL I did it in 10 minutes and about 20 lines of lua code (though I did use this other plugin, it's a kind of support for linters).

Whatever I wanted to do it felt like I can just open the config and hack on it. Sublime never felt this way.

I'm not sure I got your point.

Also, https://www.teamten.com/lawrence/writings/coding-machines/

I think GP meant that it's two digits instead of one (you have to type 01, not 1).

How does compiling it yourself change anything?

This is so stupid and genius at the same time.

The landing gear creates very high air resistances. Certain maneuvers are impossible to do with it down, you can't fly very fast, ridiculously high fuel consumption, et cetera.

That's a fair point. I guess attacking the problem from another angle helps then - simplifying the computer UI and minimising the number of situations where an alarm could be warranted in the first place.

But yes, this stuff is very complex and I'm (we're?) only judging this from the outside.

But we can have both. Make the button yell at you if the circumstances make it dangerous to use it. The fact that they didn't know is a failure of the system, which should've let them know immediately that the button didn't actually do the thing.