There is little point in doing PharoJS in Angular.
Amber and Angular is also hard to do.
Another issue with Amber is that it "compiles" to JS, and there are a ton of hard to read context handling code (try to debug that in a js debugger... ahah). For a project of mine, I can do it all Amber.
Backend code is another story and frankly, a lot of *paying* customer are not caring about the latest "fad" in SPA/push/reactive/...
A solid app that makes sense in streamlining a process is already heaven, and translates into cold cash.
I am inheriting some code base where I see jQuery, React, Angular 1.x and some custom scripting all mixed up along with npm, bower, yarn, grunt things to do. WTF.
So, customers asking for Angular. Ok, what kind of customers? Business owners? Or IT departments? I am done trying to sell Pharo to IT people.��
We are better off at upper echelons in the food chain. Where there is business value and speed of execution, and tangible results.
I was explaining some reporting code to a Project Management Officer this afternoon. It is Pharo and Seaside. Well, he can actually make sense of what is in the code and can now come back with new ideas for value added features. Just put a halt at a strategic place and was able to inspect key business data interactively.
Try that with any JS code.
Phil