The builder pattern sucks shit.

There I said it.

Why?

No you're just a fucking loser

it's _rarely_ useful. but in those cases, it rocks.

as a matter of fact, i used it myself today.

I agree with @tosensei.

If you apply it everywhere like a moron, it sucks.

If you use it where needed, it rocks!

every pattern sucks, when forced on the wrong things and/or overused. Something that every design patterns book tells you too, btw.

Java library developers only bothered to learn one pattern and use it for everything. Now, rightfully so, people hate said pattern because for some reason you need to do IntegerFactory.create().setValue(3).isSigned(true); instead of just int a = 3;

@jestdotty please specify:

how do i wrap something in javascript proxies if i don't use a shit-tier language?

it's the best way to define smart defaults for packages.

I was annoyed because I was using it from https://mvnrepository.com/artifact/...

One of the create methods was deprecated and their was no javadoc explanation of what replaced it.

@b2plane Blow me

Do you mean Factory pattern?

@MammaNeedHummus both exist