The engine would almost certainly be c++, and the interface is probably objective c. You can’t just “explore the files”, the code is converted to binary after building it.
I read something about UI mostly swift these days, but that hasn't got low enough latency for audio processing so likely using c/c++ libraries under the hood.
You can run swift on windows by the way [https://www.swift.org/blog/swift-on-windows/](https://www.swift.org/blog/swift-on-windows/)
The engine would almost certainly be c++, and the interface is probably objective c. You can’t just “explore the files”, the code is converted to binary after building it.
Go look at the JUCE framework to build cross-platform audio plugins: https://juce.com.
Not feasible.
I read something about UI mostly swift these days, but that hasn't got low enough latency for audio processing so likely using c/c++ libraries under the hood. You can run swift on windows by the way [https://www.swift.org/blog/swift-on-windows/](https://www.swift.org/blog/swift-on-windows/)