For me it's not emotional, just purely business.
I have a hardware/software development environment that works the way I want it to. Setting up a new machine - or shaping an existing one that gets a new OS - is a huge undertaking that takes quite a while and then has lingering little details that nag at me for days afterward. It is horribly inefficient for me to go through the churn of a new tool, much less a new OS, when there is no additional deliverable at the end.
Here's how I approach such things: "What problem am I trying to fix?" In the case of Win7, the answer is "None". I am intimately familiar with where Win7 has hidden all the controls that affect what I do, and I have it tuned the way I need. Sure, I could invest a bunch of time (and likely money) to switch to something else, but when I'm done... what problem have I solved? What additional value have I received that improves my workflow? Until I have a real problem that interferes with my work, such an effort is a waste of time, a waste of money, and worst of all an opportunity cost because of the productive things I'm NOT doing while I'm wasting time on the "upgrade".
Specifically with respect to Win10, I'm against changing because of my earlier statement "I am intimately familiar with where Microsoft has hidden all the controls that affect what I do, and I have it tuned the way I need." I have several friends whose businesses run on software hosted on Win10 machines, and about once a month I get a call from one of them telling me that their business software or accounting package or whatever won't run that morning because Win10 "did an upgrade" overnight or over a weekend. The reason is always that the "update" has silently set one or more things to what THEY deem preferable/safer/whatever and this has disabled their applications. These guys lose 4-8 hours calling the application software vendor and working through their setup process just to get back to where they were the previous day. That represents a theft of valuable time and an opportunity cost that they neither wanted nor approved.
I cannot afford to let that happen to me. Is it possible to defeat the auto-update feature in Win10? I've heard conflicting answers but the bottom line is it shouldn't be a game of cat-and-mouse with your OS vendor to get and keep your machine configured the way YOU want it. If they have what they believe is a "better idea", propose it, accept my answer, and don't change it behind my back (and also don't keep nagging me about it!). I cannot afford the risk of downtime to unravel whatever well-intentioned "we know better than you" change(s) were inflicted upon the machines at the heart of my workflow.
What I need is an OS that lets me configure it the way I need, and stays there unless I - alone - decide to change it. The latest version of Windows that behaves that way is Win7. So there I stay, along with my workstation and my laptops, until I have a problem that Win7 cannot solve but Win10 or Linux can.