Hi Ricardo;
=> PowerScript is one of the competitive advantages of PowerBuilder against other tools. It’s simple to learn, simple to use. And with the help of the IDE it makes object orientation easy to implement.
Absolutely ...
1) Visual Inheritance
2) Save & Go compiling & debugging (no incremental compiling).
3) Application Profiling built-in
4) Supports Property programming (which PB.Net does not).
5) Supports all the primary OO concepts (just needs parameterized constructors)
etc, etc.
The other major concern I have (looking at this as a long term IT person) ... languages come & go. God knows I have seen a plethora of these since starting my IT career on mainframes => mini's => PC's => Cloud => ?! My worry would be for example .. "What if tomorrow MS now standardizes on F# vs C# or some other new passing language fancy"? Staying in pure PowerScript future proofs your application's ability to continue.
Now, some improvements to the PowerScript language should be done - but, keepingPowerScript front & center (IMHO) would be an asset ... even in Armeen's new PB product.
What does everyone else think?
Regards ... Chris