"Hog" implies bloat to me? Video's hard work, though, and OBS will chew a CPU but it really needs to (unless you use a GPU encoding solution like NVENC, but there are quality concerns there). I have a second PC--actually a pretty nice 4U rackmount in a 6U wheelie with my audio interface--dedicated to video crunching and audio mixing for when I do livestreaming events for folks.
Before, I was using a 2015 MBP and it was having a VERY hard time handling the streaming at 1080P (mind you I was running 2 screens off of it).
I am not sure it's a hog because of bloat, it's just that you need a more than average computer to stream with good quality.
Funny story is that once I clicked stop on the stream and it kept streaming. Showing me having a phone call, going on Facebook and just continuing with my day. I had to just shut down my computer because OBS would just not stop.
On the new iMac I had absolutely zero issues with it and I am running it with 2 screens and 5K on the main screen.
Also use twitter etc. to promote yourself.
Some solid tips on here and OBS is a surprisingly good piece of software but it can be a resource hog at times.
The hardest thing about it is to keep the schedule and be emotionally available when the stream comes on. I wrote about it here [1].
What I like the most is working through a project in stages on the stream. People can connect with the project and also contribute to it. Working on one-offs tutorial style did not really work for me.
I stream full stack content. From Node.js to Golang and even Devops. [2]
The screen to not show the desktop when doing secret things is good, however, as mentioned here I would definitely recommend a second screen. It changes the way you work a lot.
[1] https://fullstack.network/announcing-my-most-ambitious-strea...
[2] https://www.twitch.tv/kensodev