hairy

I have more than just a hairy experience with JS lately.

One of the big reasons mentioned was that Java's just too big and hairy of a language.

The OpenGL API is really hairy to implement at all, let alone making it fast.

Jim Gray was famous for predicting that the end point of computers were "smoking hairy golfballs".

Cleaning up hairy code or removing redundant files and gunk from older projects.

And that case can get quite hairy, as anyone who has watched their machine self-immolate after it discovers it is out of RAM can attest to.

You probably know that equality becomes a hairy, nasty thing in category theory.

The fact is even if you are doing it "right" with strict topic branches you still can get very hairy unbisectable conflicts that would be easier to reason about with a rebased history.

The general conclusion of that series of tickets was that the code generation required to make this CPS transformation work with all edge cases is a bit too hairy to be worth it on balance.

Most common are the real simple refactorings: A method might grow too hairy and need a split up, maybe a method's name does not correctly convey its meaning anymore, arguments would have to be reordered for consistency, and so on.

I only wish it were, and I speak from a rather privileged perspective where I work for myself, don't care about what people say about me most of the time, and have a big, tall, hairy fiancé and a big, tall, intimidating roommate to back me up.