And bow to the compiler’s whims? I think not!

This shouldn’t compile, because .into needs the type from the left side and let needs the type from the right side.

[clicks light switch off and on repeatedly]

Welp, I guess we’re closed for the week.

Common criticisms here would be that these endeavors stifle creativity and show the adoption of modern solutions. That said, I find conducting “code archeology” to figure out the idiomatic way of doing something in an old project very rewarding. Because computer programs exist in people’s mind’s, doing that with the support of original developers or subject matter experts is some of the most effective knowledge transfer I’ve ever witnessed.

That totally threw me off. “Literally unplayable,” as they say.

Industrial controls equipment made by German companies can be programmed in English or German. You can also switch languages (German/English) at any time and the IDE switches over all the keywords.

I also can’t get the printer to work.

OK, tiling window managers are neat and so are TUIs, but web pages are also supposed to work with keyboard only. On Windows, F6 will jump between different panels in an application - give that a try.

The key you’re talking about is the menu key, by the way.

Using a modern OS and the modern web with the keyboard only is essentially a solved problem, not only motivated by efficiency, but also to allow access to people with motor disabilities.

But it could limit the usage of its TLD.

There’s a lot to talk about from this point alone, but I’ll be brief: having gone through university courses on processor design and cutting my teeth on fighting people for a single bit in memory, I’m probably a lot more comfortable with that minutia than most; having written my first few lines of C in 10 years to demo a basic memory safety bug just an hour ago, you’re way way ahead of me.

There are different ways to learn and gain experience and each path will train us in different skills. Then we build teams around that diversity.

I said it’ll reduce friction, you said it might be easier. Looks like we’re in complete agreement, right?

I’m working through rust-exercises.com and taking notes on my thoughts. I may or may not want to use it for a short workshop at work - mostly for fun, since I work with a very different stack.

So far, I don’t know if I like the exercises, because the target audience doesn’t feel like it’s clearly defined: you both solve is_even with an if/else and overflow an i8 to -1. I don’t think I’ve met the person who is that inexperienced and that knowledgeable…

How are folks liking these exercises?

To answer the part of your question I think is most fun, there is a standard for SQL. There are many dialects of SQL, but you’ll often hear of “ANSI SQL.” The latest version is SQL:2023.

Looking at the MySQL manual entry for the YEAR type, I think we can conclude two things:

1. The developers consider the possibility of deprecating and removing support for time data type features;

2. They use “reasonable defaults” for conversions of 2 digit years, based on the current year.

The good news is it sounds like this issue is being taken into account. I’m sure the conversion window will be adjusted in future version and the data type may be changed or deprecated altogether. I wouldn’t be surprised if they added a YEAR2 though. T-SQL has a datetime2, after all.