Interesting read daniel.haxx.se/blog/2026/05/…

Which will you go for? First off, did you know .windows(size) exists? Link to a detail explanation of `.windows` is in the comment. You'll be able implement your own version after reading this article.

Sometimes a question can be so simple you'll think it's a trick question. Saw this on YT short youtube.com/shorts/cPmknFpOl…

Here is a more correct diagram and code illustration showing the pointer and variable has distinct addresses, thanks to @isocroft 🙌 who helped clarified this. But the claim is still remains though.

The name of the array in C is a pointer to the first item in the array. I find this behaviour very confusing, what is the purpose?

C feels simpler here. Only thing that trips me off is how scanf uses `lf` precisely for a double while printf uses `f` for either double or float. Rust lets you always read a String first and then .trim().parse::<f64>().

Rust forces you to accept string input and then parse it to whatever-type. In C, scanf directly reads formatted input into the expected type. C is simpler on the surface but will require much more extra effort to avoid unexpected runtime error.

One of my very first C code in comparison to Rust. I plan to write a Rust version of every practice problem. Rust doesn't allow implicit type coercion, C does.