I have noticed a trend with newer JS tooling beyond performance. Indeed, builds are quicker. The cold starts decrease. That’s great. ~
However, the feedback duration is the actual behavior modifier.
My perception map.
Speed test, compilation time benchmarks.
Loop tightness refers to how fast you notice a mistake.
Cognitive load refers to the amount of context you maintain in memory while waiting.
Most developers don't make use of max throughput. They strive to avoid distractions. Tools that are written in faster languages matter mainly because they shrink the gap between action and signal.
Some "quick" weapons stick, that is why. Problems of today often relate to mystery, not slowness.
The rule I abide by now is that if a tool feels calming while debugging, it wins.
Inquisitive.
What tools have made an impact on your daily workflow?
When has hype about performance not translated into adoption?
What is the next bottleneck after speed?
> What is the next bottleneck after speed?
Movable parts / dependencies
LLMs can get you just the functions you need in place of a whole package with 200 dependencies