Comments on: Creating Complexity: Lock-In To Bad Technologies http://www.codesimplicity.com/archives/31 Thu, 04 Dec 2008 21:29:50 +0000 http://wordpress.org/?v=2.6.2 By: Max Kanat-Alexander http://www.codesimplicity.com/archives/31#comment-360 Max Kanat-Alexander Thu, 17 Jul 2008 20:40:28 +0000 http://www.codesimplicity.com/?p=31#comment-360 Yeah, I definitely agree. That’s one of those good technology choices that allows you to have interoperability without much sacrifice. Of course, you have to choose an ORM that also fits all of the criteria, but Hibernate is well-enough used that even though I’ve never used it, I would probably look at it as my first choice if I were developing in Java, just because it has that much momentum. Recently I used SQLAlchemy in Python, and that is really a great ORM. -Max Yeah, I definitely agree. That’s one of those good technology choices that allows you to have interoperability without much sacrifice. Of course, you have to choose an ORM that also fits all of the criteria, but Hibernate is well-enough used that even though I’ve never used it, I would probably look at it as my first choice if I were developing in Java, just because it has that much momentum.

Recently I used SQLAlchemy in Python, and that is really a great ORM.

-Max

]]> By: Peng’s links for Thursday, 17 July « I’m Just an Avatar http://www.codesimplicity.com/archives/31#comment-355 Peng’s links for Thursday, 17 July « I’m Just an Avatar Thu, 17 Jul 2008 13:18:09 +0000 http://www.codesimplicity.com/?p=31#comment-355 [...] Kanat-Alexander: Creating Complexity: Lock-In To Bad Technologies. Max expands a point in his post The Never-Shipping Product to look at what “bad” [...] [...] Kanat-Alexander: Creating Complexity: Lock-In To Bad Technologies. Max expands a point in his post The Never-Shipping Product to look at what “bad” [...]

]]> By: funtomas http://www.codesimplicity.com/archives/31#comment-354 funtomas Thu, 17 Jul 2008 10:57:29 +0000 http://www.codesimplicity.com/?p=31#comment-354 Regarding the SQL lock-in, there's a third way to escape: use of Object-Relational Mapping tier, such as Hibernate in case of Java, for example. Regarding the SQL lock-in, there’s a third way to escape: use of Object-Relational Mapping tier, such as Hibernate in case of Java, for example.

]]>