Tesla had invented a kind of two-phase induction motor, but the three-phase induction motor that is the ancestor of the modern induction motors was invented in 1891 by Mikhail Dolivo-Dobrovolsky (working in Germany at AEG), who had also invented in 1888 the three-phase grid, the three-phase generator and the three-phase synchronous motor.
The Dolivo-Dobrovolsky motor is the ancestor of all high-power induction motors, while the Tesla motor can be considered the ancestor of the single-phase induction motors that have been used (more frequently in the past than today) for several household appliances, like washing machines (or reel-to-reel magnetic tape recorders, a half of century ago).
Other way round. He invented the induction motor (1887) which the three-phase grid was then demonstrated to drive (1891). That's how influential it was. There are other reasons a three-phase grid is handy but being able to drive these brushless contraptions must have seemed utterly wild at the time.
A three-phase grid cannot drive a two-phase induction motor, like that invented by Tesla.
In 1891, the three-phase induction motor was invented by Mikhail Dolivo-Dobrovolsky, combining the principles of the three-phase synchronous motor previously invented by Mikhail Dolivo-Dobrovolsky with the principle of the induction motors invented by Nikola Tesla and Galileo Ferraris.
Like any inventions, the induction motors of Nikola Tesla and Galileo Ferraris had not sprung out of nothing, but they were based on the experimental observation that had been known for many decades that if you rotate some magnets around a disk of copper, the disk will rotate, even if the magnets do not have any action on the disk when stationary.
Because of the symmetry, it is easier to generate electromechanically three-phase currents than two-phase currents where the phase difference must be precisely of one right angle.
Rare earth magnet motors require software too if you want them to be maximally efficient. You could embody that software in e.g. an FPGA of course, but it's still software.
I thought the same thing when I started using locals, but the reality is that - for a given context depth - the token generation speed doesn't change whether it's 128 or 8000, it just lengthens the benchmark run time.
$1,500 across multiple models to compromise one app is interesting only when the cost basis includes the human time to set up the harness. The token spend is the cheap part. The labor cost to write the eval rig that knows what "successful exploit" looks like is what determines whether this scales as a discovery method or stays a one-off.
The “massive files” problem is very real. Agents need architectural pressure before they start coding, otherwise they optimize for completion instead of maintainability.
reply