thanato0s

Author here. Thanks for the feedback!

I agree I could have been more direct, but I also wanted to explain the concept in detail, especially for beginners to understand it. When I was beginning in the industry myself, it was difficult for me to understand abstraction, and the articles I was reading didn't really improve my understanding; they often speak about the way to create abstraction instead of explaining what is abstraction and why we need to abstract things. I don't have the presumption I did better, but I tried.

I speak about simplicity in the article; therefore about complexity, but indirectly. Maybe I should have been more direct on that point though.

And I also do many analogies with abstractions outside of software development.

Writing from my TUXEDO InfinityBook Pro 14 - Gen7 in a train (important details :D), it runs very well with a good old Arch Linux and i3. The battery is really good!

Thanks! I got rid of it. Glad you liked the article!

Fixed. Thanks!

Yeah, I'm a bit confused by the concept of "controlling terminal". As I understand it, in the physical video terminal days, the console connected to the computer was the "controlling terminal", but I'm not sure how this concept translate in the terminal emulator world.

So, do you know what's the difference between the "controlling termina" and the "terminal connected to stdin"? I though the terminal connected to stdin was the controlling terminal...

Author here.

So the article begins with a story where a character, who doesn't know what he's talking about, try to mentor one of his colleague. It might be awkward though, and difficult to understand; sorry for that.

For sure this article was written better by others, but to me they were also lacking some stuff. I never found an article summarizing the whole story; most of the other sources were brushing away too much information for me to understand really why the TTY device had this weird structure.

But I guess not everybody will agree... and that's fine :)

woaaa looks really cool. Thanks for that! I might add all of this in the "references" section of the article.

I didn't try to be smart, I just got super confused what verb to use for telegrams (weirdly enough, to me "encoding" was only used in the context of computer... which is wrong; I tried to use "codify" also, but I'm pretty sure it's also wrong... from there the confusion spread in the whole article).

I'm not a native speaker. It doesn't excuse my mistake though.

Looks super interesting. Thanks!

If you see other errors and you have a bit of time, please let me know :)

Author here.

Yeah, my bad. I'm not a native English speaker, and somehow to me the word "encoding" was only used for encoding information on a computer. I was confused when I wanted to say the same thing for telegrams; I began to use "codify", and then "encrypt", which is obviously wrong.

I fixed the mistake. Sorry for that.

I tried to go through it multiple time, but I couldn't:

1. It's way too long, the complete stuff is ten of thousand of lines. 2. It goes into needless details, especially at the beginning (the "finding help" section is intense for example). It turns me off each time. 3. It's too dry, not really enjoyable to read to me.

I agree. That said, I also like to have a more complete guide and pick and choose what could be useful for me.

What do you mean by "infantilising tone"? If you have examples, I'd be glad to see them.

For the "expert", it's just to have a progression in the series. It's entirely subjective.

I read the whole user manual, it's a pain. There are too many details in many areas, not enough in others. It's way too long, too. I don't see a beginner reading that and getting the info he (or she) needs before giving up.