It’s already a reality, I was doing it about ten years ago.
require.js was a big piece of the puzzle, allowing the use of modules in browser without a build step.
The only time a “build” happened was to concat/minify scripts for production release, but even this wasn’t strictly necessary.
There were other pieces involved, but we had a powerful stack (aforementioned modules, css preprocessing, reactive templating) that had a faster and easier workflow than anything happening today.
I don't know anything about modulating LEDs, but could that high freq. have anything to do with the quiet but audible whine I hear when the light is on? Seems like it could be 8kish.
There isn't any ballast to speak of in essentially any LED driver topology, certainly there isn't any inductive component that is used for its reactance as part of the working principle (which is what "ballast" means).
LED driver might have some kind of LC filters on its power input for EMC reasons, but these are too small to meaningfully "sing". On the other hand it may make sense to follow the driver with some kind of reconstruction filter to remove the "high frequency" flicker, but AFAIK nobody does that because it involves costly and large-ish components with significant losses for somewhat questionable benefit.
Wouldn’t a boost converter from LiPo to voltage needed to run a string of series LEDs have an inductor? That seems a common design pattern. It’s arguably before the LED driver chip but a meaningful part of the overall design.
The idea of impossible fingerings is ambiguous - I can play that D minor voicing in that position as 2 - 4 - 4 - 3. It'd be interesting to see if you could take a set of samples from the user first and apply that to your algorithm. Also useful would be something that purely takes a set of pitches as input, and produces fingerings with the same pitches across various fretted\open strings (and possibly allowing for octave transposition).
This is the problem with "knowledge by web article" in general, isn't it? Blindly following best practices, rather than developing any true understanding of the task at hand.
I consider Babel a trusted source. I prefer to transpile the code by Babel instead of using 15 libraries developed by one person. Also, I can remove some transpilation plugins as soon as the browsers implement it
require.js was a big piece of the puzzle, allowing the use of modules in browser without a build step.
The only time a “build” happened was to concat/minify scripts for production release, but even this wasn’t strictly necessary.
There were other pieces involved, but we had a powerful stack (aforementioned modules, css preprocessing, reactive templating) that had a faster and easier workflow than anything happening today.