Comments on: Use final http://javablog.franksalinas.net/2009/10/27/use-final-judiciously/ Java Enterprise Development & Technology Wed, 10 Mar 2010 23:24:13 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Frank http://javablog.franksalinas.net/2009/10/27/use-final-judiciously/comment-page-1/#comment-308 Frank Sun, 08 Nov 2009 16:10:49 +0000 http://javablog.franksalinas.net/?p=574#comment-308 @Peter - I agree. If developers could just forget about the potential performance optimizations final may, or may not, provide and focus on the intended purpose of the keyword for preserving immutability code quality would increase. In my opinion, code quality comes before performance and leveraging defensive programming techniques such as enforcing immutabilty appropriately increases code quality. @Peter – I agree. If developers could just forget about the potential performance optimizations final may, or may not, provide and focus on the intended purpose of the keyword for preserving immutability code quality would increase. In my opinion, code quality comes before performance and leveraging defensive programming techniques such as enforcing immutabilty appropriately increases code quality.

]]> By: Peter Lawrey http://javablog.franksalinas.net/2009/10/27/use-final-judiciously/comment-page-1/#comment-307 Peter Lawrey Sat, 07 Nov 2009 08:47:41 +0000 http://javablog.franksalinas.net/?p=574#comment-307 Its so under utilised, its a shame that final wasn't the default and a keyword like 'var' wasn't used for mutable variables/fields. I suggest you make all fields final if possible. While performance is a consideration, I believe it makes it much clearer which fields can be changed over the life of an object. Its so under utilised, its a shame that final wasn’t the default and a keyword like ‘var’ wasn’t used for mutable variables/fields.

I suggest you make all fields final if possible. While performance is a consideration, I believe it makes it much clearer which fields can be changed over the life of an object.

]]>