Strudel is dope and a ton of fun, but every single piece of its interface seems determined to confuse people who already know music theory and composition.
That's not really a point against it, it's a great tool and it's a ton of fun, but I wish there was a way to use it that at least kind of sort of mapped back to traditional music notation, especially rhythm notation.
It would be unergonomic, if not painful, to use a western classical approach to rhythm in a programming environment. Alex McLean, the main author of Tidal/Strudel, is very much into Indian classical, and this is reflected in the approach to rhythm. IMO this is an good choice, and people who know music theory and composition should feel right at home, assuming we're talking about the right theory.
When it comes to pitch (and I guess we agree on this) Strudel is firmly on the western traditional side. It generally assumes 12-tone equal temperament, uses ABC notation, has built-in facilities to express chords using their classical names...
Meanwhile I'm over here programming music where I express all frequencies as fractions or monzos. I find this better suited to a music programming environment, but this might be more personal.
I vividly remember the first time a friend showed me PHP in the late 90s. You're saying I can just write a script that generates HTML and throw it in /foo/index.php and that's the whole thing?
It's wild that right up until Rails got popular, we were writing code that served billions of requests off of homebrewed MVC-ish PHP frankenframeworks.
Cheetah was an earlier (and dumber) version of this model that we used to test production speed. They are both developed in-house. If you liked Cheetah, give this model a try.
This is nice. I liked Cheetah for grunt work that I want to get out quickly and is not too hard. The speed is really awesome. A model that would run at even higher speeds like the OSS models at groq/cerebras would really be workflow changing, because the slowness of SOTA models really breaks the flow. I find myself taking a ton of breaks and getting distracted while I wait for a model to complete a task (e.g. just now).
Awesome, thanks for the clarification. So are the rumors around Cheetah being based on a Grok model just straight up untrue? I want to try Composer but have a pretty strict no X/Grok policy.
Wouldn't you be able to pedal at your most efficient rate, and go at whatever speed you want? Like how diesel-electric trains don't actually drive the wheels with the diesel engine, they power an electric motor.
(I've never ridden any kind of e-bike so I don't really know how it works)
Bikes have very efficient transmission systems, so outside of extremes you can pedal at an efficient amount of torque for the rider regardless of say: hitting a big hill. This is doubly so for e-bikes that assist in the pedaling.
This is more akin to a hybrid car, who's gas engine could generate electricity, but in the case of this e-Bike from Rivian, why would you do that? The electric motor is significantly more powerful than a person's legs, outside of the Pro Peleton.
Watch anyone on a Class 3 ebike: they're not pedaling. The bicycle drivetrain is just there to get around regulations, like having a license.
Rivian isn't known for making hyper-efficient electric vehicles. Rivians are MANLY trucks made to do MANLY truck things, like go fast! and go through tires faster!
Trains and large trucks use this setup because a mechanical gearbox would need to be enormous to withstand torques they produce. Bikes don't experience even moderate torques so they can be equipped with 10-20 geared transmissions, which weight under 1 kg.
On my e-bike, with just a standard 7-speed transmission I can pedal at my most efficient rate always; since I have an extra 300W of power available I don't need the super-low gears for climbing.
> I assume there'd be a big single rectangular bounding box or sphere, and only once a projectile is in that range, then animations occur.
Now that's a fun one to think about. Hitscan attacks are just vectors right? So would there be some perf benefit to doing that initial intersection check with a less-detailed hitbox, then running the higher res animated check if the initial one reports back as "Yeah, this one could potentially intersect"? Or is the check itself expensive enough that it's faster to just run it once at full resolution?
This is the basis for basically every physics engine in some form of another. Collision is divided into the "broad phase" pruning step that typically uses the bounding box of an object and a "narrow phase" collision detection step that uses the more detailed collision primitives
This kind of exploratory/creative programming is bar none the most fun you can have as a software engineer. I love reading write-ups about projects like this because you can practically feel the nerdy joy radiating off the screen.
Plus the translation issues, where you can have an absolute sledgehammer of a haiku that would need to be watered down in order fit the "correct" meter in English:
in kyoto / hearing the cry of the cuckoo / i long for kyoto
That's not really a point against it, it's a great tool and it's a ton of fun, but I wish there was a way to use it that at least kind of sort of mapped back to traditional music notation, especially rhythm notation.
reply