Working offline is perfectly doable. I've grown not to rely on connectivity when I was living in a rural area with spotty/slow 3g connectivity at best. Not rel

Working offline is perfectly doable. I've grown not to rely on connectivity when I was living in a rural area with spotty/slow 3g connectivity at best. Not relying on network connectivity in my entire pipeline is still today a big discriminator in the stack I choose. The biggest downside was, and still is, documentation. I had a script that scavenged the installed packages and downloaded all relevant documentation packages automatically, along with a local indexing service (I'm still using and recommend "recoll"). There is a humongous gap between libc/posix (anything instantly accessible with "man" with stunning quality) and pretty much everything else. Even python, which has a decent "online" (built-in) reference, is not as convenient and easily searchable when looking at the html manual itself. A local search index doesn't have the inference power of something like google to point you to the right example you're looking for something in cppreference. And once you pass the top 10 best documented packages you have on system, you realize how downright bad everything else is documented and how much you rely on the search engine to fill the gaps from unofficial sources. For me at least, documentation was always THE problem.