I need to say something that will make many of you deeply uncomfortable: your refusal to call fascism “fascism” is not sophistication—it’s complicity.
When Donald Trump posts explicit orders for “REMIGRATION” and “Mass Deportation Operations” targeting American cities because they are “the core of the Democrat Power Center,” that’s not “controversial immigration policy.” That’s mass deportation directed against political opponents. When federal troops deploy against American civilians exercising constitutional rights, that’s not “enhanced law enforcement.” That’s military occupation. When the systematic dismantling of democratic institutions gets described as “political polarization,” that’s not nuanced analysis—it’s linguistic evasion that enables the very thing it refuses to name.
The sophisticates hate this clarity. They prefer the safety of euphemism, the comfort of complexity that never quite arrives at moral judgment. They speak of “concerning developments” and “troubling trends” while democracy burns around them. They perform nuanced understanding while fascism consolidates power through their very refusal to name it.
But here’s what they don’t understand: authoritarianism thrives in ambiguity. It requires linguistic fog to operate. It depends on our unwillingness to call things by their proper names. Every euphemism is a small surrender. Every hedge is a tiny collaboration. Every refusal to speak plainly is a gift to those who profit from confusion.
Language shapes consciousness. When we refuse to name what we see clearly, we don’t just fail to communicate—we erode our collective capacity to think clearly, to feel appropriately, to respond effectively. We make ourselves complicit in our own moral disorientation.
George Orwell understood this when he wrote that “political language is designed to make lies sound truthful and murder respectable, and to give an appearance of solidity to pure wind.” But he was describing propaganda techniques used by totalitarian regimes. What we face now is worse: the voluntary adoption of euphemistic language by people who should know better, who pride themselves on seeing clearly, who claim to defend democratic values.
We are doing the propagandists’ work for them.
Consider how this linguistic distortion operates in practice. When mass deportation operations targeting millions of people get called “immigration enforcement,” we’re not being diplomatic—we’re making state violence psychologically easier to accept. When systematic attacks on democratic institutions get labeled “political disagreements,” we’re not showing balance—we’re normalizing authoritarianism. When obvious lies get treated as “alternative perspectives,” we’re not being fair—we’re weaponizing false equivalence against truth itself.
The euphemism isn’t just descriptive failure—it’s moral failure. It changes how people process information, how they make decisions, how they understand their own moral obligations. When you call fascism “populism,” you’re not just using imprecise language. You’re making it easier for people to support fascism without confronting what they’re supporting.
Hannah Arendt spent her life studying how ordinary people enable extraordinary evil, and she identified linguistic evasion as one of the primary mechanisms. In Eichmann in Jerusalem, she showed how bureaucratic language—“evacuation,” “resettlement,” “special treatment”—allowed participants in genocide to avoid confronting the reality of what they were doing. They weren’t murdering children; they were “processing population transfers.” They weren’t operating death camps; they were managing “facilities for the final solution.”
The language didn’t just hide the reality from others—it hid it from themselves. It allowed them to participate in evil while maintaining their self-image as decent, law-abiding citizens following proper procedures.
Arendt’s insight was that evil becomes possible not primarily through active malice but through the refusal of ordinary people to see and name what’s in front of them. The “banality of evil” is fundamentally about linguistic evasion enabling moral evasion. When we stop calling violence violence, we make violence easier to commit.
This is what we’re witnessing now. The systematic training of a population to see clearly but speak obliquely, to understand precisely but describe vaguely, to recognize authoritarianism but call it something else. We have become a society of people who know exactly what’s happening but lack the linguistic courage to say so.
Consider how this evasion plays out in our current discourse:
We don’t say “Trump is implementing fascist policies.” We say “Trump’s approach raises concerns about democratic norms.”
We don’t say “Republicans are supporting mass deportation operations.” We say “There are disagreements about immigration enforcement strategies.”
We don’t say “Conservative media spreads lies designed to enable authoritarianism.” We say “Different sources present different perspectives on complex issues.”
We don’t say “MAGA supporters have chosen to enable fascism.” We say “There are legitimate grievances driving political polarization.”
Each euphemism makes the reality a little less clear, a little less urgent, a little less morally demanding. Each hedge creates space for people to avoid confronting what they’re witnessing or participating in. Each refusal to name plainly is a small act of collaboration with the forces that depend on confusion to operate.
When Trump orders ICE to conduct “Mass Deportation Operations” in cities he identifies as “the core of the Democrat Power Center,” that’s not immigration policy—it’s the use of state violence against political opponents. When he calls for “REMIGRATION” of millions of people, that’s not border security—it’s forced population transfer. When federal agents separate families and detain children, that’s not law enforcement—it’s state-sanctioned cruelty.
The defenders will say “the law is the law”—as if legality were equivalent to morality. But slavery was legal. Segregation was legal. Japanese internment was legal. Every authoritarian regime in history has operated through law, not despite it. “The law is the law” is not a moral position—it’s moral abdication disguised as principled governance.
Law without moral foundation is just organized violence. Rules without ethical grounding are just systematized cruelty. When your only defense of a policy is that it’s technically legal, you’ve already admitted it’s morally indefensible.
The sophisticates will tell you that such plain language is “inflammatory,” “divisive,” “unhelpful to productive dialogue.” They’ll suggest that calling fascism “fascism” alienates potential allies, shuts down conversation, makes compromise impossible.
But here’s what they’re really saying: they prefer the comfort of ambiguity to the responsibility that comes with clarity. They’d rather maintain the illusion of reasoned discourse than confront the reality that one side has abandoned reason entirely. They want to keep playing by rules that the other side has explicitly rejected.
This isn’t sophistication—it’s cowardice. It’s the intellectual’s version of appeasing authoritarianism through linguistic accommodation. It’s the belief that if we just find the right words, the right tone, the right approach, we can somehow reason with people who have chosen unreason as their governing principle.
But you cannot have productive dialogue with fascists about the merits of fascism. You cannot find common ground with people who reject the premise of shared reality. You cannot compromise with those who view compromise as weakness and good faith as stupidity.
What you can do is name what they are doing clearly enough that people understand what’s at stake and what choice they face.
The power of plain naming is that it forces moral confrontation. It makes people choose sides. It strips away the comfortable distance that euphemism provides. It demands that people acknowledge what they’re actually supporting rather than hiding behind sanitized language.
This is why authoritarians work so hard to control language. They understand that linguistic precision is the enemy of moral confusion. That clear naming makes their projects harder to defend. That euphemism is their friend and clarity is their enemy.
They want us to call their fascism “nationalism.” Their lies “alternative facts.” Their cruelty “tough love.” Their mass deportations “border security.” Their authoritarianism “law and order.”
Every time we adopt their language, we do their work. Every time we refuse to name their actions plainly, we make those actions easier to defend, easier to rationalize, easier to continue.
When we refuse to call fascism “fascism”, we don’t make fascism less dangerous. We make ourselves less capable of recognizing and resisting it. We participate in our own disorientation. We become accomplices to our own confusion.
The courage to name things plainly is not the courage to be harsh or inflammatory. It’s the courage to accept the responsibility that comes with seeing clearly. It’s the courage to abandon the comfortable illusion of neutrality and acknowledge that some things cannot be straddled, some positions cannot be hedged, some realities cannot be euphemized away.
To say that systematic deployment of federal troops against American cities constitutes military occupation is not inflammatory—it’s accurate. To say that mass deportation operations targeting political opponents constitute fascist policy is not hyperbolic—it’s precise. To say that obvious lies designed to enable authoritarianism are lies is not divisive—it’s necessary.
The alternative to plain naming is not diplomatic nuance—it’s moral blindness. It’s the systematic erosion of our capacity to recognize authoritarianism when it appears in familiar forms, speaking familiar languages, wearing familiar clothes.
Evil depends on our unwillingness to call it evil. Fascism depends on our refusal to call it fascism. Lies depend on our treatment of them as “alternative perspectives.” State violence depends on our description of it as “tough policy choices.”
The moment we name these things plainly, we restore the moral clarity that makes effective resistance possible. We acknowledge what we’re actually facing. We accept the responsibility that comes with seeing clearly. We choose truth over comfort, accuracy over diplomacy, moral clarity over intellectual sophistication.
This is not just a linguistic choice—it’s a moral one. Every time we speak plainly about what we’re witnessing, we strike a blow against the forces that depend on confusion to operate. Every time we call fascism “fascism”, we make fascism a little harder to defend. Every time we name state violence as state violence, we make such violence a little less acceptable.
Two plus two equals four. There are twenty-four hours in a day. And Trump’s mass deportation operations are fascistic displays of state violence targeting political enemies whether we have the courage to call them that or not.
The difference is not in the reality—the difference is in our capacity to respond to reality appropriately.
Name it plainly. Not because it’s easy, but because it’s true. Not because it’s comfortable, but because comfort in the face of authoritarianism is itself a form of collaboration. Not because it’s diplomatic, but because diplomacy with fascists is enabling fascism.
The revolution is linguistic honesty. The rebellion is calling things by their proper names. The resistance is refusing to participate in the euphemistic erosion of moral clarity.
Say what you see. Name what you know. Call fascism fascism.
Every minute of every day.
Remember what’s real. Because the alternative to naming fascism clearly isn’t moderation or diplomacy—it’s surrender.
Mike Brock is a former tech exec who was on the leadership team at Block. Originally published at his Notes From the Circus.
![]() |
Andrea and I after wowing the Smithsonian. |
Google has just announced the acquisition of Fitbit for a cool $2.1 billion (USD). The move will undoubtedly drive change in the industry, though, not as much as one might think – at least initially. Don’t worry, I’ll explain in a moment. Like any acquisition, it needs to actually be approved by regulators, but that’s largely just a formality for this particular instance. Google & Fitbit expect that to occur in 2020, which is when the real work can begin.
It’s probably best to start off with where these two companies’ products fit in the market today. Fitbit, of course, being one of the biggest wearable players, though sliding in the last few years as Apple, Samsung, Xiaomi, and Huawei (and to a lesser but still visible extent Garmin) have seen their sales increase significantly (keep in mind that global IDC tracking isn’t a great indicator of North America/European sales). Apple sells approximately 20-25 million Apple Watches per year (and more than double that for the entire ‘wearables’ category). Whereas Fitbit has been in the 13-20 million ballpark the last few years.
Google meanwhile hasn’t sold their own watch device. Instead, they have Wear OS (previously known as Android Wear). That’s an operating system that’s largely focused on the higher end smartwatch with a similar battery profile as the Apple Watch. Meaning, it’s designed to roughly last 1-2 days. Exactly how long it lasts depends heavily on the exact partner hardware. For example, Polar’s M600 (Wear OS) fitness-focused watch tends to last longer than some other companies’ thinner watches. And similarly, we saw Apple decrease actual battery life this year in the Series 5 from past years. Again – it all depends on the hardware under the covers.
Battery aside – Fitbit and Google do have wearables overlap, but it’s kinda messy overlap. For example, Fitbit’s top-end device – the Ionic (priced $200-$250 depending on tidal and moon phases) has music, GPS, and contactless payments. Wear OS devices in that category tended to start from the same price point and increase depending mostly on materials used. Fossil had countless watches all in that price range. However, Wear OS wasn’t situated well for the less expensive all-day activity trackers that made Fitbit popular.
The battery demands of Wear OS (like WatchOS from Apple) simply didn’t allow that. They are blow-torches in the battery department in comparison to the much longer-lasting Fitbit (and Garmin/Suunto/Polar/etc…) wearables. A large part of that is the screen – Wear OS devices tended to have far more vivid screens. And as we saw this year with Fitbit, Apple, and Garmin introducing always-on screens like Samsung has had – when enabled, it more than halves the battery life.
Next, if we look at the health side of things- while Google has their health platform, it doesn’t have anywhere near the depth of Fitbit from a social fitness tracking standpoint. Nobody really does. That’s why Fitbit has succeeded to date: Their platform is engaging. Even looking to Apple, for example, one can see the huge lack of social engagement between Apple Watch users. You can do basic competitions, but the methods and challenges that Fitbit has, exceeds everyone else’s capabilities.
So the real question here is: Which OS wins?
The easy answer is ‘Wear OS’, and to an extent, Google says that as well. Their SVP of Devices and Services, Rick Osterloh noted that this “an opportunity to invest even more in Wear OS as well as introduce Made by Google wearable devices into the market.”
But the challenge with that broad-brush statement is somewhat twofold:
A) Wear OS isn’t viable for Fitbit’s non-smartwatch activity trackers
B) Wear OS is still a battery beast
Not to mention that Wear OS still has relatively little uptick in apps (just like Fitbit does). Sure, the app stores are full of apps, but very few that you’ll actually use beyond a cursory one or two time glance.
Realistically – Google and Fitbit are going to have to keep both platforms running, likely for many years. But that might not be all bad. Take the lower end wearables (the Inspire and Charge families), there’s no reason to even bother trying to port Wear OS onto these devices. Instead, Fitbit/Google will likely keep them on the platforms they’re on (the core Fitbit platform that was there prior to FitbitOS proper). They can add in things like Google Assistant down the road (they added Alexa to the Versa 2 this past summer) and since there’s no apps on these, much of the benefit of Wear OS is negligible or non-existent.
Meanwhile, you’ve got the Versa and Ionic lineup. These have strong overlap with Wear OS and are likely to be canned from an operating system standpoint. At first glance, you might assume that FitbitOS is newer than Wear OS (or Android Wear). But in reality, one has to remember that FitbitOS is essentially just a spin-off of the Pebble operating system (remember, Fitbit bought Pebble). In fact, some of those lead Pebble engineers are still there leading this platform. But, I can’t see any scenario where they keep FitbitOS. There’s simply no reason to.
All of the fitness and lifestyle type interfaces and functionality that run on a Versa or Ionic type watch can easily be ported over to run on Wear OS. Sure, there will be differences, but because Fitbit’s products are fairly modular and also less deep in individual functions than say something like a Garmin watch, it’ll be easier to stock replace pieces like the music player or even basic run tracking. Wear OS does those just fine today – and not appreciably different than Fitbit.
So in short – I’d argue FitbitOS goes away, Wear OS continues, and basic Fitbit trackers stay the course on their proprietary platform as they have for more than a decade.
And this is where things get a bit messy. See, they say almost nothing about existing Fitbit users in their press release except this single line item:
“Consumer trust is paramount to Fitbit. Strong privacy and security guidelines have been part of Fitbit’s DNA since day one, and this will not change. Fitbit will continue to put users in control of their data and will remain transparent about the data it collects and why. The company never sells personal information, and Fitbit health and wellness data will not be used for Google ads.”
At first you might think – great, that means all is well, right?
Not so fast. What’s missing in this entire press release is any commitment whatsoever to maintaining the Fitbit platform or ecosystem. Bizarre as that omission might seem (since that’s what Fitbit is so well known for), it means Google is keeping all options on the table – including burning down that ecosystem to fold into other projects (which historically the company tends to do for acquisitions, they’ve acquired at last 229 companies as of today).
In fact, when I asked Fitbit’s PR team about any commitment (at all) to existing Fitbit users – they said:
“The release and blog post are the comments for now.”
In other words – ‘no comment’.
That could be taken both ways. But I know better. We all know better.
When it comes to acquisitions, if a company plans to keep something – they say it (and usually say it loudly and proudly – like they did above with the security/privacy bits). If a company has even the slightest thought of not keeping it, they say nothing. And if the company plans to burn it down, they definitely say nothing.
This is a pretty big deal for neither Fitbit or Google’s statements to address.
They do however offer one other line item around compatibility, which is:
“Fitbit will continue to remain platform-agnostic across both Android and iOS.”
And that makes sense. After all, Wear OS works today on iOS and Android devices, and there’s no reason to shift away from that. Most companies in this segment find that they have 60-70% iOS market share for consumers of these types of devices (as compared to far higher global Android market share). Thus, ditching iOS support would be a self-inflicted wound.
Interestingly, Garmin was asked this very question on their earnings call this week by Robert Spingarn of Credit Suisse. CEO Cliff Pemble said the following:
“So we’ve seen the speculation obviously around Fitbit and Google. It’s really hard to say what we can think about that without any kind of formal announcement and whether or not it’s even a real thing.
We believe that Fitbit’s customer base is very different from ours and our product focus is also different. So it’s not something that we believe impacts us and we’re not worried about it.
In terms of other opportunities, we look at every opportunity basically in terms of what it can bring to Garmin both in terms of technology or product lines. So we would evaluate any of those opportunities based on that and what we can achieve with it going forward.”
Of course, he brushes off the concern – but what he states in the middle paragraph is mostly untrue. Fitbit and Garmin have always had huge overlap at the low-end, and have always competed head to head there. They’ve referenced Fitbit as a competitor in their earnings calls and sales guidance for years.
However – there’s also some nuances to what he says. What he’s probably trying to say is that ‘A Garmin customer is less likely to become a Fitbit customer, whereas a Fitbit customer is more likely to become a Garmin customer’. Meaning that the athlete-focused feature set of a Garmin watch is easier to ‘upgrade’ into from a Fitbit device, but harder to go back to a Fitbit device once on a Garmin (speaking purely from a feature standpoint). They have overlap, but the bulk of Garmin’s *revenue* comes from their mid-range and higher-end devices, not from the activity trackers that they still compete with Fitbit on.
The other two players this impacts are Apple and Samsung.
But predicting how it’ll impact them is a tricky beast. Obviously, this will give Wear OS strength over time, but not immediately. Apple’s integration between phone and watch is second to none. The cleanliness of that integration is in many ways the cleanliness of Fitbit as an ecosystem. Whether or not Google can find a way to port not just the overarching fitness platform to Google proper, but also retain that cleanliness remains to be seen.
I don’t see this making any appreciable negative impact on Apple (or Samsung) anytime soon. I could, however, see this having a detrimental effect on Fitbit sales near-term, whereby people actually end up on an Apple Watch (or other competitor) due to uncertainties around Fitbit. As I often say, the ‘Best Buy’ effect. Meaning, consumers of this type of device are often heavily reliant on advice from someone in a brick and mortar store like Best Buy, who can easily make an off the cuff statement when asked by a consumer which device is recommended – only to have that person respond ‘Well, Fitbit just got bought by Google and we don’t know how that’ll end up’. The person turns and buys a competitor device instead.
I’m never one to want to see less competitors in the space. But I’m not sure there was any other realistic option here. No, Fitbit wasn’t going to die this year or next year, or even in 2021. However, they were facing an issue of not being innovative anymore, which in turn causes loss of market share. Their Versa 2 launch this past summer was a prime example of that – where the global reaction was ‘shrug’. Combine that with the continued shift from lower-end activity trackers to highly integrated smartwatches like an Apple Watch, was becoming the perfect storm for the company.
They couldn’t really seem to fully lock and complete the various projects they’d announced. Whether that was the sleep tracking that took over a year to get out the door, or even broader music streaming services adoption. It was like things were stalling, as if the ship was just getting too heavy.
I think this acquisition though gives Fitbit a second life – but also gives Google a second life in the wearables realm. Remember, aside from Fossil, almost nobody was rolling out new watches with Wear OS. It had kinda sputtered.
I’m hoping we look forward to Fall 2020 with a Google Watch announcement. Something that can compete with Apple Watch in the mass market arena, but perhaps also have the flexibility to compete with companies like Garmin and others in the athletic focused space.
With that – thanks for reading!