stevesi

There are bulleted lists in the posts. You can just read the bold words :-)

Definitely ignore me :-) While I get what you're saying, the timing isn't quite like that. Two things: 1. The 68030 ran Apple System 6 and as a result Macs were slow and not "modern". 2. The Mac IIx came out at the end of 1988, which was the tail end of the 386 line. The 486 PCs arrived in mid 1989 in volume (so months later). The 486 quickly following with Windows 3, were significantly faster than Mac for all the things that were measured like Word, Excel, compiling, etc.

The 68030 was an elegant chip, but the OS for it did not arrive until 1991.

The spirit of the post is about integrated hardware and software. Sorry if I was not perfectly clear in this line. But by all means do not take anything I said seriously :-)

reply

Thank you and Hello ... the posts are all written, except for the artifacts/captions. I usually post on sundays and then one other day during the week based on the testing I've been doing for the first 20 or so posts. It depends on holidays and other events--I recognize this isn't a time sensitive topics and don't want to interfere with big events.

There's no prior restraint--no one is reviewing this and there are no constraints on what I am writing

(all of this as per the Author note and introduction)

Your water heater is a legacy device because it is horribly inefficient and lacks any connection to how you actually use water (when you need it, how much, etc.) It just constantly consumes energy keeping massive amounts of water ready for you even if you are away for two weeks (as one example). Same with sprinklers that have no knowledge of soil water. Or an ice maker. Or... that's what makes them "legacy".

If you've followed CES over the years (maybe you have) then you know the incredible pains consumers have gone through with physical button remotes--trying to make IR work, trying to figure out what grids of tiny buttons do (with shift keys no less), trying to customize physical button remotes to control multiple devices and more.

If you've tried to put in a security camera or other monitor you might have noticed how unsightly the wires can be when you put them where you want to see. Or how impossible it is to put one at an outside door where there are no outlets. Of course having mains is compelling but this is another trend that we experience in mobile that turns out to be pretty convenient for many uses.

You might think an ethernet cable is one cable to rule them all, but the jack is very large and almost no homes have those jacks on more than one wall of any room (if that). And many systems (in particular lighting) were controlled using ethernet cable from each outlet. But those were all based on proprietary home runs and routed to the electrical panel not data location and so you ended up with a "one cable to rule them all" legacy wiring that was quite costly.

Just a few thoughts.

This issue is known, intermittent and dependent on a number of factors. It has been addressed and an update is forthcoming.

This type of issue would be identical across NVIDIA based ARM PCs and large numbers of the reference platforms were available at the same time they have been available to external developers.

Developers on the Office team (and Word team) that needed to contribute to the ARM focused work had access to the tools and hardware needed, including Surface specific hardware. There was no shortage of knowledge, hardware, or communication.