News for hackers. Stuff that matters.
Re:Why is printing “B” dramatically slower than printing “#”... by agumonkey on Thursday September 08, 2016 @09:11AM (#12452610)
So printing B isn't slower: terminal rendering of lines of text is just less obvious than thought.
Re:Why is printing “B” dramatically slower than printing “#”... by __jal on Thursday September 08, 2016 @01:34PM (#12455154)
Any time I'm seeing really strange results involving the terminal, I try to look for terminal-related weirdness. There is a lot of stuff going on that people generally ignore or simply don't know about, because it generally just works.

And when it doesn't, if you're not at least a little familiar with what's going on, it can be a deeply confusing and obscure little world.

Re:Why is printing “B” dramatically slower than printing “#”... by aidenn0 on Thursday September 08, 2016 @02:31PM (#12455799)
I don't know if it's still valid, but SBCL has a readme entry indicating that building in xterm is much faster than building in gnome-terminal. SBCL's build output is incredibly noisy and the compiler is quite fast, so the combination of the two makes for an incredible rater of output to the terminal.
Re:Why is printing “B” dramatically slower than printing “#”... by agumonkey on Thursday September 08, 2016 @01:46PM (#12455272)
I remember how confusing IO was in college. Even the implicit flush requirement to show stuff. Utter dread. Few years ago I read an old lisp book (something written before Common Lisp), they don't touch IO until the end, for transparency/bootstraping reasons, and since it's insignificant for thinking it's a straightforward model without fancy features, I wish people taught CS this way.