“We're going to code in one IDE, one IDE only”
Motivation so low my boss wanna fire me

* cue N****s in Paris *

Yeah, we use "one" ide here too.

However, I set it to dark theme. Waiting for the question "What are you running?"

I would refuse.
If the boss flipped, I'd ask him if he wanted me to be productive or obedient. If the answer was the latter, I'd look for other work.

It isn't about the ide. Well it is, but only so much. It's about requirements that are objectively harmful to productivity, and by extension, the business.

This nigga be out here censoring nigga

Unless you have a very good reason for imposing an IDE, you can be sure that I'll try to circumvent that at some point.
Even if you do, if the IDE is eclipse, I will persevere in my effort to rid my computer and my workplace from this antiquated ball of hideousness, regardless of said good reason.
If the reason is that the build system relies on the IDE, and that IDE is eclipse, and the build system starts vomiting at the first sight of an obscure configuration file created by its predecessor by a single minor version, I will stop taking anything that is remotely connected to this IDE with even the smallest amount of seriousness, including the company forcing me to use it.
Looking at you NXP, I know most embedded developers seem to have no idea about the progress we made in the last 20 years, but you need to step up your game, or just stop obfuscating your build and debug chain behind the literal worst build system I have ever laid eyes on.

@Root

I would too, and I agree: it wouldn't be about the IDE. That's just indicative of the larger problem: a company culture of closed-minded subservience. The IDE would be the tip of the iceberg. Management that views itself as, "above" engineering, development, operations, and everyone else, and blindly refuses to acknowledge the intelligence of anyone who is not a manager.

It's a toxic environment, and I would want out. I like to think I would see that in the interview process though, and rule the place out for that reason.

@bahua Agreed. Major issues like that are usually apparent long before accepting the job.

If I can't use my beloved vim instead of some fat IDE, I don't think I'd be working there for very long...

Lol, my boss is lead programmer. He is also co-owner. I think he should have SOME say over how his company is run, or what tools are used. I mean in a mechanical shop he certainly has say over what tools to buy, brand and such. Really, we are getting pitchforks out over an IDE? Subservience? What about choosing to follow the lead of someone you can learn from? Why has my boss taken this route of choosing tools? Has he been burned in the past? Is there a quality issue such as formatting and tab usage which is solved by choosing a particular IDE? I may not agree with the solution, but I can see the reasoning.

In the places that count my boss is great. He listens, he respects my work, he genuinely wants me to enjoy my job, and he takes time to explain his decisions to me. If he wants to choose tools I am fine with that.

@Demolishun That's your boss. He's the rare exception in a world full of useless, deaf, egotistical managers.

I would still be annoyed at mandated tools, though.

Having a mandated OS is bad enough.