Posted this one yesterday - https://fixedbycode.blogspot.dk/2017/08/why-i-keep-preferring-delphi.html - personal comments, to agree to disagree upon :) Have a nice one.
Posted this one yesterday - https://fixedbycode.blogspot.dk/2017/08/why-i-keep-preferring-delphi.html - personal comments, to agree to disagree upon :) Have a nice one.
It's very interesting this part in what he says: "... should I spend time on keeping up with the current APIs for various enterprise systems - or should I just pay up and delegate the work to the CData people that are focused on that issue. It all depends on need and time..."
ReplyDeleteIt's exactly what I think that the majority of us think when deciding the acquisition of a third party component library.
We don't want to read the third party code to understand what the code is doing and how to use it.
We want a black box library with a good set of user manuals and programmer manuals.
We don't buy your code, we buy your experience! We delegate the development and the knowledge!
It's a reflexion about certain third party component libraries that argue that his documentation is as poor because his code is auto-explained.
Poor philosophy, of course.
Juan C. Cilleruelo Agree. The example I used (CData's Enterprise Connectors) actually has very good documentation. I would add that I never buy components without source - and which do not have proper documentation or perfect samples. And I have stopped using components that have a too steep learning curve and too many features. Less is more :)
ReplyDeleteThe less, if good, two times good!
ReplyDelete