Don't assume your readers know anything at all. Work out your assumptions and always state them.
I was curious, but not enough to do more than a cursory search. Apparently it's some game I've never heard of and am not curious enough about to read an entire article on it to learn what it can't run on and why porting it was worth it.
State your axioms. That means, step 1, work out what your axioms are, and specify them.
There's a sort of motto in technical writing: every page is page 1.
https://everypageispageone.com/
Don't assume your readers know anything at all. Work out your assumptions and always state them.
I was curious, but not enough to do more than a cursory search. Apparently it's some game I've never heard of and am not curious enough about to read an entire article on it to learn what it can't run on and why porting it was worth it.
State your axioms. That means, step 1, work out what your axioms are, and specify them.