[Esims-devs] To go entirely Tiger or not
Status: Alpha
Brought to you by:
binil
|
From: Juby V. <vi...@ne...> - 2006-12-06 18:13:07
|
Some thoughts on moving our app to tiger
The plus points are
1) Autoboxing
2) new for loop that looks cleaner
3) Annotations ( I find some really stupid though)
The reservations I have are
1) Makes declarations of 'Types' & Collections more tedious and
'visibly complex'. It types go wrong a lot of time will be wasted in
debugging why the class dint compile
2) One has to write "Java 5" code than java code,
(I dont see a scenario where we will add a Teacher to a list of
students or so.. coz the entities and VOs we use are sensibly named.)
3) Repeating DAO problem can be handled by just sub classing one base
class for all entities that need to be persisted and checking if the
object is an instance of that base class.
4) Additional learning curve (as though we dont have enuf)
I feel that we must use a subset of Tiger than just adopting it just
because its there.. i doubt the value addition it brings into the
project in just taking it up entirely.
In essence "use what makes sense" is what I feel , but I go with the
majority since the code will work both ways
Comments plz
Best regds
JV
|