First, "the right approach" to building a software program is wildly unspecified: it could refer to the UI/UX aspects and/or the internal design, and these both have dramatic impacts on long term evolution.
Second: the "right approach" for "making music" in the early days covered things as distinct as MIDI sequencers, trackers and early ProTools. It was far from obvious whether all 3 would continue to exist or some hybrid would become dominant (that's actually what happened - early ProTools did not do MIDI; the eventually archetype for DAWs turned out to be a blend of ProTools and MIDI sequencers, and trackers were discarded).
Third: As I alluded to in my comment here about user groups, the right approach is going to differ for different workflows and use cases. FL Studio is not used by many audio mastering engineers; ProTools is not the choice of beat producers.
Fourth: the goalposts keep moving with increasing compute power. The current idea of infinitely elastic audio that has become common among the most popular DAWs would have been unachievable in the early 2000s. Network bandwidth may have a similar impact.
Fifth: the right approach (especially visible today) for some people who are generally "in DAW space" isn't a DAW at all, but hardware designs that bypass most of the functionality associated with traditional DAW design. The Elektron and similar h/w sequencers of the last 5 years are in some senses closer to plugins than they are to DAWs.
Sixth: plugins - the ones associated with compositional elements (you could say sequencers but it goes beyond that) - have long been where the innovation has been taking place. These have evolved quite differently and more diversely than the DAWs that host them. For many users, plugins are the real workhorses and the DAWs are just the scaffolding around that. It would be hard to take a look at compositional plugins and conclude that the "right approach" emerged early.
> I started thinking about this question, of whether software transitions ever really happen, when I noticed just how common it was for the most popular application in a category to still be the very first application that was ever released in that category, or, they became the market leader so long ago that they might as well have been. The Adobe Creative Cloud is a hotbed of the former: After Effects (1993, Mac), Illustrator (1987, Mac), Photoshop (1990, Mac), Premiere (1991, Mac), and Lightroom (2007, Mac/Windows) are all market leaders that were also first in their category. Microsoft Excel (1987, Mac) and Word (1983, Windows) are examples of the latter, applications that weren’t first but became market leaders so long ago they might as well be (PowerPoint [1987, Mac] is another example of the former).
So in this world at least, the longevity of the first mover has more to do with actual and imagined barriers to entry rather than anything especially good about the software itself (and indeed, many of its users used to complain endlessly about the software).
I think the factor you're missing is path dependence. The approach that becomes dominant isn't necessarily "best", just a stable equilibrium where switching costs are greater than potential benefits for most users. I'm typing this comment on a QWERTY keyboard, but I don't believe for one second that it's the optimal layout - I just can't be bothered to learn Dvorak or Colemak or whatever.
The piece I linked to makes all these points, as well as addressing your others.
Everything is represented as blocks of samples on rows of timelines which are then effected by transforms placed on the rows above the rows containing samples. Edits and transform adjustments all happen in real time, and everything is continuously rendered to a scratch buffer that can also be dragged in to the project as a new block of samples.
It is truly a very creative approach and when you see it you will be wondering why nobody tried this approach before. The developer, Colugo, has a new video on YouTube showing how it’s main features work.
A video about Blockhead (experimental digital audio workstation)
This is why these applications have lifespans measured in decades, and it's extremely rare for a new player to be able offer anything new, different, and valuable because the design space has already been solved for the problems these applications are solving.
I wrote a piece on this subject, e.g., why, how, when software transitions do happen for these kinds of apps: https://blog.robenkleene.com/2023/06/19/software-transitions...