You are very polite to use the word "quirks". I have a little knowledge about coding, still I was on the verge of giving up AE scripting several times. Despite the fact that I consider javascript a mess compared to a decent scripting language like Python, using such a language for anything else than web dev indeed a "very poorly chosen option" (I try to keep the polite attitude going) I managed to set up a PyCharm based environment, with a grunt task runner to concatenate different files. I also put some "node.js" features like require or module.export between two specific comments, which grunt takes out before concatenating so I can write test with mocha. I build a library of pollyFills to add the many missing features of the language, which "is based" on ECMA-262, without anybody telling you that based doesn't mean included. Vital things like indexOf or Object.keys() are missing and many more. There is no (or maybe I couldn't find anything except Peter Kahrel's guide) decent Adobe issued documentation regarding the UI. The Script Editor is a mess.(This is why I had to invent the PyCharm solution. webStorm would be better I think, but this is what I have at hand right now.) Finally, in terms of tutorials and support for this crucial enhancement, all you can find are your tutorials, which are wonderful, but should have been done by Adobe first, and only after have user tutorials for more specific situations. To conclude, when you request such an amount of money for your products, you break backwards compatibility every year to squeeze money from your users pocket or you move your app online, because it's obvious the squeezing gets even better, "quirks" is definitely a very gentle word, but it fits perfectly someone so generous to offer his time and knowledge to other as yourself.
... View more
AdChoices