Question Re: what next for Powerbuilder developer -- Java or .net in Technology Q&A

what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 09:44:57 GMT

Hi guys,

I have been working in Powerbuilder tech for last 10 year and now I find myself at a cross road to upskill myself as jobs have dried up in UK for powerbuilder projects. I have got another year before I hit the job market. I am totally confused as which direction should I go. Java world or .net side. Most companies in UK are moving away from PB product and jobs on offer are with little dev work and more of patch work. It looks only dev work happening in PB is in US.

Guys any suggestion will be really appreciated

thanks,

Viresh

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 11:14:45 GMT

Hi Viresh;

This information was just released last week ... TIOBE Index | Tiobe - The Software Quality Company

As far as your IT path is concerned though, I would suggest looking at your local IT job market as each locale will have a different demographic software wise. Also, try and network with IT professionals in your area as well and see what they have been observing.

HTH

Regards ... Chris

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 12:46:16 GMT

My opinion - neither... They're both aging technologies.

Look at Javascript (node.js, Angular, Ionic) or Swift development. Both are positioned for the next wave of innovation. Signup for a trial of IBM's Bluemix cloud platform, and all these tools will be available to you for free.

-Paul Horan-

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 13:46:59 GMT

This is my understanding, if you used PB more than 10 years that means you are a master in programming in general..You need to think really careful before you make a move.. I used PB 15+ years and recently changed my job.. I don't use PB at my new job as of now.. But I read everyday about PB and waiting for official announcement from Appeon.. I am sure that PB will rock the market soon.. That's my hope..

Regards,

Jahir.

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 14:41:14 GMT

Buenos Días a todos

Estamos a la espera de un nueva Version de Power Builder Urgente, la empresa donde laboro esta a la espera, ya el Señor Mazda dio luz verde

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 14:51:11 GMT

Señor Pollach

Bunos Dias

Segun el listado: TIOBE Index | Tiobe - The Software Quality Company power Builder no aparece por ningun lado.

La innovacion de Power Builder tiene que ser pronto.

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 15:26:42 GMT

Sí, me ha sorprendido mucho que PowerBuilder no estaba en la lista, ya sea!

Sería bueno para obtener una respuesta oficial de SAP antes de julio 1 2016 (25 cumpleaños de PowerBuilder) al mover la responsabilidad del producto a Appeon!

Re: what next for Powerbuilder developer -- Java or .net

arnd_schmidt — Wed, 22 Jun 2016 17:14:55 GMT

PowerBuilder is not a programming language.

You also will not find Eclipse or Visual Studio in this programming language index.

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 17:31:43 GMT

I think he meant "PowerScript".

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 19:34:03 GMT

Yes, but PowerScript cannot be considered a programming language in the same arena as the other languages because it is ingrained in the PowerBuilder IDE. One cannot compile PowerScript code without the IDE....for the time being. This will change in the new Appeon version of PowerBuilder which as I understand will allow us to compile PowerScript code outside the IDE.

But even if this happens the important thing to consider is, will PowerScript properties and features be good enough to lure programmers from programming in C, C++, C#, or Java, or from any other language for that matter into programming in PowerScript?

I think PowerScript by itself, (i.e. without the DataWindow), has many interesting properties that can make it a suitable alternative to any of the before mentioned languages, even if one doesn't intend to write business oriented applications. As I have mentioned in other posts, it is clean, easy to understand and easy to program with but still it is object oriented making it a robust language in my opinion.

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 23:34:55 GMT

Hi Ricardo;

FWIW: The batch compiler as far as I understand it thus far, will just be a non-visual part of the PB IDE that allows you to basically deploy a project. In fact, it sounds more like an OrcaScript than anything else. Maybe with some much better ootions. At least that is my impression this far.

I get the impression that this feature comment was directed at PB Shops that were complaining about buying an extra copy of PB just so that they could use it on a dedicated"build" machine.

For luring low level programmers away from "C", Java, C++, etc - that should be easy with a robust set of controls, PowerScript, GUI, DW, etc improvements that are targeted for the business programmer. Also, RAD & productivity features are still key IMHO.

Regards ... Chris

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Wed, 22 Jun 2016 23:54:25 GMT

Chris,

Thanks for the clarification. At this point everything about Appeon's PowerBuilder is still blurred although I have to say we have been given some guides as to where it is heading.

My point is, to program in Java, C, C++ or even in C# you just need in theory a text editor and a compiler.... and a good set of libraries (for example the .NET Framework). In practice of course a good IDE like Visual Studio is welcome specially for building visual stuff but again in theory it is not necessary whereas in PowerBuilder you cannot code without the IDE (correct me on this if I'm wrong) because for starters every object is stored in PBLs which cannot be opened by a simple text editor which in turn then locks the language to the product. Is this bad? Not necessarily in my opinion but it helps explain why we don't see PowerScript in the list of most used languages. The IDE gets old and obsolete, the language follows along.

But I agree 100% in your comments that a robust up to date tool will attract new and past business programmers.

Ricardo

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Thu, 23 Jun 2016 00:38:25 GMT

Hi Viresh,

Sounds like there are many legacy systems end-of-life-ing. You are in exactly the same bind as a lot of us. I asked myself the exact same question five years ago and my bet was on Objective-C and a future in App programming. Before actually learning the new language I found myself back in maintaining a legacy pfc based system to be kept alive for another year or two. Objective-C would have been a gamble for me and I would now have to transition forward to SWIFT which has replaced it.

PowerBuilder; with still unsurpassed datawindow technology; with XML; with WEB Services; with added Appeon WEB and Mobile plus a dose of very positive road map; is the basket I am putting all my eggs in;

The skills you have would not only be PowerBuilder. You would have SDLC. Agile maybe. You are most likely database designer and developer. You would have domain experience. Business Analysis. You probably know how to elicit requirements. Whilst Crystal Reports and Jasper are inferior to the datawindow, you can easily transition to either. If you want to be a lower level programmer; take on Java in your spare time. From job adds you can see the buzzwords. Google them.

Lars

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Thu, 23 Jun 2016 01:06:59 GMT

Correct, PB is not a compiler ... its a development ecosystem really when you think about it.

The PB object source is just that. It's readily available as an export / import via the IDE, OrcaScript or using native source control (my favorite way to keep automatic track of object source).

The main thing to remember is that along with the object source, PB keeps a copy of the compiled object in its PBL's as well. That's why it's always ready to run your applications right after a painter "save" operation. Something that regular compilers just can't do.

Your 100% on the money about the IDE vs Language vs Getting old. It's really Sybase's fault 1st of all trying to convince everyone that we needed a new IDE versus working on adding more .Net features to PB Classic (like WCF) plus controls, DW features, etc. SAP of course has done nothing to move the PB IDE forward during its tenure (so sad). Now we have PB.net based on an outdated VS2010 and almost obsolete.Net framework version support. What a waste of time - that could have been put into PB Classic moving it dramatically forward.

Boy, do we Appeon ASAP!

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Thu, 23 Jun 2016 07:54:25 GMT

"Objective-C would have been a gamble for me and I would now have to transition forward to SWIFT which has replaced it."

This sums it up for me, these modern technologies do not last very long which in my opinion says a lot about them. Within 2 years Objective-C was replaced by SWIFT which could be another short term trend.

To be honest it cannot predict what is gong to be the next big thing as there has not been one for many years now.....

I believe that there are more lines of Cobol used in production systems than any other language..... What does that tell you!?

David

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Thu, 23 Jun 2016 10:59:19 GMT

That's it .... Micro Focus Object Oriented Cobol ... Visual COBOL | Micro Focus

Re: what next for Powerbuilder developer -- Java or .net

Former Member — Tue, 02 Aug 2016 10:24:22 GMT

Objective-C is not a modern technology, it has been used commercially since 1988, when NeXT licensed it and within Apple when they bought NeXT