bruce.armstrong wrote: Somebody just said it better than I did, and with more chops to say it:
Open Letter to Mark Zuckerberg, Sheryl Sandberg & Facebook Mobile
In many cases, the end of the year gives you time to step back and take stock of the last 12 months. This is when many of us take a hard look at what worked and what did not, complete performance reviews, and formulate plans for the coming year. For me, it is all of those things plus a time when I u...
Recently I have been having déjà vu back to the days of PowerSoft. If you are old enough to remember, PowerSoft was the leader in making graphical development practical for the masses — rather than the object oriented gurus. Back in the early 1990s when PowerSoft’s product PowerBuilder was in its heyday, it had been able to achieve dominance over arch rival Gupta Technology and a myriad of other long forgotten competitors. Ironically, at the time, Gupta had a much more sophisticated object oriented environment than PowerBuilder. But PowerBuilder was able to achieve leadership because the company found a way to make the traditional COBOL developer (and there were lots of them) very successful as graphical software designers.
The secret was that while PowerBuilder professed to be an object oriented graphical development environment, it was actually a procedural environment that was familiar to the COBOL developer. Therefore, the skills that had made this generation of developers successful in an earlier generation provided the platform for a new career path in client/server development. Therefore, PowerBuilder took the market by storm and set the path for the early success of client/server computing.
Now, fast-forward to today and the advent of Web 2.0. We are seeing lots of interesting tools such as Nexaweb, JackBe, and Kapow. All these companies have a common strategy: they want to become the PowerBuilder of this new generation of application development environments. To create a rich, collaborative environment requires a level of sophistication that would prohibit less technical developers from participating. Therefore, just as PowerBuilder provided a way for the masses to create a graphical first generation environment, so this next generation of development tools will bring Web 2.0 to a broad audience. These web development environments provide the dynamic, stateful approach needed to create Web 2.0 environments.
I think that this movement towards Web 2.0 and these abstracted tools to support them will complete the picture of a service oriented architecture. The Web 2.0 environment is making the browser environment a full-fledged participant in enterprise computing. Over time, we’ll see lots of business people creating compelling business services in this way focused on innovative, collaborative software that provides a rich client environment that provides sophisticated communications, as well as a stateful distributed computing platform. This is not an easy feat but one that some innovative players are going to grab to become the PowerBuilder of the Web 2.0 set.
About Judith Hurwitz Judith Hurwitz has been a thought leader in the technology research and strategy consulting for more than 20 years. In 1992, she founded Hurwitz Group, a software research and consulting organization that quickly became an industry leader with top technology clients. Currently she is the President of Hurwitz & Associates, a research and consulting firm with a pragmatic portfolio of service offerings focused on identifying customer benefit and best practices for buyers and sellers of information technology in the US and Europe. She is a frequent keynote speaker at industry events and holds advisory board positions at Safeguard Scientifics and various emerging technology companies. She is also a recipient of the 2005 Massachusetts Technology Leadership Council award.
Reader Feedback: Page 1 of 1
#5
Scan commented on 14 Feb 2008
Her comments more closely resemble Visual Basic and not powerbuilder. Until the arrival of .Net, visual basic was the least object oriented GUI tool with tons of procedural code inside every function and event one can get hold of, as it did not even support basic feautures such as inheritance or encapsulation. It became popular because of the Microsoft tag that was attached to it. I am really surprised how the blog had completely ignored this fact. IF powerbuilder turned Cobol programmers into OOP programmers then Visual Basic turned non programmers into programmers.
#4
SS commented on 4 Feb 2008
I would like to echo the same sentiments as Bernard. Powerbuilder supported all the important characteristics of OOP more than many other graphical tool, but unlike Java did not force one to be object oriented . I have come across many apps written in PB that were extremely object oriented (due to the fact that these were written by developers well versed in OOP) and some poorly coded apps due to lack of OOP knowledge on the part of the developer. This goes to prove that there is nothing typically wrong with the product iteself. The mass appeal was due to the datawindow that made database manipulation much easier than any other tool and it still continues to be unrivalled.
#3
HommeDeJava commented on 25 Jan 2008
Google is definitely the Web 2.0 PowerHouse / PowerBuilder. They are creating all the Web 2.0 Open Source Frameworks to be able to build easily all the great applications following the idea of Web 2.0 application patterns.
"...while PowerBuilder professed to be an object oriented graphical development environment, it was actually a procedural environment..."
The PowerBuilder I know supported true OO before Java existed; however, it also allowed programmers to use as much procedural logic as they wanted, whereas Java and .Net languages are better at forcing object use (but are hardly immune by any stretch to procedural code bloat).
But I understand your point. Because so many developers during the PowerBuilder halcyon days did not have proper training in OO concepts and techniques, PowerBuilder apps by design (or lack thereof) tend to be non-OO piles of COBOL-like scripts. This is, however, more a reflection of the practitioner's skills than of the tool (and I would know - I wrote some bad PB code in the earlier years).
Mr. Armstrong is correct: PowerBuilder is to C++ what things like Dreamweaver are to HTML. For better or worse, that's probably what made PowerBuilder successful in the 90's.
Not sure about the COBOL part. I have known and continue to know a vast number of PowerBuilder developers. Few of them have any experience with COBOL. I certainly didn't. The few COBOL folks I did know did not find the tool familiar to work with.
PowerBuilder abstracts the developer from low level implementation details. To that end, it makes it easier for anyone who doesn't want to deal with such details to do development. That's probably more in line with the point you're trying to make.
Scan wrote: Her comments more closely resemble Visual Basic and not powerbuilder. Until the arrival of .Net, visual basic was the least object oriented GUI tool with tons of procedural code inside every function and event one can get hold of, as it did not even support basic feautures such as inheritance or encapsulation. It became popular because of the Microsoft tag that was attached to it. I am really surprised how the blog had completely ignored this fact. IF powerbuilder turned Cobol programmers into OOP programmers then Visual Basic turned non programmers into programmers.
SS wrote: I would like to echo the same sentiments as Bernard. Powerbuilder supported all the important characteristics of OOP more than many other graphical tool, but unlike Java did not force one to be object oriented . I have come across many apps written in PB that were extremely object oriented (due to the fact that these were written by developers well versed in OOP) and some poorly coded apps due to lack of OOP knowledge on the part of the developer. This goes to prove that there is nothing typically wrong with the product iteself. The mass appeal was due to the datawindow that made database manipulation much easier than any other tool and it still continues to be unrivalled.
HommeDeJava wrote: Google is definitely the Web 2.0 PowerHouse / PowerBuilder. They are creating all the Web 2.0 Open Source Frameworks to be able to build easily all the great applications following the idea of Web 2.0 application patterns.
GWT, Android, Google Gears, AJAX Feed API, OpenSocial, YouTube API, Gooogle Maps
Bernard Dy wrote: "...while PowerBuilder professed to be an object oriented graphical development environment, it was actually a procedural environment..."
The PowerBuilder I know supported true OO before Java existed; however, it also allowed programmers to use as much procedural logic as they wanted, whereas Java and .Net languages are better at forcing object use (but are hardly immune by any stretch to procedural code bloat).
But I understand your point. Because so many developers during the PowerBuilder halcyon days did not have proper training in OO concepts and techniques, PowerBuilder apps by design (or lack thereof) tend to be non-OO piles of COBOL-like scripts. This is, however, more a reflection of the practitioner's skills than of the tool (and I would know - I wrote some bad PB code in the earlier years).
Mr. Armstrong is correct: PowerBuilder is to C++ what things like Dreamweaver...
Bruce Armstrong wrote: Not sure about the COBOL part. I have known and continue to know a vast number of PowerBuilder developers. Few of them have any experience with COBOL. I certainly didn't. The few COBOL folks I did know did not find the tool familiar to work with.
PowerBuilder abstracts the developer from low level implementation details. To that end, it makes it easier for anyone who doesn't want to deal with such details to do development. That's probably more in line with the point you're trying to make.
Private clouds solve many problems for enterprises and bring unique operational challenges along with them. There are dozens of companies of all sizes that will build you a private cloud and turn over the keys – then what? Trying to convert a traditional enterprise IT operations team t...
Like a moving company for the cloud, Racemi provides the ability to easily migrate Windows server images to public clouds. The company is a sponsor at the upcoming Cloud Expo where visitors can see Racemi demonstrate server migrations.
Racemi announced on Wednesday its DynaCenter soft...
As a Platinum Plus Sponsor of Cloud Expo New York, Oracle is offering special passes to SYS-CON's 10th International Cloud Expo, which will take place on June 11–14, 2012, at the Javits Center in New York City, New York.
With more than 380,000 customers – including 100 of the Fortune ...
SAP on Tuesday announced its intention to buy Ariba for $4.3 billion, a 19 percent premium on Ariba's market capitalization.
The move comes soon after SAP's SuccessFactors February buy and shows that SAP is quickly and aggressively acquiring its way to a full cloud business services c...
Google said first thing Tuesday morning that it’s closed on its $12.5 billion acquisition of Motorola Mobility Holdings Inc.
It’s been waiting nine months to clinch the deal and get its hands on Motorola’s patent portfolio. It finally got Chinese approval over the weekend albeit with...
How do we connect clouds? Since the Internet has no SLA, many organizations are concerned about being exposed to the vagaries of the Internet. There are only a few options for concrete quality of service (QoS) when accessing public clouds.
In his session at the 10th International Clo...