Many people say how it is C #, why is PB how bad? In fact, each tool has its own characteristics. I have been working in PB for some years. I have written some feelings about PB, and I will test blog, huh, huh.
Powerbuilder's DataWindow is the best, efficient data operation component I have ever seen.
Some people say "PB big projects are often like mess", I think it is because of the reason for the design of the system. I have to admit that there are many PB projects that have little mess, that is because PB is indeed easy to use, solve small problems efficient, most in line with the style of the country's development project, what is the design, just make the customer's function, then say, But this is not the fault of DataWindow.
The support of the PB for large projects is quite good, he has its own complete set of systems. PB's OO implementation is simple and practical, and it is much better than VB6. PB's unique visual inheritance is also a highlight, and now it is learned by vs.net. DataSet in VS.NET is also a very shadow of the Datastore of PB.
The disadvantage of PB is that the system is closed and conserved. The interoperability of the Pb and Windows systems is extremely poor. After 5.0 (huh, I originally used this version, it is estimated that there is no significant change in PB, almost there is a good learning routine, but there is no practicality , I will make a class library that I use my own class library for PFC, refer to MFC's idea. I understand that many companies use PFC ideas, and they will re-have class libraries (generally in such companies, they will only study PFC). In addition to database operations, PB does not like other ways in other ways. The third-party components available in PB are very small, which is related to the closure system of the PB itself, and there is almost no longer multiplexing.
For now, the advantage of PB can say that only DataWindow is left. Once Sybase has a DataWindow.net, I think Powerbuilder is no one, and there is also a plurality of window controls for VS.NET. I still have something to do, so long, how do you have a third party to do what DW for net is a patent restriction?
For the development of the company's MIS level, MS Framework is too large, if there is a third party to provide a higher-level Framework based on .NET, I want to be popular. I feel that the Sybase Powerbuilder department should be the choice, huh, huh.
