The Design Patterns book is the alpha and the omega of design patterns currently. It is not new however but it seems that it passed the test of time.
You can read detailed real life examples of each design pattern, how do they relate to each other, how and when to use them and a thorough explanation for each. The Builder pattern is included of course.
As to answer your question I can present my views although they are of course not authoritative.
I think that if you have a small number of fields you can go with using the constructor. If you take checkstyle for example it fires a warning over 7 parameters.
If you know for sure however that you will refactor that class soon or you will have to extend it I think the Builder pattern is better since it is easier to refactor. Refactoring constructors is never fun.
If you are over 7 parameters I think the Builder is far better. I've been using it in the current project I'm working on extensively.
Please note that by using the Builder pattern you don't say that "Okay, I'm an immutable object builder". You say that "Okay, I'm building parameterized objects". It is therefore not a problem that you have a set of mutable fields in your class. If you however name your class like ImmutableFooDTO
and later you add mutable fields it leads to confusion.
So if there is a set of fields which must not be mutable then mark them final and use a constructor/builder and provide setters for the mutable ones.