....'here's a welcoming hand'...
I considered that because I didn't want it to seem like
'here's a slap in the face with the tech'
What I was hoping for is to eliminate those concerns if someone isn't willing to give up Windows based software. It was a concern I had and a deterrent. Because so few people need it I wouldn't mention resource consuming software. But if anyone around here does use use it and they could share good experience I definitely would include that.
... even if your personal situation made it difficult due to computer issues.
Listing reasons for wanting to know about the solutions were for all the people who would probably tell me about all the alternatives. I wanted express how important those things could be for
someone like me. I want to be able to refer to someone elses experience with a 'VM' inside Linux and/or dual installs because I don't have it and now I can't get it. I heard about those, but I didn't hear about someone's personal experience. Personal experience is much more meaningful than suggestions.
I wouldn't mention the computer specific problems. They have nothing to do with Linux. I wouldn't have mentioned anything about UEFI or Secure Boot settings either.
After all the frustration, I could have easily gone back to Windows after the ASUS got home from the hospital. I was originally going to keep Windows on a separate drive so I could use those programs. On the day I got it running again, I copied the files I didn't back up. The only reason I didn't erase Windows on the 2TB drive right away is because I wanted to double check for files I might have missed. I was too excited to get going with Linux so I installed it on my second drive. After I checked for files again I deleted Windows.
Essentially It didn't take much to make up my mind. I like Linux THAT much. All the issues with the other computers that delayed a full install puts a fine point on how sure I was when deleted the Giant.
If they want to know how there are 1,000,000 pages telling them so...
There are a zillion technical articles...
Those were intimidating until I tried Linux. My fears were relieved. I should say so because it might be useful to someone.
References to basic "Getting Started" guides that are
actually helpful to a newbie is something I would have liked. When I'm talking about something I know very well, for example all the technical terms of botany, propagation, soil, architectural drawings, I forget that people who are hearing these things for the first time can't follow a single thing I'm talking about. That's how those articles are written. It's like trying to make sense of a foreign language.
I have dumb things down so I can be understood. I would really like a Linux guide written that way.I look things up everyday so I can figure out how to do something. The very first thing I have to do is figure out what that thing is called. If I don't know how to say something in Linux, I'll get a lot of unrelated, meaningless or useless information in terms of what I'm trying to do.
This would be a very personal article.
Make sense?
Again, you're under no obligations. Plus, I can work with all sorts of content to make it applicable. It often takes longer to edit something that I didn't write, but I'm fine with that.