zlacker

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

>>kyleee+(OP)
Who is realistically going to innovate the boilerplate out of Java if they're stuck using it at work?

>>kyleee+(OP)
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.

>>keving+g
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.

>>kyleee+(OP)
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.

>>keving+g
I mean, Clojure kinda does that

>>closep+l2

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

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

>>keving+g
Lombok and most intellij features make java boilerplate pretty obselete.

>>keving+yu
Oh I was just chiming in really, not trying to say anything about copilot