Feedback from new user - Install problems

[MALsPa]

And it's great that Debian has extensive documentation, but the world has evolved to the point that documentation should (rightly) be the last resort. It's the new world. You can literally judge the quality of a design by how small its manual can be.

Wow. I don't see things that way at all. I'll stick with the old school approach. The documentation is the first place I look, not "the last resort."

[debiman]

oh, the mysteriously slow network install, i remember being stumped by that.

well good you have it up and running, though you seem to be somewhat less than satisfied.

And it's great that Debian has extensive documentation, but the world has evolved to the point that documentation should (rightly) be the last resort. It's the new world. You can literally judge the quality of a design by how small its manual can be.

really?
"the world has evolved to the point that documentation should be the last resort."
wtf does that even mean? people are getting more and more stupid in this brave new world of yours? or cannot read anymore? everybody should just click the large, friendly OK button? software has finally developed self-awareness?
take this:

PS: i really need to add the word "pseudo-intellectual" to my criticism.

[GarryRicketson]

by spechter »You can literally judge the quality of a design by how small its manual can be.

Yes , exactly right, and I have learned to avoid poorly documented software and OS's when they have no manual, or very little (small), it is of very poor design, and reflects that the same probably applies to the software or OS .

When there are no manuals, nor good documentation for some software or
program, including a OS , I stay away from it.
The manuals and documentation are essential, especially for some one that has not used the software or OS before.

[RU55EL]

[...]You can literally judge the quality of a design by how small its manual can be.[...]

Yes, I also agree with this. The quality and completeness of software documentation is a direct reflection of the quality and completeness of the software. I find that complete and eloquent documentation is a good indicator of high quality software. I love it when I can install software that I'm completely unfamiliar with, but after an afternoon of reading the software documentation, can operate the software and make use of many nuances that I would never realize without the documentation.

When I first began using GNU/Linux software, I would play around and experiment with software to try and figure out how to use it. Somewhat frustrating. It wasn't long before I realized that evaluating the software documentation before attempting to use new software was much quicker and simpler. Sometimes poor quality, or lack of sufficient documentation, would be all that I needed to decide not to install the software. And, after evaluating the documentation, I usually had a fair idea how to properly use the software.

[Gaius]

..... but the world has evolved to the point that documentation should (rightly) be the last resort. It's the new world. You can literally judge the quality of a design by how small its manual can be.

That must be one of the dumbest things I've ever read.
This statement may be correct, if the software in question is designed for a single simple task (like creating a bootable drive from an .iso file, i.e. Rufus et al), but it certainly doesn't apply to something as complex as an OS.

I work with SAP software.
The documentation/manual for the basic module is approx. 1,500 pages, with another 800 to 1,000 pages for each of SAP's dozens of specialised modules.
Don't expect to be able to use the software expertly without having read a few thousand pages of documentation.
And if you know what SAP ERP systems are, you'll also know that they have no real competition. It's the best software available ... despite extensive documentation, lol.

You sound like somebody who'd be much happier with a Mac ... a "dongle" here and a "dongle" there ... and absolutely no need to use your own brain, ever.

----------

I won't even ask why 30GB for the / partition seem "dangerously small" ... my / is 20GB, and I expect to never use more than maybe 5% of that (currently 563MB).
Were you talking about a 2-partition setup, maybe, only / and swap?