This is exactly what I have wanted for a while, so thank you very much!
Disclaimer: I haven't dug into axe enough yet, just going on first impressions.
>No daemon, no GUI.
I love the world we developers live in right now. ;)
>What would you automate first?
In a sense, I have wanted to be able to just add AI to a repo, and treat it like the junior developer it is. Its okay if the junior developer will do literally any stupid thing I tell it to do, because I won't tell it to do stupid things.
So, exactly: refactor this code, implement a shim, produce docs for <blah>, construct a build harness, write unit tests, produce a build, diff these codebases, implement this API, do all this on your own branch, and build and test things so that I can review the PR over coffee.
Essentially, three word commands which will encourage the AI to produce better software. Through my repo, so I can just review through the repo.
Okay, that's how I hope things work, now off to actually dig in to axe and give it a try on a few things, thanks very much again ..
It sounds different but it is great in its own right and priced adequately to how amazing it sounds. Maybe 'alternative' is a wrong word. I think I meant 1:1 replica.
Also it doesn't come with ring modulator nor ribbon. I think black corp synthesizers are inspired by the original vintage devices and are great on their own but there are justified reasons to also avoid them mostly because of common issues that arise when you buy a niche product from a tiny company thousands of kilometers away.
>common issues that arise when you buy a niche product from a tiny company thousands of kilometers away.
Sorry, this is just negative - but anyway, have you played with both?
I have. There are differences but they are minor and you can very definitely accomplish an approximation of the CS80 'sound' with the DD. It sold out for a reason.
Either way though, if you have an opportunity to have a real CS80 in the studio, as I do, you are very right in saying that it is an amazing beast.
Native builds are always a safer/more reliable path to take than cross-compiling, which usually requires solid native builds to be operational before the cross environment can be reliably trusted.
Its a bootstrapping chain of priority. Once a native build regime is set in stone, cross compiling harnesses can be built to exploit the beachhead.
I have saved many a failing projects budget and deadline by just putting the compiler onboard and obviating the hacky scaffolding usually required for reliable cross compiling at the beginning stages of a new architecture project, and I suspect this is the case here too ..
I last used this menu about 20 years ago when a dialup modem was the only way to roll, and have pretty much forgotten about it since the days of always-on direct to the desktop TCP/IP ..
The purpose of scaffolding is to create persistent memories.
>claim "persistent memory"
Just look at it as a build product.
>abstractions that don't work
Look at this as a testing problem.
reply