Kissaki

I had to look up pebkac / PEBKAC

problem exists between keyboard and chair

I also like the acronym PICNIC - problem in chair not in computer

Storage concerns should be separate from the data model.

would make it clearer

Would make what clearer?

If I change a string to a raw string or an interpolated string, it is a semantic change on the entire string, even if it leads to consequential changes only on subsections of it. The next time or additional changes I make must take different semantics into account.

If the formatting configuration forces one specific style then that is the deliberate choice; to have that one.

If there is no uniform single string quoting it is useful to differentiate between them; for example if for normal strings ' is preferred while for specific cases where escaping characters like \n is required, " must be used.

Don't use the share with shortened url. Copy the page url instead.

Otherwise (you'll have to) accept that you don't know what's included in the shortened link.

"" to '' … There is nothing to highlight for SemanticDiff.

Really? I definitely want to see that. I want to be deliberate about my code. I am not only targeting compiled code. I am also targeting developers through maintainable code.

I'm surprised they did not list an alternative that would be my preference: Highlight the entire string. The f prefix changes the entire text value type. I would like the `f´ to be highlighted strongly, and string it changes the interpretation of weakly, and the placeholder variable more strongly again.

Is it because you read one per day by the end of the day?

Does the Linux Kernel use simple C though?

I think and assume they use enforced guidelines, custom types and tooling to make it workable. By that point C is no longer simple. You extended the language to make it safe, and ended up with the same complexity.

I'm very skeptical of sticking to "old and tested" without reasoning.

If you're talking about the implementation, if they're making changes it's no longer "well tested". If it's undocumented, it's not approachable. If you're talking about toolchain, if the old is unapproachable because of inherent toolchain barriers, and custom toolchain dialects, I think it's good to question.

There may also be something to say about them struggling to get new contributors and maintainers (from what I heard/read).

The "we use a stable macro that uses the same unstable features anyway" is kinda confusing though.

I guess it's about language interface stability more than unstable feature functional stability?

DRM panic support

I'm already panicking

Linus Tech Flips