When parsing outputs from builds and other complex processes all it is difficult to tell which output belongs to which command. Especially if you want to do it programmatically and handle errors. It is a decades old problem due to stdout/stderr being "stringly-typed" and garbled together. Is there any serious attempt at creating structured outputs?
=> More informations about this toot | View the thread | More toots from federico3@oldbytes.space
text/geminiThis content has been proxied by September (3851b).