S
Shao Chan
Guest
Personally, I've always liked pretty much everything about Progress and not really fussed about whether it has bolt-on's to be similar to modern languages - its about the speed and ease at which the application can be developed. The biggest problem with Progress is purely to do with integration. Whilst in the past Progress could live in its own world and companies only had one main application to support their business, its a whole inter-connected world out there. When doing any integration, Progress has always been a sore point. You can get all other database vendors into a room for applications to integrate with each other, but there will always be a separate 'How does Progress do it' meeting. Whether its ODBC, SOAP, REST, SSL, whatever, Progress will not integrate reliably to the same level as other technologies such that you need to look for workarounds which then wipe out the advantages of using Progress to build the application at pace. bprowsdldoc hangs on many WSDLs and the -show10style option needs to be used to get a basic wsdl. Code pages not supported. Cipher suites not supported. All these things make it so that even if you get code working in one instance, a change at the target end and you're looking for workaround solutions - often with other technologies. For any kind of capability in the integration area, Progress needs a programme called 'Challenge Progress' or something where you send the endpoints you need to integrate with and either they get it working or they patch it so that it works in the next version.
Continue reading...
Continue reading...