Re:The Finder’s GUI tax can be very expensive
by thaumasiotes on Thursday December 08, 2016 @08:21PM
(#13135902)
Maybe so, but, as pointed out elsewhere in the thread, printing to stdout is much, much, much, much slower than printing to a file. The fact that stdout is a file descriptor can only explain a vanishingly small quantity of the time cost of using it.
[ Parent
| on HN ]
Re:The Finder’s GUI tax can be very expensive
by arjie on Friday December 09, 2016 @01:07AM
(#13137013)
It's a combination of many things. You're probably writing to a file buffered, but terminal writes are generally unbuffered. In addition, I had a terminal setup once that just did a poor job of displaying text (line wrapping was slow, perhaps) and programs that would write out to stdout would be slow.
Re:The Finder’s GUI tax can be very expensive
by majewsky on Friday December 09, 2016 @09:27AM
(#13138893)
> printing to stdout is much, much, much, much slower than printing to a file
False dichotomy. stdout can very well be a file. What you mean is that printing to a terminal is slower than to a file.
Re:The Finder’s GUI tax can be very expensive
by thaumasiotes on Saturday December 10, 2016 @12:22PM
(#13146677)
True enough.
Re:The Finder’s GUI tax can be very expensive
by anthk on Thursday December 08, 2016 @09:39PM
(#13136272)
2>&1>/dev/null
Re:The Finder’s GUI tax can be very expensive
by goldenkek on Thursday December 08, 2016 @08:38PM
(#13135977)
blocking. blocking. blocking. blocking. rtfm
Re:The Finder’s GUI tax can be very expensive
by thaumasiotes on Thursday December 08, 2016 @10:03PM
(#13136349)
Again, the problem is not that writing to file descriptors is blocking. The problem is that writing to the screen is very slow. Writing to a file is just as blocking, but you'll block for much less time, because writing to a file is not slow.