The author seems to really not like ncurses. But why? Is there something wrong with it?
Everything you ever wanted to know about terminals
31–40 of 191 posts
Re: Everything you ever wanted to know about terminals
#32Earlier quoted context omitted.
Isn't worrying about someone else's grammatical use of capitalization when the piece is understood anyway a little too pedantic?
I find the text more awkward to read without capital letters starting sentences, especially in paragraph form.
Re: Everything you ever wanted to know about terminals
#33I could take this a lot more seriously if capital letters were properly used.
Re: Everything you ever wanted to know about terminals
#34> but i swear to god developers have so completely forgotten how terminals work that i might be one of a handful of people left on earth who actually has the knowledge to, so they all just layer their bullshit on top of ncurses (which should never have survived the '90s) instead and it's maddening. Actually, yes, understanding the tty in detail seems to become a dark art. However it's the best way to do complex thing…
It looks like you have done a lot of work with sixels based on your github too. Have you ever written anything about that?
No, WYSIWYG: I don't bother much more than that with explaining how it's done: the source code + the comments + the github page already give all the details away to whoever wants to dig deeper.
I'm not much into social media or self promotion either: if people like what I do, they'll use it - I don't care much more than that, as everything was written for myself and my selfish needs first.
The tty/sixel world is very small world anyway, we generally know and recognize eachother, so we know where to look for cool new stuff :)
Re: Everything you ever wanted to know about terminals
#35Earlier quoted context omitted.
it is a security centric view point not a "Western" one.
The solution is prohibiting characters that can easily be confused (across all writing systems), not banning Punycode altogether.
In practice, browsers already check for this and display the "raw" punycode if they detect mixed script usage, but I wish such domains would not be registrable at all. These checks are somewhat complex and difficult, and easy to get wrong.
Re: Everything you ever wanted to know about terminals
#36Earlier quoted context omitted.
I find the text more awkward to read without capital letters starting sentences, especially in paragraph form.
I can’t agree more. An author who can’t be bothered to follow well established forms of style, grammar, and punctuation in a technical article somehow deflates whatever else they have to say even if accurate. It’s not as if they are trying to emulate the works of E. E. Cummings, James Joyce, or Arno Schmidt.
This author is a much much better writer than average for free technical content! They have an interesting, unique style! The typography and punctuation are part of that style! It would be tangibly worse if they adhered to the (bad, and also arbitrary!) typographical conventions of raw html just to please a bunch of square-ass nerds. Shit just makes me sad seriously.
Re: Everything you ever wanted to know about terminals
#37Then I noticed Pygments, a Python-based library for pretty formatting source code, has an option to output an ANSI formatted file. I quickly found a bunch of libraries that could render ANSI formatted text to a print canvas.
In the end, I put the original source code file through 'pygmentize -16m -o tempfile.an` (`16m` is the 16M color terminal ANSI formatter) and pipe the `tempfile.an` through a print-optimized renderer to actually print the source code.
ANSI escapes FTW!
[1] WinPrint - https://github.com/tig/winprint [2] https://pygments.org/
Re: Everything you ever wanted to know about terminals
#38The author seems to really not like ncurses. But why? Is there something wrong with it?
The article has no pictures of what it is selling, so it just seems like a rant, as suggested by the opening profanity. I don't see how I can use what they are saying to make a TUI.
The tone and presentation seem calculated to annoy HN readers (nice) but this article has a bunch of difficult-to-uncover details with just enough context to apply them if you actually have a use for them and a desire to.