I don't like the go requirement when compared to awk which is essentially no requirement at all.
And I generally don't like reimplementations of things that already exist without a significant justification. (for real I mean, vs for the fun of it or just experimenting or as an excersize to use a new language)
Don't care much either way about the verbosity because the extra verbosity can also be more consistent and easier to read because of fewer special implicit things to have to just know and resolve mentally.
But the execution time is undeniable, and it's probably a lot more convenient for typical awk-ish jobs to use something like this than to make a dedicated little c or go program, not to mention, this still lets you treat your code as an interpreted, readable, hackable script, vs an actual c or go program that would have to be an executable.
All in all, walking in the door I was predisposed to find this pointless and annoying that some number of people might buy into it and eventually I'd have to care because something I want some day will require it.
But in fact I find it not pointless at all. Nice.
And I actually like and use awk. I'm comfortable and productive with it for the occasional jobs that fit naturally. So comfortable I've accidentally written things that ended up becomming mostly just a big END{} block which could have been done exactly the same way in bash or anything else.
And I generally don't like reimplementations of things that already exist without a significant justification. (for real I mean, vs for the fun of it or just experimenting or as an excersize to use a new language)
Don't care much either way about the verbosity because the extra verbosity can also be more consistent and easier to read because of fewer special implicit things to have to just know and resolve mentally.
But the execution time is undeniable, and it's probably a lot more convenient for typical awk-ish jobs to use something like this than to make a dedicated little c or go program, not to mention, this still lets you treat your code as an interpreted, readable, hackable script, vs an actual c or go program that would have to be an executable.
All in all, walking in the door I was predisposed to find this pointless and annoying that some number of people might buy into it and eventually I'd have to care because something I want some day will require it.
But in fact I find it not pointless at all. Nice.
And I actually like and use awk. I'm comfortable and productive with it for the occasional jobs that fit naturally. So comfortable I've accidentally written things that ended up becomming mostly just a big END{} block which could have been done exactly the same way in bash or anything else.