So it was very much a complex infrastructure that never was able to update to match what the ecosystem was providing. So, eventually, Cordova kind of became a victim of its failure to update. And it really just was not a good time. If you're doing anything in Cordova now, I highly recommend that you don't. Upgrade the capacitor after this.
Now, what was interesting about Cordova, and some things that I think they had that were pretty interesting, was, again, the web was their main goal. They wanted to just be a giant polyfill to bridge the gap in what the browser was doing. The gap in what the browser could do and what native could do. They really didn't want people to know about a native IDE, which, as somebody who's primarily a web developer, every time I have to open up Android Studio, I kind of get afraid a little bit because Android Studio is very complex. Same thing goes for Xcode. It can be a very complex tool and a very confusing tool, so I think them having the idea of let's go ahead and abstract that away was a good attempt and a good goal, but implementation left a lot to be desired. And then native projects has a DIST target, meaning that your native project should be something that can be configured through tooling and then if, for some reason, you upload it to version control and then your co-worker had to clone it and set it up again, they should be able to get the same steps and get the same features and enablements, like accessing file system in camera, that stuff should be scriptable. How successful they were in that kind of depends, but it was an interesting idea at the time. But it's definitely hindsight's kind of 2020 when you think that this definitely did not work out 100% well, but at the time it was the best that we probably had.