Ben Hoyt

Hi @datatraveller1, unfortunately no news -- at least in my own usage (and many other usages I've seen), this distinction has never been important, because you're almost always using the...

@arnoldrobbins Two things: 1) I/O used to be the bottleneck, but in the last decade or two that's no longer the case ([more in my article here](https://benhoyt.com/writings/io-is-no-longer-the-bottleneck/)). Sequential read speed...

Hi @datatraveller1, thanks for that. Maybe I need to see more context, but it's the hard-coded constants like 8 and 4 that I don't understand, and tend not to use...

@datatraveller1 Understood, and fair enough if you're using fixed-length fields. There are straight-forward UTF-8 string functions in Go to do all this, and I've done it before (see above), but...

@vegarsti No, unfortunately not -- this is a different issue.

@fioriandrea, thanks for this. I'd be happy to accept a PR for this, if you're game. Let's start keeping it simple with `matches()` and if that proves unwieldy we can...

Interesting -- that Gawk port must have a special-case handling for `/dev/stderr` on Windows, because otherwise I'm not sure how that would work. I'm not sure I want to add...

> the structure of the command implies the creation of a separate process for each line being written, something that is a expensive task in windows. Yes, that's true if...

Hi @sergeevabc, I'm afraid that ship has passed, as [v1.25.0](https://github.com/benhoyt/goawk/releases/tag/v1.25.0) is built with Go 1.21 (in general, I use the latest version to build, so I'm probably going to build...

@naalmlqpele Sorry for the delay. Does https://github.com/benhoyt/goawk/pull/225 work for you on Windows? It seems to work fine on Windows in CI, but I don't actually have a Windows machine handy...