I’m sorry, but I can’t agree with your arguments.
PDFs are an entirely different conversation. Since you’re using it as the basis for your argument, let’s talk about them, and why there’s zero reason for a UXer to rely on a PDF on a portfolio site, especially as a resume.
###PDFs Lack Responsive Design
A majority of today’s web traffic is done on mobile devices. PDF design is static, and attempting to view a PDF document on a mobile device can still be a frustrating experience, especially for those using out-of-date browsers or devices. From a responsive design perspective, PDFs are about the worst-possible solution to a problem.
###Default opening behavior for PDFs is browser-dependent
Some browsers will attempt to use a built-in PDF viewer. Others will attempt to open the document in whatever program is set as the default PDF viewer. Mobile, PC, iOS all affect how the browser attempts to handle PDFs. With a myriad of different solutions, there can be no expected behavior-- and no truly right away to code a link to such.
###PDFs have a host of security concerns
PDFs have played host to a bevvy of security concerns over the course of the years. I won’t go into details here, but suffice it to say that including a PDF on your site increases security considerations… considerably.
###There are many way better options than using a PDF for a resume
LinkedIn, in particular, comes to mind. There are also a host of different HTML/WordPress/Joomla/Etc. templates out there built specifically for resumes, all of which support responsive design and eliminate security concerns associated with target="_blank" and PDF files.
There’s no need to do things the hard way.
While we’re talking…
Sure, that will work, in some circumstances, but it’s far from foolproof. If you have concerns for supporting legacy browsers, for instance, it’d be a poor choice of defense. Also, notably, Edge does not support noopener.
Quite apart from that, it’s a hack that doesn’t address the main difficulty with opening links in new tabs or windows in the first place. Forcing new windows/tabs breaks expected functionality and is hostile to the user.