Hacker News Reader

Comment by kyleee | Hacker News Reader

It may be desirable for boilerplate to be maximally painful if it forces our collective hands to cut down on boilerplate and innovate it away

View on HN

In my experience whenever someone tries to "innovate" away boilerplate they end up creating shitty abstractions that are inflexible, poorly documented, and unmaintained.

Boilerplate generally exists for a reason, and it's not because the creator likes typing.

That’s a good plan if your language isn’t Go. For us I think tools to wrangle boilerplate are a lot more feasible than actually eliminating it.

    if commentErr != nil {
        hn.Upvote("https://news.ycombinator.com/item?id=29017491")
    }

Who is realistically going to innovate the boilerplate out of Java if they're stuck using it at work?

That, or any job where you're not permitted to make the sweeping changes required to resolve boilerplate. Many of my jobs had such restrictions.

I mean, Clojure kinda does that

So the solution to the problems that Copilot tries to solve is "migrate your workplace to Clojure"? Ordinary devs can't do that.

Oh I was just chiming in really, not trying to say anything about copilot

Lombok and most intellij features make java boilerplate pretty obselete.

Reply on news.ycombinator.com