If one does Angular, one does it the Angular way, typescript and all. 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 On Thu, Jun 22, 2017 at 3:38 PM, andrew glynn <aglyn...@outlook.com> wrote: > I was wondering: > > a) I'm assuming PharoJS would be much like Amber but inside the Pharo VM. > > b) How much of the Amber codebase could be re-used for it? > > I'm interested on the one hand, mainly due to the demand for Angular code > in the browser (jQuery is great in Seaside, but many clients are looking > for Angular recently), and my distaste for debugging JavaScript. Amber is > ok but lacks the depth of tooling in Pharo, and isn't keeping up with the > (constant) breaking changes in node and NPM. (Not that I blame the > developers of Amber, it's a problem with the mindset of the developers in > the JavaScript ecosystem - the way that Angular2 is almost completely > different from Angular is an example of the lack of interest in the > existing user base). > > The problem I see is that PharoJS would have the same issues. As a result > it would not only be a fair amount of work to accomplish, it would be far > more to maintain. The Pharo ecosystem is based on an entirely opposite > mindset to the JS ecosystem - a few very good frameworks and a reasonable > number of very good libraries, resulting in highly maintainable code even > on projects with only one or two developers. On top of that it would have > to deal with the issues with JS itself that make writing decent tools > virtually impossible. > > Andrew Glynn > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf > Of pharo-users-requ...@lists.pharo.org > Sent: Thursday, June 22, 2017 8:41 AM > To: pharo-users@lists.pharo.org > Subject: Pharo-users Digest, Vol 50, Issue 108 > > Send Pharo-users mailing list submissions to > pharo-users@lists.pharo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.pharo.org/mailman/listinfo/pharo-users_ > lists.pharo.org > or, via email, send a message with subject or body 'help' to > pharo-users-requ...@lists.pharo.org > > You can reach the person managing the list at > pharo-users-ow...@lists.pharo.org > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of Pharo-users digest..." > > >
