How Google's rumored 'Campfire' dual-boot Chromebooks may burn Microsoft
Google is rumored to be bringing a Windows and Chrome dual-boot solution called 'Campfire' to Chromebooks. Here's why that's bad news for Microsoft.
Seven years ago, Google began an assault on Windows PCs with its cloud-centric Chromebook PC alternative. Google's leveraging of a more secure, easier to manage and more affordable "PC" positioned Chromebooks for market success. Despite this success, however, Chromebooks' global market share still pales in comparison to Windows PC's seemingly indomitable presence.
Google remains committed to an unrelenting multifaceted assault on Windows PCs, in an attempt to position Chromebooks as the "PC" for the modern personal computing age. Android apps on Chrome, aggressive Chromebook ads, a strategic push in schools, Progressive Web App (PWAs) and low Chromebook prices are tools Google has and will use to make Chromebooks appealing to the masses.
Campfire, Google's rumored Windows and Chrome dual-boot solution, is just the latest, and possibly most important, tool in Google's arsenal to unseat Windows PCs as the PCs for the masses.
'Campfire' brings more than OSes together
The rumored "Campfire" code name for a solution that brings Windows and Chrome OS together on Chromebooks resonates with the concept of a real campfire that brings people together. In a twist consistent with the adage of keeping your friends close but your enemies closer, Google bringing Windows to Chromebooks is a self-serving strategy to amplify its attacks against Windows PCs.
Google's advertising onslaught outlining Chromebooks' advantages over PCs has had little meaningful impact on the PC market. Thus, getting Chromebooks into more customers' hands so they can experience Google's purported advantages is Campfire's aim. Campfire is a "Trojan Horse" strategy that'll potentially lure consumers with the Windows PCs they want on affordable hardware while also giving them the Chrome OS-based PC Google hopes they'll prefer.
Campfire is the delivery method Google may use to push its browser-based OS to the Windows PC-adoring masses. And this dual-boot system may succeed where aggressive ads have failed.
Google's coordinated Chromebook attack
Google has aggressively pushed anti-Windows-PC Chromebooks ads using taglines like:
Besides the above commercial, which uses misleading antiquated Windows alerts and OSes, most Chromebook ads appeal to a generation of smartphone users accustomed to simple, web-based light computing.
Google's ad assaults are complemented by OS-enhancing efforts such as Android apps and Google Play on Chrome (though most Android apps are optimized for phones). Also, PWAs, Google's hybrid web-app investment, may propel its browser-based OS forward as the user experience is made to feel more native and app-like. Google may strategically be using Chrome as PWA's "vehicle," and Campfire as Chrome's "vehicle," to the masses.
Additionally, as a derivative of Chromebook dominance in education, parents seeking a consistent home-school experience are purchasing cheap Chromebooks for their children. Finally, many small businesses are bypassing Microsoft's productivity solutions as they embrace more affordable Chromebooks and Google's accompanying productivity tools.
Google's Chromebook progress has occurred in a context where customers had to choose between Windows or Chrome OS. Campfire potentially removes some competing Windows PCs from the equation since consumers, schools and businesses will get both platforms on affordable Chromebook hardware.
Campfire may burn Microsoft
PC World published a piece highlighting the fact that Chrome OS and Windows on the same Chromebook hardware could ultimately hurt the more resource-hungry Windows.
The touted advantages of a simpler, faster and smoother Chrome experience on inexpensive hardware not optimized for Windows may be exaggerated when Windows is "unfairly" assessed in a "side-by-side" on-device comparison. One can imagine users' complaints as Windows drags on such hardware as Chrome zips along "proving" Google's claims.
Campfire, if real, may prove to be Google's most effective assault on Windows PCs.
Windows Central Newsletter
Get the best of Windows Central in your inbox, every day!
Jason L Ward is a columnist at Windows Central. He provides unique big picture analysis of the complex world of Microsoft. Jason takes the small clues and gives you an insightful big picture perspective through storytelling that you won't find *anywhere* else. Seriously, this dude thinks outside the box. Follow him on Twitter at @JLTechWord. He's doing the "write" thing!
#7 Visual Studio
- Hmmm, "browser." If people are thinking of Chrome OS in terms of Chrome the browser, Google has a problem.
People CHOOSE to use it. People can use firefox Edge, Opera, etc but choose to use Chrome. Should McDonald's be forced to sell Whoppers cause they outsell Burger King?
The perfect solution would be running Windows inside virtual software in Chrome, rather than the multiboot option though.
That's one leverage I think.
ChromeOS isn't made to play games and will only be like Apple back in the day. Good for educational use.
Gamers will buy a X86 PC and hipsters will buy a mac
"oh? my baby boy/girl self taught himself/herself how to use a "computer"? He/she's genius!!"
If a freshman graduate with 0 PC skills, only knows iOS, Android or Chrome OS, thinking those are the "computer" we use in the work environment...
He or she will have a hard time looking for job that can earn her 3k~10k+ a month tbh.
The reason why the chrome browser was removed from the store was because it was a crappy weblink install or something like that. And Chrome and Firefox are legacy apps, not efficient battery wise (coming from a firefox user). You can still install firefox etc outside the store so I don't see the problem. If they change that it would be a problem but they won't (why would they? they would lose more than they would gain).
Forced Cortana on us? Yes, like every other OS that has forced theirs, Apple and Siri, Google and Google Assistant (if that's it mange still).
Blocked other browers in the Store, mistaken again. Blocked other browser engines in the Store, like every OS Store. Edge on iOS uses a Safari Engine, Edge on Android uses the Chrome Engine.
In the meantime, this means another Windows license they sell--I'm sure they'll take the money.
- No, because the entire point of Windows is the ability to run on arbitrary compatible x86 hardware. As a matter of fact, this is something Windows is better at than any other OS in existence, period. Also, it means more license sales for Microsoft. Windows 10 on Chromebooks won't be free, a point many people seem to be forgetting.
- Exactly. The only problem with that is doing so requires strong hardware partnerships, which Google are notoriously bad at.
- Anyone who's already spent the money buying Apple's overprice hardware already likes macOS. Putting Windows on Macs doesn't change that.
One day, will we be telling Cortana to ask Alexa whatever happened to Windows ?
- It's amazing how often crashing comes up in Chromebook reviews. "Chromebooks suffer from the fact that Google is shoehorning a browser into an operating system"
- More like vice versa: shoehorning an OS into a browser. Chrome OS is a science project that runs on the Linux kernel masquerading as an actual product.
You are still buying Windows right? And why pay twice? Once for chrome and then for windows. When you can just buy windows machine and slap it with chrome. Chromebook still cannot run legacy win32 apps. You still need to load windows for it. And remember chromebook were supposed to be light? Apart from pixelbook there are hardly and devices with enough horse power in terms of space and computing power to run windows. Ya it may tempt people to buy pixel book .. which other wise is way too costly. Its much better to pay for surface book or macbook in what it asks for pixel book ($999).
2. Xamarin die-hards leave for Flutter/Dart because of reasons. Flutter is just a baby and it became better than Xamarin :))) now that's something embarrassing for Microsoon isn't it? There was enough proof that devs do not give a damn about MS's Xamarin tool, and now, their flee to the other side is yet another one.