Win a copy of Kotlin for Android App Development this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Devaka Cooray
  • Jeanne Boyarsky
  • Bear Bibeault
  • Junilu Lacar
  • Paul Clapham
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • salvin francis
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

The Good and Bad Parts  RSS feed

Posts: 11
Hibernate Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome Jim.

I have certain expectations from your book. For example, I would like to know first of all, how do you differentiate between the GOOD parts and the BAD parts of the Java programming language - does this book cover the internals of the topics mentioned in the TOC OR just the externals required in day-to-day coding? Also, does it cover good programming practices while using, say Collections? In short, please describe in brief the gist of the book.

Thanks & Regards
Mahesh Kandpal
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here's what I tried to do in the book.

First of all, "good" is a relational term, not an absolute-- a language isn't, I argue, good; a language is good for doing some kind of programming task. I then argue that Java is good for doing large-scale, multi-person projects for software that needs to work reliably and has a long lifetime (and, therefore, will need to be changed).

I then talk about the features of the language that make it good for those kinds of tasks. I do talk a bit about the internals, but this isn't a book about the guts of Java. I do talk about good programming practice. And I talk a fair amount about how you design systems for this sort of thing.

Hope that this helps...
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!