On Oct 3, 2010, at 11:58 PM, Sam Stainsby wrote: >> In any case coding to a standard persistence interface (JDO) >> over a proprietary API is IMHO an insurance policy > > I can understand that, and I think that way too in some situations, but I > reject the notion that there is no price to pay.
This is where the old "Total Cost of Ownership" comes in to play. The right technology for a particular developer or team is going to be the one that allows the problem domain to be solved with the least cost. For some developers, a lack of documentation or online examples is might cost more in lost time than the additional cost of laboriously setting up JPA and all the requisite annotations. For others, unlearning their old habits might be a huge cost. In a team environment, change can lead to politics, another cost. As a project grows to include a team, potential difficulty in hiring new staff that is receptive to the chosen technologies also needs to be considered briefly (Wicket itself had this issue until recently). There's *always* a cost, but which one is cheapest (most efficient, easiest to use, yada yada) in the end depends on a lot of localized factors. If it did not, there would be a website that every developer visited before starting a new project, and the anointed "best technologies" for that moment would be listed there. Heck, you would be able check boxes on the list and generate a POM from it... Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
