The reason I gave a specific use-case is because in this use-case, it does work like that. I did not give a use-case which had RF signals, large currents, or much of anything else. I2C "fast mode" is 400 kbit/s.
The reason things like STEMMA work is because everything is slow enough that parasitics don't matter, and power is low enough that voltage doesn't sag. The lumped element model is nearly perfect there.
Even many domains not like that -- let's say audio -- have a lot of places where abstraction break, but where those failures are well-contained. An audio amplifier might have 50MHz gain-bandwidth, and the layout around it needs to be pretty tight, but once that's a block, things matter a lot less. That's why you can have all sorts of analogue synthesizers where people plug blocks together. A qualified engineer needs to design those blocks, but connecting them, abstractions hold pretty well.
No one will design an oscilloscope or a software-defined radio front-end using React for Circuits. However, as much as those occupy a lot of engineer time, they're actually in the very tiny minority of boards people want built. Most things are pretty simple and dumb.
Heck, even many high-performance designs have simple stuff around them. If you're making a radio receiver, the RF might be voodoo, but you know what's not voodoo?
- The controller for the buttons and the seven-segment displays
- The battery charger / monitor circuit (at least as a block)
- The USB-to-RF232 converter for development (at least as a block)
- The power, temperature, and other monitors
- The neato audio spectrum bar display
- The bass/treble filter (at least as a block)
- A lot of the test fixtures needed to test the RF equipment (not all; a lot of the other test fixtures are deep voodoo; it depends on what you're testing)
The reason I gave a specific use-case is because in this use-case, it does work like that. I did not give a use-case which had RF signals, large currents, or much of anything else. I2C "fast mode" is 400 kbit/s.
The reason things like STEMMA work is because everything is slow enough that parasitics don't matter, and power is low enough that voltage doesn't sag. The lumped element model is nearly perfect there.
Even many domains not like that -- let's say audio -- have a lot of places where abstraction break, but where those failures are well-contained. An audio amplifier might have 50MHz gain-bandwidth, and the layout around it needs to be pretty tight, but once that's a block, things matter a lot less. That's why you can have all sorts of analogue synthesizers where people plug blocks together. A qualified engineer needs to design those blocks, but connecting them, abstractions hold pretty well.
No one will design an oscilloscope or a software-defined radio front-end using React for Circuits. However, as much as those occupy a lot of engineer time, they're actually in the very tiny minority of boards people want built. Most things are pretty simple and dumb.
Heck, even many high-performance designs have simple stuff around them. If you're making a radio receiver, the RF might be voodoo, but you know what's not voodoo?
- The controller for the buttons and the seven-segment displays
- The battery charger / monitor circuit (at least as a block)
- The USB-to-RF232 converter for development (at least as a block)
- The power, temperature, and other monitors
- The neato audio spectrum bar display
- The bass/treble filter (at least as a block)
- A lot of the test fixtures needed to test the RF equipment (not all; a lot of the other test fixtures are deep voodoo; it depends on what you're testing)
- Etc.