For a verbose language the problem isn't the typing it's the reading. On the typing side I agree with you: I don't mind spending 30 minutes typing a bunch of boilerplate. I do mind digging through 100s of lines of code to find the 2 lines that actually do something interesting.

Of course, copilot is only going to save you typing time, and you'll have to pay it back at reading time.

I spend 95% of my day reading existing code not writing it, I have no idea what these developers writing code all day work on

"verbose" and "expressive" are on two different axes. Go is neither verbose nor expressive, for example, while XQuery is both verbose and expressive.

People write languages at higher levels of abstraction not to type fewer characters but to reduce logical errors that can occur, and provide better abstractions over things.

An example here is an infinite list. It's far easier to do that in say Haskell and python, applying filters along the way using higher order and curried functions than it is to do it in say C.

There is a difference between higher levels of abstraction and having a separate symbol for every single operation imaginable just for the sake of "expressiveness".

Yes, you can shove a 20 line function into one line with a ton of weird symbols, but the one reading it after you will need to unroll it anyway to understand it so what's the point?