Will powerscript die and be replaced by C#?
No, PowerScript is not being replaced! PowerScript historically has been the client-side scripting language for building desktop apps, and it continues to be as such under Appeon's roadmap for PowerBuilder.
In fact, we've made a lot of enhancements to PowerScript features, which confirms our commitment to PowerScript: https://www.appeon.com/developers/powerbuilder-release-history.html and https://docs.appeon.com/appeon_online_help/pb2019r2/whats_new/index.html
Sybase had some failed attempts to make PowerScript also a language for server-side programming on top of the .NET framework... but that is just silly way to do things. Anyway, under our roadmap, C# is the language for server-side programming on top of .NET Core framework (e.g. C# Web APIs).
Hope this clears up any confusion.
C# is a .NET language used for building .NET applications which are based on the .NET Framework, a library of components. They require the CLR (Common Language Runtime) to run, already included in Windows.
So as long as PowerBuilder remains a tool for building native windows applications PowerScript cannot be replaced by C#.
Appeon has added SnapDevelop and several migration tools to its suite of products that allows developers to transport non visual components created in PowerScript to .NET using C# and also to create C# Web APIs. But these new tools do not change the basic way of building PowerBuilder applications so PowerScript is still needed.
I see PowerScript with DataWindow technology continue to thrive in a polyglot environment:
- UI in PowerScript (win-platform directly; web and mobile UI via PoewrServer)
- C# on .NET Core for server-side cross O/S
- Any combo of DBMS you care for giving relevant DB drivers.
- PowerScript also fine for hassle free Windows services without UI.
C# has existed for close to 20 years.
Java for 25+ years.
PowerScript is still great for UI apps.
My 2 euro-cents, /Michael
Good question, though Appeon until now have always stated it won't.
In the long long, very long run, I don't see why it wouldn't.
- Miguel Leeuwe
- Monday, 3 February 2020 05:07 AM UTC
Of course, the main problem with replacing the powerscript language would be that everyone would have to translate all of it's existing applications to use use the .net version. Not very likely to happen, unless there'd be a way to let users choose which language to use (meaning old powerscript for old applications and .net for new applications).
Anyway ... just imagining myself things here.
- Chris Pollach @Appeon
- Monday, 3 February 2020 17:59 PM UTC
Enter Language A
Enter Language B
Enter Language C
That was so ahead of its time!
Same for IDMS. It was coded in ISL (Intermediate System Language). An invention by B.F.Goodrich in London, Ontario Canada. In the ISL compiler, you could say "Output=Assembler" or "Output=C++", etc.
Regards ... Chris
- Page :
However, you are not allowed to reply to this question.