James Widman

unicode mavens, please correct me if i'm wrong, but this:

"Furthermore there are practical issues, such as bidirectional text [...]"

does not seem applicable to the question of whether a compiler should allow non-ascii characters in identifiers. (iiuc, you only need to worry about bidi stuff when you're rendering glyphs. and compilers generally don't have render pipelines.)

so this seems like a bullshit excuse.

@mekkaokereke@hachyderm.io

• Is self-deprecating about his pale skin, and how much sunscreen he has to wear.

This is basically the right mindset. We are extra susceptible to folate loss; it's a dermal disability. So it's healthy to acknowledge & accommodate for that!

@TomF@mastodon.gamedev.place i really really like this approach to code presentation:

• https://gargaj.github.io/demos-for-dummies/#outro/1

it would be really cool to see it as a standard part of something like forgejo, for cases where you have a big change that you present as a series of commits, and where you can write a list of comments where each comment points to/highlights a set of chunks in a commit, with that nice big "next" button to introduce the next comment & highlight set.

@typeswitch ok, (1) this rules. (2) in case anyone cares:

• Clang 22 and GCC 15 introduced support for the new ISO C feature for named loops*

• the GNU C feature, statements-and-declarations-in-expressions**, can be used in lots of interesting places; e.g. ternary expressions; in the final /expression/ part of the header of a for-loop; etc.

[*] https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3355.htm [**] https://gcc.gnu.org/onlinedocs/gcc-3.2.2/gcc/Statement-Exprs.html

"we can't put that horse back in the barn"

what are you talking about. horses aren't invincible.

time is an illusion. st_mtime, doubly so.

periodic reminder that creationists don't know what darwinian evolution is.

if given a pop quiz on the basic concepts, they would not be able to earn a passing grade.