By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,296 Members | 1,469 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,296 IT Pros & Developers. It's quick & easy.

PowerBuilder vs .Net

P: n/a
I have to prove .Net technologies over PowerBuilder of all things.
Powerbuilder is OOP, has a .net interface with the DataWindow.net. Thats
about all I know. It's a shootout between my group and another for an
upcoming project. The other group is mainframe/pb. Anyone have any ammo I
might use?

TIA
Jun 7 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Cats,

Net uses as internal development tools three of the major building tools.
Visual Basic (used by more people than all the other developments tools
together), C#, the quick raising star, C++ the proven one.
Net uses not the other 2 Java and Cobol (in a way as it can be done with the
3 called before)
Beside that is Net based on solutions, a complex of projects and all its
documentation and tools that are needed for that.

With Net you can develop with the same tool for Intel (windows) PC, PDA, the
InterNet in a very high quality in some area's not even touched by others,
you cannot develop for the other 2%.

I find that arguments enough,

Cor
"CatsCradle" <Ca********@discussions.microsoft.comschreef in bericht
news:04**********************************@microsof t.com...
>I have to prove .Net technologies over PowerBuilder of all things.
Powerbuilder is OOP, has a .net interface with the DataWindow.net. Thats
about all I know. It's a shootout between my group and another for an
upcoming project. The other group is mainframe/pb. Anyone have any ammo
I
might use?

TIA

Jun 7 '07 #2

P: n/a
CatsCradle <Ca********@discussions.microsoft.comwrote:
I have to prove .Net technologies over PowerBuilder of all things.
Powerbuilder is OOP, has a .net interface with the DataWindow.net. Thats
about all I know. It's a shootout between my group and another for an
upcoming project. The other group is mainframe/pb. Anyone have any ammo I
might use?
For one thing, consider difficulties in hiring: how many PowerBuilder
developers are out there, compared with .NET developers? How much
effort is being put into improving PowerBuilder compared with the
effort MS is putting into .NET?

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Jun 7 '07 #3

P: n/a
Thanks guys. All valid. Appreciate it.

"Jon Skeet [C# MVP]" wrote:
CatsCradle <Ca********@discussions.microsoft.comwrote:
I have to prove .Net technologies over PowerBuilder of all things.
Powerbuilder is OOP, has a .net interface with the DataWindow.net. Thats
about all I know. It's a shootout between my group and another for an
upcoming project. The other group is mainframe/pb. Anyone have any ammo I
might use?

For one thing, consider difficulties in hiring: how many PowerBuilder
developers are out there, compared with .NET developers? How much
effort is being put into improving PowerBuilder compared with the
effort MS is putting into .NET?

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Jun 7 '07 #4

P: n/a
I am running right with you on this one Jon. The only "company" that uses
PowerBuilder (that I know of, that is) in Nashville is the Department of
Children's Services for the State of Tennessee. They are mired down in an
application that has hardly ever been refactored and are paying the price
for the monolithic architecture.

Currently, they pay a pretty penny for their contractors, whom will never
become state employees, as their salaries will be slashed. If the state does
force budget cuts, both teh state and the devs will lose, or switch
proficiencies.

Switch to .NET devs, which are also in limited supply (compared to demand),
but there are a lot more of them. Thus, one can pull one in (mid-level) for
about $25k less than an equivalent PowerBuilder dev.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)

************************************************
Think outside the box!
************************************************
"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP*********************@msnews.microsoft.com. ..
CatsCradle <Ca********@discussions.microsoft.comwrote:
>I have to prove .Net technologies over PowerBuilder of all things.
Powerbuilder is OOP, has a .net interface with the DataWindow.net. Thats
about all I know. It's a shootout between my group and another for an
upcoming project. The other group is mainframe/pb. Anyone have any ammo
I
might use?

For one thing, consider difficulties in hiring: how many PowerBuilder
developers are out there, compared with .NET developers? How much
effort is being put into improving PowerBuilder compared with the
effort MS is putting into .NET?

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

Jun 10 '07 #5

P: n/a
Gregory,
>I am running right with you on this one Jon.
In what do you disagree with me than, just for the wider public

Cor

"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMschreef in
bericht news:O9**************@TK2MSFTNGP03.phx.gbl...
>I am running right with you on this one Jon. The only "company" that uses
PowerBuilder (that I know of, that is) in Nashville is the Department of
Children's Services for the State of Tennessee. They are mired down in an
application that has hardly ever been refactored and are paying the price
for the monolithic architecture.

Currently, they pay a pretty penny for their contractors, whom will never
become state employees, as their salaries will be slashed. If the state
does force budget cuts, both teh state and the devs will lose, or switch
proficiencies.

Switch to .NET devs, which are also in limited supply (compared to
demand), but there are a lot more of them. Thus, one can pull one in
(mid-level) for about $25k less than an equivalent PowerBuilder dev.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)

************************************************
Think outside the box!
************************************************
"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP*********************@msnews.microsoft.com. ..
>CatsCradle <Ca********@discussions.microsoft.comwrote:
>>I have to prove .Net technologies over PowerBuilder of all things.
Powerbuilder is OOP, has a .net interface with the DataWindow.net. Thats
about all I know. It's a shootout between my group and another for an
upcoming project. The other group is mainframe/pb. Anyone have any
ammo I
might use?

For one thing, consider difficulties in hiring: how many PowerBuilder
developers are out there, compared with .NET developers? How much
effort is being put into improving PowerBuilder compared with the
effort MS is putting into .NET?

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too


Jun 16 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.