As to the Beta vs VHS battle, I'm old enough to remember that one. Sony had a big disadvantage right from the start: Beta was orignally only good for one hour, VHS was originally good for two hours. And very soon, many more than just two hours. Practically a no-brainer, for anyone wanting to use these VCRs for time-shift recording.
And also, even if the masses may not have obsessed over these other differences, VHS was designed from the start to support stereo sound, even BEFORE VHS HiFi, whereas Beta did not support stereo until much later, when they too introduced HiFi audio.
And one more. VHS would retract its heads during rewind, whereas Beta would not. This meant head wear and gunking up whenever you had to rewind a tape. Or you had to buy one of those separate rewind boxes.
I know that years down the road, Beta improved on all those fronts. But by then, VHS had won. If other OEMs thought along the same lines as my obsessions of the day, you can see why they picked VHS.
Same can happen here, right? Unless Microsoft does something very uncharacteristic, I don't see why they would want to become a closed shop. Even if they will be one of the hardware players.
I still don't see that, Junko or Rick. Microsoft is hardly the only company building super portable tablet-like devices with Windows 8, even if it's one of the players in that field. If you consider the Surface Pro as a tablet, then what about Asus, Lenovo, Acer, Razor, HP, etc., who build very similar devices?
I wouldn't assume that just because Microsoft buys Nokia phones, that no one else will be permitted to build a Windows phone. I wouldn't put a negative spin on this, at the outset. Microsoft might very well NOT want to emulate Apple's closed shop environment. Doesn't mean these tablets and phones can't succeed. They seem to have gotten good reviews.
Further, managing "partner" OEMs is harder than we all think.
I know this from my humble experience of having worked at JVC -- which inveted VHS but needed help from OEMs to sell VCRs and promote VHS.
Sony also looked to sign up system OEMs adopting Betamax in hopes of presenting a united front of Betamax camp, but the company never managed to get the level of support and commitment from its OEM partners.
The art of managing "partners," and the human psychology behind it, never changes, even after the world has gone digital.
I think Rick outlines the challenges Microsoft faces correctly in his questions above.
In other words, the context of the story is not about whether Microsoft will succeed with Surface Pro, etc. (vs. Apple). Rather, a bigger question is if Microsoft will successfully change its tried and tested business model traditionally heavily dependent on its PC OEMs.
Apple never had that problem, because the Cupertino company has always done things on its own (or go it alone).
Meanwhile, Microsoft's past success is built on the Windows-faithful PC OEMs. Now that Microsoft builds its own tablets and phones, the OS giant is positioning itself as a competitor to many of its partner OEMs.
That business model switch is a bigger hurdle Microsoft needs to overcome, more than anything else, in my humble opinion.
That may be true, but perhaps they didn't give those products a chance.
The Surface Pro and the Windows phone appear to be competent products, by all accounts I've read. They need to stick it out. You can't expect a 50 percent market share a year or two after product introduction.
Bert wrote: Now [Microsoft is] getting serious about the hand held gadget market, and by all accounts, making decent products in that field. Including the Surface Pro and Windows phone. But it just got started.
Microsoft is by no means new to the hand-held gadget market. The Zune portable media player was introduced in 2006 and discontinued in 2011. The Kin phone was introduced in 2010 and discontinued within a year. Microsoft has tried to make in-roads in hand-held devices, but has yet to inspire the marketplace.
Companies reinvent themselves all the time, so there's no reason to think Microsoft can't do the same thing.
Apple was always a closed shop, unlike Microsoft, but so what? Apple went almost extinct, until Steve Jobs reinvented it from a very struggling walled garden PC maker to a fashion-trendy gadget company. It did stay "vertically integrated," but that's hardly enough to guarantee success.
Microsoft was just a software house for IBM. Then it became the premier software house for PCs and servers, becoming bigger than the IBM it was serving before. Weir, right? Now it's getting serious about the hand held gadget market, and by all accounts, making decent products in that field. Including the Surface Pro and Windows phone. But it just got started.
It wasn't long ago that the trade press could only gush about iPhones. Now the trade press has come to realize that Android is also a power to contend with, yet even that is a relatively new phenomenon, let's not forget. All Microsoft has to do is stick with it, and trhe marketplace will see another adjustment.
eewiz wrote: [Microsoft] didn't build the first browser yet has the most used browser now.
According to Wikipedia, Google Chrome has higher usage than Explorer. Explorer's share will only decrease as desktop PCs are used less. I'll let others compare Windows usage to Android and iOS, but if they haven't already overtaken Windows I suspect it will happen pretty soon. And if "popular" means that people "like the OS" rather than "are required to use the OS", I suspect that others are far more "popular".
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.