Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Powerscript vs C#

  1. Misc
0
Votes
Undo
  1. Armando Rogerio Brandão Guimarães Junior
    Armando Rogerio Brandão Guimarães Junior
  2. PowerBuilder
  3. Friday, 31 January 2020 04:06 AM UTC

Will powerscript die and be replaced by C#? 

  1. C#
  2. PowerBuilder
  3. PowerScript (PS)
Make Simple SQL Dropdown Without DataWindow Like C...
Suggestions
Accepted Answer
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 31 January 2020 06:04 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Armando,

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.

Best regards,

Armeen Mazda
CEO, Appeon

 

Comment
There are no comments made yet.
Responses (4)
Ricardo Jasso
Ricardo Jasso Accepted Answer Pending Moderation
  1. Friday, 31 January 2020 17:44 PM UTC
  2. PowerBuilder
  3. # 1

Armando,

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.

Regards,

Ricardo

 

Comment
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Friday, 31 January 2020 16:05 PM UTC
  2. PowerBuilder
  3. # 2

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)
  • TypeScript/JavaScript with HTML5+ for addittional UI scenarios
  • 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

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 31 January 2020 04:34 AM UTC
  2. PowerBuilder
  3. # 3

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.

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 3 February 2020 05:07 AM UTC
Haha, thanks for the upvote !

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.

Cheers
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 3 February 2020 17:59 PM UTC
Ahhh.. the good old days of NCR's NEAT/3 compiler ...

Enter Language A

// CodeA....

Enter Language B

// CodeB...

Enter Language C

// CodeC...

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



  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.