3 ms·
Whilst I understand that you can have good reasons for want to integrate to the libraries he mentions, I can't help feeling that Hibernate is a library that sol
by moomin 13y ago
Whilst I understand that you can have good reasons for want to integrate to the libraries he mentions, I can't help feeling that Hibernate is a library that solves a problem caused by the type system, so just using a dynamic language and forgetting Hibernate strikes me as a good approach. Indeed, all the libraries listed look avoidable.
- playing_colours 13y agoRight, you should have reason to use all these JPA, Hibernate, EJB in Scala, in most cases you can just go with Scala's modern alternatives (Play, Slick etc.) and build robust apps. Dynamic languages aren't often a pill for everything, especially with larger codebase and when performance is considered.
- lmm 13y agoHibernate is limited by the language it finds itself in. Enhance it with a few macros and you get something truly wonderful - type-safe handling of data from outside your application. (as for spring, I'm working on a type-level alternative as we speak)
- pjmlp 13y ago> Indeed, all the libraries listed look avoidable. Not on an enterprise context, like it or not, most consulting projects on the enterprise world require interaction with them.
- gngeal 13y agoIs that the IT equivalent of legally requiring a man with a red flag to run sixty yards ahead of the car?