Looking at the ONSemi datasheet for the BS170, it is very clear that the "Drain−Source Breakdown Voltage" spec only applies at "VGS = 0, ID = 100 uA DC".

Doesn't it cause problems for designers if the curves measured from actual devices look different from those shown in textbooks?

Not as much as you'd think, because (a) the measured curves are still within the stated parameters, and (b) many basic parameters vary from one part to the next (or as the same part drifts over time) even more.

Look at the values of V_GS used in the graphs: [2.34, 2.5, 2.63, 2.71 V]. They differ by 0.4 V. But the data sheet specifies V_GS(th) (the V_GS threshold needed to just start to turn on) as a range of 0.8 to 3.0 V!

A range isn't even given for the slope of the curve (g_fs). The datasheet only gives a "typical" value at a single operating point.

So the designer cannot rely on this parameter to determine the behavior of the circuit, only its general range and direction. You can't just use the bare transistor alone and expect to get an oscillator or amplifier that behaves predictably.

Any manufacturable circuit must ensure that these variations are completely dominated by negative feedback. This is why actual circuits tend to have networks of resistors and capacitors hanging off of every leg of every transistor.

I think that counts as "cursed" from a design-for-manufacturing perspective.

"After a production run of 12,000 units the TR-808 was no more." https://secretlifeofsynthesizers.com/the-strange-heart-of-th...

That's usually the case for Rust programs because the language encourages it. Are Zig programs like that?

Does the program handle character data? It is indeed a rare server app which never handles strings.

It's the manufacturer's fault. Because that's not a reasonable thing for a car to do.

The answer looks entirely reasonable. I can't check the Android settings, but I was able to confirm that all of the suggested iPhone and Spotify and settings exist. Most of them I had already configured that way, some I didn't know about before.

Don't get me wrong - I personally "trust" an LLM as a source of facts about as far as I could throw a rack of GPUs. But this article you linked takes a whole lot of words to cast LLMs as the villian for amplifying a bit of bad information originally published by a usually reliable and widely-cited source:

"In short, either Phoronix mocked up the screenshots to demonstrate what the feature could look like, or perhaps they were testing a preview snapshot for FreeBSD 15.1 which was never shipped. Either way, it looks like other blogs and reviewers picked up on this and shared the information, presenting it as a feature which would be (or was included) in FreeBSD's latest version."

Cf. https://machinelearning.apple.com/research/illusion-of-think...

For example, consider the term "short wave" radio which refers to wavelengths of at least 10 meters. Today's mobile communications use wavelengths 100x - 10,000x shorter.

https://knowyourmeme.com/memes/my-father-in-law-is-a-builder...

Imagine growing up in Cairo.

Does anyone have an actual estimated time we can discuss?