at your text editor, your IDE, and include a library and just see what you can do with it. Which, I mean, that's a valid way to learn a library, believe me. It is just, it's not quite as natural as learning the commands that are functional on an everyday basis. And very frequently the default of those applications does something useful. Whereas with a library, because they very frequently do so many minute little specific things, even if you are just doing a little test run in a programming language, you do one or two things in a library and as far as you know, you haven't done anything. All you've done is, I don't know, queried the size of a window. You know, like, well, great. Now what? What do I do with that? How do I even get that output? Like the program didn't fail to compile, so I guess it must have worked, but I don't, you don't see the difference. It doesn't do anything for you. And I think that's why Bash is such a very, very useful introduction into the concept of (41/54)
You are viewing a single comment's thread from: