Computers and Creativity
mollymielke.com
mollymielke.com
This is amazingly wrong. DAWs are notorious for imposing a specific workflow, and users will select a DAW specifically for some new workflow it has produced. For example, Ableton rose to prominence largely due to its unusual alternative workflow option (the grid) which made it popular on the DJ scene. Other DAWs have workflows and tools which make them popular with composers (Cubase for example) or tinkerers (Bitwig, Reason, etc.).
It's an old problem within software itself and not really addressed until the individual puts their foot down and says, "This. This is the medium, these are the restrictions, this is the way I structure everything." At that point it's possible to define perfect software, but we're too fickle to really get there.
Reason + Cubase linked together was a lot of fun :)
That's spectacularly wrong. The core workflows (sequencing, editing audio, mixing, etc) are similar in every DAW because that's their inherent nature, nor because they're somehow imposed upon users.
The only major different paradigm was Live, which, as it name implies, offered a "live clip launching" way of interaction. But that's not about "imposing a strict workflow" it's about supporting a different use case or not. In other words, it's like there were editors for programming, and someone went and make an editor optimized for live coding. And even that, is offered in several DAWs, including BitWig, FL Studio, and even Logic.
The core workflow itself (which involves sequencing, editing audio, mixing, etc) has 100s of ways it can be mixed/matched/customize/performed differently within the same DAW.
The Association for Computational Creativity is holding its 12th annual conference this year, and this reads as if the author has never heard of them.
I almost LOLd when I read that "no tool exemplifies moldability better than music digital audio workstations." DAWs are the antithesis of moldability. They force you to think of audio in the same way that a 70s/80s studio engineer thought of audio, but with time-saving virtualisation and automation. They're almost entirely closed to any context-aware semantic editing or creation.
So... superficially researched, and not an inspiring piece.
> However, a new way of thinking about these machines began to emerge in the late 1980s. From the punch card came the spreadsheet
Spreadsheets were in no way derived from punch cards (except in the sense that everything was), and the first widely used spreadsheet, VisiCalc, was developed and released in the late 1970s.
> Collaborative software as we know it was born soon after in the form of Google Sheets, the first simultaneous multiplayer software.
What?
- Yeah, DAWs suck, poor example, let's ignore this.
- The title is probably not very well chosen, as some other commenters highlighted by focusing a lot on creativity on itself. The actual piece seems to try to focus more on making computers better platforms for the practice of creativity, not so much about the creative limits of computers on themselves.
- This is a technical crowd, and the piece is more about "what would be nice", so no point bothering that much on technical issues.
I actually agree with the main point, but indeed, just saying "what would be nice" is not that helpful. For the point on standarization, I think a better, more technical and actionable framing, would be to try to port the concept of type safety from languages to specs and APIs. While there's some kind of informal consensus on the main types that are used everywhere, if we could (yeah, this is a massive leap, but I'm only trying to illustrate the idea) pass "specs" into functions in type-safe languages, just like we can pass complex functions as parameters in many modern languages, and we could automatize to some degree compliance and testing, that would be awesome. So, not so much about standarization, but about a new abstraction level, making the interoperability of computational systems type safe. I think about something as common as urls, and I tell to myself: this is such an unsafe mess. Even if a spec is technically well defined, translating that into code is too much.
The other general point, moldability, might be better expressed as "accessibility". Making systems more accessible to users. But I think besides many poor software tools made in a rush for specific interests, we are already doing decently here when we really try. It's only that big companies that make the big products usually have too much inertia to continue doing certain things the same way they have been done in the last 40 years (most DAWs are a good example as many commenters pointed out), and smaller actors don't have enough resources to make complex tools that are much cooler than what we have. But on this aspect, I don't think the obstacles are that significant.
Oh, and on a final note, nice writing (even if it wanders a bit too much sometimes) and really beautiful design. Even the html is pretty readable.
It takes multiple years of focused effort to get good at the other skills involved in using a tool.
And it takes no small amount of investment of time and energy to get to the point where you have the programming skills to modify the tool.
Plus of course the inner calculations of "will trying to modify this thing be likely to find any success before I have spent more time trying to hack it than I will ever save by doing this" need to at least look like they will come up favorably.
I mean, someone in the community is probably gonna have that combination, this past month I've been looking at picking up Adobe Animate for the first time in like 15 years to do some animation, and I went looking for plugins for it and found a few paid plugins made by a dude who started working in the animation scene around the same time I did, and never left it; this man has clearly found a lot of pain points in the process of cranking out the footage in Flash/Animate and built plugins to fix those holes long before Adobe could be bothered (and it sounds like there are a lot of unlicensed copies of his plugins floating around studios, too), and if I find this one animation gig I'm being coaxed out of retirement to be enough fun that I wanna take a few more, you can bet your ass that I'm gonna give this dude like sixty bucks for his well-polished patches in Adobe's UI rather than spending the time getting up to speed on making Animate plugins.
And this is coming from someone who hangs out on HN and has a tidy little collection of homebrew scripts for Illustrator, the art tool she spends most of her creative time in.
Flash was always kind of a big pile of shit, while at the same time being the least shitty thing available, and it seems to have maintained that status after fifteen years of development while I was off mastering Illustrator. It is the devil I halfway know, and am already paying for with my Adobe subscription, vs. the mystery of shelling out for Toon Boom and starting from scratch on it or trying to learn Blender's weird 2d workflow or something. You should look at animation tools that aren't Animate. :)
[1] https://www.maa.org/press/periodicals/convergence/mathematic...
Huzzah!! Yesss! Sing it loud. There's other who believe similarly. The Malleable Systems Collective[1] for example! From their opening words:
> Modern computing is far too rigid. Applications can only function in preset ways determined by some far away team. Software is trapped in hermetically sealed silos and is rewritten many times over rather than recomposed.
This idea/aspiration of ever-enrichening imminently-flexible ecosystems is mirrored in my reply to the recent The Dispassionate Developer[2], where I argue my hopes that systems be more open ended & allow more people access & participation.
It just feels so cheap, that negativity is so free, that snark is just seems overflowing in most comments, and that's what seems to attract support. Like the case here, I want to see a more open, unlimited mentality. Instead it just feels like everyone's looking for fuel to burn.
If you started this with a more neutral "I loved this!", that would serve as a warning for "passionate, high energy comment incoming", and people would know to skip if they weren't looking for that. Simply, your signals are too confusing in this context.
Edit: wow, rereading this it sounds quite harsh, almost as if I was making a moral judgement here. Not my intention at all, I was just trying to add some perspective.
https://www.egreenway.com/taoism/ttclz41.htm
AKA "Don't let the turkeys get you down."
Those ideas inspired the making of the first personal computer btw[2]. [1]https://ia801707.us.archive.org/29/items/illich-conviviality... [2]https://en.wikipedia.org/wiki/Lee_Felsenstein#Life