TinkersW

Oh my bad, I read that as nullptr, I use a custom optional that does not support such a silly mode as "disengaged"

That is actually memory safe, as null will always trigger access violation..

Anyway safety checked modes are sufficient for many programs, this article claims otherwise but then contradicts itself by showing that they caught most issues using .. safety checked modes.

Error Log/assertions prints are by are the most likely code to have not been run prior. Some compilers type check printf, but not all.

Good article, but for profiling you are missing the big daddy of them all, Tracy.

I my experience you absolutely must have type checking for anything that prints, because eventually some never previously triggered log/assertion statement is hit, attempts to print, and has an incorrect format string.

I would not use iostreams, but neither would I use printf.

At the very least if you can't use std::format, wrap your printf in a macro that parses the format string using a constexpr function, and verifies it matches the arguments.

My understanding is Rust compiles each crate in the same way C++ compiles each .cpp file, so if you stick everything in a single crate you get horrible compile times.

This does seem like a poor design decision by Rust to me, forcing people to break things into arbitrary crates just to get reasonable compile times.

It also seems like a disaster for incremental compilation.

The android team wasn't comparing like to like, though people seem to gotten the impression they were.

OpenAI appears to have bought the DRAM, not to use it, as they are apparently buying it in unfinished form, but explicitly to take it off the market and cause this massive price increase & squash competition.

I would call that market manipulation(or failure if you wish)--in a just society Sam Alton would be heading to prison.

FEX is a CPU JIT, so your GPU settings are irrelevant to it, it is translated but not by FEX, and there is no real perf hit for the GPU

The old games don't really matter with regards to FEX perf, so the only relevant bit is the semi newer games at 30/40 fps, which seems very slow to me, given that you are only running at 1080p/Medium, so you likely have a CPU bottleneck there.

One other accident that was similiar, but these planes have had a ton of crashes for other reason.

I am surprised Intels server chips can only do 2 AVX512 ops per cycle, that is rather sad given how long they have supported it in server chips, and I hope isn't a sign of things to come with Nova Lake.

Nova lake looks potentially pretty good, AVX512/APX and very very high core count, so maybe we will see AMD have some competition next year.

The article is simple wrong, dithering is still widely used, and no we do not have enough color depth to avoid it. Go render a blue sky gradient without dithering, you will see obvious bands.

The python example looks fixable with a reentrant mutex, no idea if that translates to the Rust issue.

Ya ever heard of this thing called a debugger? They have this amazing ability to show you what the problem is right when it happens!