Done; see above

It was ReliableSite.net. I tried to name them earlier but was too subtle. :-)

I was only out a month's worth, fortunately.

You can't fire a faculty member because outside the scope of his duties he expresses an opinion you don't like -- even if it's a clearly crackpot opinion. If you could, Stanford would have kicked Linus Pauling out when he became a Vitamin C crackpot.

The difference, though, is that Pauling was a sincere crackpot -- brilliant people are often susceptible to crackpottery because they're so used to being more right than their neighbors. Dr. Oz is a snake-oil salesman; when he's faced with people who are educated -- not necessarily scientists but critical thinkers -- in a forum he doesn't control, he speaks in a much more equivocal fashion. That shows he knows the language he uses on his show and in his magazine is irresponsible.

So selling snake-oil isn't crackpottery, it's misconduct. But somebody's got to find, chapter and verse, the specific institutional rules of conduct Dr. Oz's misconduct violates. There will have to be due process, particularly if he's a tenured professor, which will probably require lesser disciplinary measures than dismissal be tried first.

uhm, actually plist files are xml

ACTUALLY plist files can be either textual or binary, which is very much not XML

I should have said not necessarily though, instead of just "not"... but it was kind of irrelevant to the main point.

They certainly aren't very compact as far as formats go, even on the watch.

Sigh, didn't read much of that original message, did you?

They don't NEED TO BE EXTREMELY COMPACT because they are sent over only once, when the app is loaded on the watch - that said, it is in the binary format which is much more compact than the textual format.

In use the watch pulls files from that bundle at runtime. And if you were any kind of programmer you'd know there is a tradeoff between compression and computation (which the watch has little of) in terms of file formats, so a fairly but not maximally compact file format is better for performance than whatever you are thinking of.

The UI definition is held in a Plist format (like, but not, XML) but that's not what the device gets. It gets a very compact binary form of your UI, that is loaded onto the watch before the user even opens your application.

The Apple Watch API is actually EXTREMELY conservative with what gets sent over to the watch, to the extent that even attempting to set the same label value twice in a row is rejected with a warning. and UI elements on the screen are wits-only (you cannot query the watch see what currently displayed values are).

You mean like the iPhone...Oh, wait, that was a rushed piece of [bleep] as well.

Especially if you held it "wrong".

who the heck wears a watch nowadays, other than old people...And why would I want to be constantly interrupted by stuff I don't want to do anything about?

So you can more easily press the "F off!" and/or "Get off my lawn!" reply button.

Yeah, and Microsoft...had phones YEARS before Apple did.

But people expect Microsoft to suck.

We use Microsoft because help for all the glitches and work-arounds are relatively easy to find because everybody else uses Microsoft and gijillion people already ran into and documented the issues we encounter. It's the Network Effect applied to volume suckage.

Microsoft just couldn't sell enough phones for the Volume Suckage Network Effect to kick in.

It's a new field. Vendors are going to trip and stumble until the lessons of the street straiten things out. The first PC apps sucked, the first Mac apps sucked, the first Linux apps were...all in EMACS, anyhow, you get the point.

Why wouldn't a randomized subsample from 10M people get funded? The required sample size doesn't grow as the population does.

Absolute true story I'm embarrassed to say:

My 7 year old son: "Pffft, I know how babies are made; I watch all the nature channels".

You don't see people pulling out a crossword puzzle when you are at dinner with them.

I guess you had better dates than I did.

"You've been replaced by your own robots"

I suspect Intel will find a way to keep AMD alive using pricing games to avoid both anti-trust accusations and the appearance that X86 cpu's are a dying biz. Intel and AMD need each other whether they like it or not.

why central Texas has water is because of the creation of a lake system via dams. This would be never, ever done today...

You imply it's Fate's Will and/or a "good thing" that we heavily populate arid land.

I suppose you could argue "we do it because we can", but then don't whine when Blow Back hits.