|Why are you not using java.util.concurrent classes? [message #1174954]
||Thu, 07 November 2013 07:25
| Marvin Toll
Registered: July 2009
As I review more of your code base over time, it appears that there is a pattern to not take advantage of advances to the Java language.|
This pattern is strikingly apparent with a lack of java.util.concurrent classes.
I remember the Toplink days, back in 2005, scratching my head trying to figure out why you were still using Vectors.
What is being put at risk is not simply performance and scalability... but reliability in the context of contemporary multicore (concurrent) coding practices. Said more directly, in my opinion, you are marginalizing your product by not supporting concurrent programming usage patterns.
CTO, Pattern Enabled Development
[Updated on: Thu, 07 November 2013 07:27]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02386 seconds