And this is exactly why KVL is an abstraction of Maxwells equations. It makes things easier while not influencing the result (when used correctly).
Because in many of your "abstractions" you used KVL instead of Maxwell, you think that KVL is an abstraction of Maxwell. Don't say that anymore.
Saying that means that every time you have a problem solvable by Maxwell, you can immediately apply KVL "used correctly" and that's it.
It implies that you can get away without understanding the underlying phenomena. No, you can't.
That's what Cyriel Mabilde disastrously did. That's what Lewin is desperately trying to warn you about.
That's because abstractions also have there limits. So do Maxwells equations when you get down to really small scales where quantum effects take over. You have to know about those limits and simply make sure you don't use that particular abstraction when outside of them.
Why you can get away with that in computing? Because those languages, including machine code, are all equivalent in computing power. So you can get a program working without knowing the details under the hood at the expense of a messy code.
Kirchhoff and Maxwell are NOT equivalent. If Kirchhoff and Maxwell were languages, Kirchhoff would describe a machine with LESS computing power than Maxwell.
In theory yes any truing complete language can do anything.
In practice the capabilities of programing languages vary a lot. Some languages are simply faster to compute a given task, no matter how well you optimize your program (While others complete it with less program code). But there is also certain low level functionality that many languages are simply not capable of. Modern CPUs often have special instructions that most compilers don't know how to use so they don't. There are special locked registers in CPUs that require a sequence of instructions that a lot of high level languages can't reproduce. These special things are usually not something that most programs need to do, but operating systems or hypervisors and such really need it, as they have to do things like set up the MMU, manage execution privilege levels, perform context switching, switch the CPU from 8086 compatibility mode into the full instruction set on boot etc... Normal programs running under a OS also make use of some special features such as JIT compiling where the whole program is basically self modifying code that compiles itself on the fly as it runs by jumping back into the compiler whenever needed. All of this is simply not possible in high level languages like python (Well apart from loading raw binary data into memory and then crashing the program in just the right way that the CPU ends up executing that area by mistake, but that's basically bypassing the language and using a hex editor to program)
This is much how Kirchhoff and Maxwell are NOT equivalent. Kirchhoff can do most things one would normally need to do, but not everything. The things it can do it usually does in a way that is move convenient than the alternative, for the things it can't do then you have no choice but to use the alternative.
Again. Who told you that you could reduce the problem to KVL? Kirchhoff? Certainly not. Kirchhoff is a bird. He doesn't know anything about propagation, delay lines, fields, etc.
You had to use MAXWELL, and you did it almost unconsciously, to reduce to problem to Kirchhoff. So you confirm what I said in one of my first messages on this thread about how we engineers are so used to that practice that we forget that we are in fact using Maxwell and implicitly reducing the problem to Kirchhoff.
You can abstract, but you cannot use this as an excuse to ditch the fundamentals. What people are doing is not even trying to study Maxwell, consequently not understanding what the flux is going on and criticizing Lewin for THEIR ignorance.
This is the most stupid educational move I've seen in decades.
Kirchhoff was not involved in in that phased array. I was making an example why wave propagation doesn't automatically make Maxwell necessary, or even make physics necessary.
I was making use of physics of wave propagation to abstract the problem down to just geometry. Waves traveling in a constant uniform medium always travel at the same speed, this leads to a conclusion that the time delay from the transmitter to the receiver is only a function of distance. With that i can craft simple factor to multiply with in order to translate distance into time delay. With this number in hand i can then predict the waveform this element will receive and feed that on into the phased array beam steering math. No physics involves what so ever, only geometry.
The results it gave matched up with other tools and with experimental results.
You only have to understand enough of the underlying physics to determine what abstraction is appropriate (if any). No need to calculate the whole thing using fundamental physics first. The understanding is more valuable than being able to blindly put numbers into famous equations. Sticking numbers into equations blindly without trying to understand what they are is ignorance. Applying understanding of the subject to form a simpler abstraction to make things easier and faster is instead called "getting stuff done".
TLDR.
Now that I've made you a convert, let's help others to avoid saying stupid things like "Physics has no use for Kirchhoffs law since it doesn't deal with anything physical."
I was almost using that quote as a signature. But then I decided to give you a second chance.
Made me convert to what?
Kirchhoffs cirucit laws still are not some fundamental law of the universe or something. Its just one of the sets of laws that make circuit meshes work. I have yet to see Kirchhoffs laws be wrong when they are used as intended. Its a great abstraction that helps you make sense of physical things.
You have demonstrated in the transformer video how useful the circuit mesh abstraction is. Transformers don't have additional winding that make leakage inductance, they don't have a physical resistor inside them that causes core losses. Yet it acts pretty much like that was the case so that's why the real transformer model uses it. It makes things much simpler to work with while acting close enough. You even use such simplifications before you get to the equivalent circuit model. For example you consider two turns in a coil as simply being 2 times a single turn, while showing segments of wire that go up diagonally to connect the two and a set of wires coming out and then showing a voltage across the two wires without closing them into a loop. I'm not saying its wrong to do this, it makes perfect sense to do it, but for these same reasons is why other people had issues with my lumped model of Dr. Lewins experimental circuit. For some reason i was not allowed to insert inductors into the equivalent model and not allowed to have a voltage on a non closed loop wire segment.
Absolutely nothing wrong in that video (Okay maybe apart from the voice)