It is pretty much what Suleyman describes in The Coming Wave as one of the measures we need to take to contain the risks of AI.

What Dario does not mention is that concentration in a few states or companies also poses a risk.

AI generated? The humanity!

> I figured out what would be a reasonable amount to spend on the project and then multiplied that by 10.

I like the way you think.

Jeff Atwood has a great quote:

"I needed to replace 18 lightbulbs in my chandelier. Turns out 18 times any number is a lot. In cash"

> So if you were to use the CLI to perform a review of some code. This tool would allow you to loop the output of the code review 5 times onto itself.

Claude already does that if you ask nicely.

To a certain extent, yes it does! For my cases, I'm often running 3 parallel implementations that get 10 to 20 iterations deep, and then Claude has to sort out the pros and cons of the options and also take the best bits of each. Easy to hit the context window with Claude just running those on its own, so giving `/cook` to Claude, it can offload a bit more via cook and stay higher level.

For those OOTL https://www.youtube.com/watch?v=MpmGXeAtWUw

My hero!

How does the "scale plan" work and how much is it?

Where is part 2? :)

You should take a look at Andre Michelle's work. https://www.audiotool.com/

audiotool is made with Flash. And a good demonstration of the actual usefulness of Flash to develop complex applications that could be deployed online. Too bad Adobe was incapable of taking good care of that product and didn't listen the community. I'm sure WebAudio can get better, but the OP's demo still proves that it's brittle. Changing anything in the patterns stops all sounds and the sequencer has hard time keeping a consistent tempo. I'm sure it will get better but Flash was really in advance for its time as audiotool demonstrated. Well, at least now people have stopped complaining about Flash "killing their battery". They can now blame Javascript /s

the fluctuating tempo is due to a poor approach of OP and proves or disproves nothing regarding web audio. that stuff can be as steady as you want.

This is the approach to scheduling I used if anyone is interested: https://www.html5rocks.com/en/tutorials/audio/scheduling/

I also tried to minimize any visual events that cause a repaint on the main instrument screen.

I've found that a steady method for timing is by calculating the number of samples to render per "tick" and decrement the counter after each completed sample when rendering audio to the buffer in JavaScriptNode/ScriptProcessor. Eg.

samples_to_tick=Math.floor( (125.0/bpm) * (1.0/50.0)*sampleRate );

Upon the counter reaching zero, the render loop actually jumps to do sequencing and effects/modulation and then resets to counter.

In my case, the tick occurs at 50Hz because that's the PAL frame clock used in Amiga and MS-DOS module trackers like Scream Tracker and FastTracker 2. Typically trackers use a "speed" setting to additionally specify the number of ticks per pattern step - usually 6.

Although you do get sample-accurate timing, you also get latency up to the size of a single audio buffer (I use 4096 samples). While this isn't really an issue when doing purely playback, it obviously is when the audio is controlled real-time (eg. MIDI).

Anyway - the module player is at http://mod.haxor.fi/ and the source code at https://github.com/jhalme/webaudio-mod-player

The tempo does not fluctuate on my setup. That is something I really tried to eliminate. Can I ask what browser, OS and computer spec do you use?

Just a hint: you can set your player's colour.