View source for Essays:TNT: free tech books/ru

<languages />

'''Автор''': Евгений Голышев

'''31-го мая 2024''' я запустил каталог технической литературы, распространяющейся под открытыми лицензиями, где все книги можно скачать бесплатно. Каталог получил название TNT (от '''T'''utorI'''n'''.'''T'''ech) и реализован в виде [https://t.me/TutorInTechBot?start=wiki Telegram-бота], в котором можно создавать свою библиотеку, иметь к ней доступ с любого устройства, делиться книгами и еще куча других вещей, но обо всем по порядку.

<span id="High-quality_vs._Free"></span>
== Качественный и/или бесплатный ==

Идея '''качественной''' и в то же время '''бесплатной''' технической литературы сегодня все еще может казаться нереальной, как четыре десятилетия назад то же самое казалось в контексте программного обеспечения. "Открытое письмо любителям"<ref>Оригинальное название "Open Letter to Hobbyists".</ref>, в котором '''Билл Гейтс''' (Bill Gates) поставил под сомнение коллективную работу над программным обеспечением (communal software development), может и сейчас откликаться в сердцах немалого количества людей, если речь зайдет о книгах. В том письме в '''феврале 1976''' Гейтс писал<ref>https://en.wikipedia.org/wiki/File:Bill_Gates_Letter_to_Hobbyists_ocr.pdf</ref>:

<blockquote>
Кто может позволить себе профессионально работать ни за что? Какой энтузиаст способен убить три года своей жизни на программирование, исправление ошибок, документацию, и потом раздать все это бесплатно?
</blockquote>

Но через семь лет '''Ричард Столлман''' (Richard Stallman) запустил проект '''GNU''', с которого началось движение за '''свободное программное обеспечение'''. Оно показало, что коллективная работа над программным обеспечением с его бесплатным распространением – вполне жизнеспособная идея.

Что касается книг, то революция там давно произошла: качественная и бесплатная техническая литература существует уже более четверти века. Одним из ярчайших примеров является руководство '''Linux From Scratch''', выпускающееся с '''1999''' под открытой лицензией, которая разрешает '''свободное распространение''' и '''создание производных работ'''. Так почему паучье чутье подсказывает, что качественная книга не может быть бесплатной? Я думаю, дело в том, что книги под открытой лицензией не управляют печатным миром в отличие от свободного и открытого программного обеспечения, на котором зиждется современный высокотехнологичный мир. Я надеюсь, что TNT сможет внести свой посильный вклад, чтобы исправить сложившуюся ситуацию.

<div lang="en" dir="ltr" class="mw-content-ltr">
== Release Gates ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Alright, we've figured out that technical literature can be both high-quality and free. However, to rephrase Gates' words, one might ask: "''What hobbyist can put three man-years into writing a book, correcting typos and inaccuracies, and distributing it for free?''" I can suggest several possible reasons why this might be beneficial for authors.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== The Free Distribution Can Expand the Audience For a Book ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Often, when books under open licenses are published by educators or professionals whose work benefits from widespread publicity, it becomes essential for as many people as possible to evaluate their scholarly contributions. Imagine two scenarios. One author says, "''I wrote a book, here's the link,''" while the other says, "''I wrote a book; if you're interested, you can purchase it here,''" and shares the link. Whose book are people more likely to check out? For me, the answer is clear as day. The difference may not be about the money but rather the number of steps required to reach the goal.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Given enough eyeballs, all bugs are shallow ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
"Given enough eyeballs, all bugs are shallow" is [https://en.wikipedia.org/wiki/Linus%27s_law Linus's Law], which can be effective not only in software development but also in writing books, considering typos and inaccuracies as bugs. As in the previous case, free distribution of a book expands its audience. Within that audience, there will undoubtedly be both readers and writers who will eagerly spot errors and suggest corrections.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Free Distribution Prolongs the Life of the Work ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Here, I want to immediately proceed with examples.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== Linux From Scratch ====
This book explains how to build your own GNU/Linux system from scratch, component by component. If readers are ready to dedicate a significant part of their lives to its reading, they'll come away with a clear understanding of the components that make up a modern GNU/Linux system, along with how they're configured and built.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The first version of this guide was released in December '''1999''', and its original author, '''Gerard Beekmans''', hasn't been actively involved in the ongoing development of the project for quite some time. However, new versions of his work continue to be released consistently twice a year.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== The Linux Kernel Module Programming Guide ====
This book discusses the internal mechanisms of the Linux kernel to teach readers how to develop modules for it. Originally written by '''Ori Pomerantz''' for Linux 2.2, the first version of the guide has not been preserved. However, since Linux 2.2 was released in '''January 1999''', it's likely the work was published around that time. '''Jim Huang''' is currently actively updating the book. In addition to Pomerantz and Huang, three other authors also contributed to the book.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Just think, these books have been around for over a quarter of a century, and this is largely thanks to the open license. However, some might argue with me, stating that history has shown instances where commercial publishers have taken over someone else's work when the original authors were unavailable for some reason. For example, after the death of '''W. Richard Stevens''' in 1999, '''Stephen A. Rago''' continued his monumental work titled [https://en.wikipedia.org/wiki/Advanced_Programming_in_the_Unix_Environment Advanced Programming in the Unix Environment]. I would not insist that open licensing is the only way for a book to avoid obscurity. Certainly, that's not the case. But I'm convinced that a book under an open license has a lower chance of becoming "orphaned."
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is by no means an exhaustive list of reasons to publish a book under an open license. There are several more that could be mentioned, but it's time to move on.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Hybrid Format for Book Distribution ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The free distribution of a book doesn't exclude cooperation with a commercial publisher. One does not interfere with the other. As an example, I would like to mention the book [https://en.wikipedia.org/wiki/Free_as_in_Freedom Free as in Freedom], which is dedicated to '''Richard Stallman''', the founder of the GNU Project and the free software movement. This book was published by '''Tim O'Reilly''''s publishing house under the '''GNU Free Documentation License 1.1''', a license that the author, '''Sam Williams''', insisted upon. Since the license permitted derivative works, the book's central figure, Stallman, released an expanded and revised version several years after its initial publication, which he called Free as in Freedom 2.0. The second edition was published by the Free Software Foundation.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is just one example of O'Reilly publishing a book under an open license. In the past, his publishing house did this quite frequently<ref>The list of books under open licenses from O'Reilly can be found [http://web.archive.org/web/20240113043735/https://www.oreilly.com/openbook/ here].</ref>. Other well-known publishers of technical literature, such as '''Apress''' and '''No Starch Press''', continue to do so even today<ref>The list of books under open licenses from Apress can be found [https://apress.com/gp/apress-open/apressopen-titles here].</ref>.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== TNT and the Open Print World ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Great, we have established that authors are motivated to publish their books under open licenses, and they can easily be found online and downloaded for free. But why TNT? As a library for tech enthusiasts, TNT offers the following features.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Maintaining an Up-to-Date Catalog of Books ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Working with books under open licenses sometimes resembles software development: they can be updated regularly, and some even have a fixed release cycle. Consequently, it's essential to keep track of updates, which is precisely the responsibility of TNT. Typically, a new version of a book appears in the catalog on the release date, and users receive notifications about the updates.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Always Accessible ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Thanks to its implementation as a Telegram bot, users can access their library from any device. For example, you can start browsing the library on your phone and then save a preferred book to your favorites, making it easy to find later on your laptop.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Unique Content ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
TNT is largely a media project. Descriptions and sometimes even covers for the books are created by the TNT team.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== References ==
</div>

<references />