The sound triangulated was in cryogenic liquid oxygen at 50 PSI. The speed of sound in that is approximately 1 kilometer per second.This paper is about calculating the exact speed. Elon talked in the conference about reading telemetry with millisecond accuracy. But this would yield only 1 meter resolution.

Sometimes companies intentionally order small numbers for their initial run of a product. If it doesn't sell well

In other words, companies set initial production based on estimates of purchases, with some buffer... since Apple had months of backlog in production, the expected sales far exceeded even the buffer of safety they had devised.

That's not the way it works. When cross-compiling, configure runs on the host. It tests that things compile. It doesn't test that they run.

Like I said, if you forget to charge it overnight.

And like *I* said in the post you responded to, if you do forget you charge it while in the shower and that's enough to last the day easily.

Right, a fitness tracker is designed to always be with you, a camera is not. That's the difference.

But since all they do is track fitness they are inherently a niche market. There are many, many people who don't want to wear something that ONLY tracks fitness.

What's it's "killer app"?

You are someone who cannot see the forest for the trees. The killer app is metaphorically the forest.

Or think of it this way - what is the "killer app
  for the Computer? The Smartphone? It differs for every person. It is the culmination of what they can do that is the killer app, the assembly of a thousand joins to make a robust structure.

Roger,

This is great. It does look like a 1:1 mapping to what we expect autoconf to do, except neater and maintainable.

The only problem with selling this to GNU folks is that it would make CMake a prerequisite to everything. But I think it's worth it. And then there's inertia. And the language isn't as pretty as we'd like.

Can you see any other possible objections?

Thanks

Bruce

The biggest issue it has is battery life.

From real-life experience, that's not been an issue at all. You just charge it at night when you go to sleep, or if you forget while you take a shower, and that is enough.

It has other issues, but battery life simply is not one of them.

Sure for fitness tracking it's good but there are better fitness trackers out there

Just like there are better cameras than an iPhone, but the iPhone takes more photos than any of them because the REAL better camera/fitness tracker is the one you have with you. I never, ever would have bought a fitness tracker, I didn't even want that from the Apple Watch at all, but I actually use that feature all the time because it's so well done - and it is there.

Whereas the Apple Watch is just more of a gimmick

I totally agree the Apple Watch is not a game-changer. I don't think everyone will want or need one.

However, there's no way it's a gimmick. It is quite useful already, and with just a bit of understanding of what apps can do with WatchOS 2, you can see a lot of third party power being brought to bear on how useful the device is - but even without them core features are compelling enough that there will be a substantial number of people who enjoy using the watch.

Customer satisfaction numbers for Apple Watch owners are even higher than the iPhone, higher still among non-technical users - THAT is a huge clue to anyone willing to think about the implications. A product with satisfaction numbers that high is not a gimmick, and will have staying power in the market because people will keep using them, and furthermore tell friends they enjoy using it.

it should do just fine for non-photo/video use.

It doesn't because it's really hard to read indoors. The display was by far the biggest disappointment to me about the Time. The color limitation did not really bother me at all, I don't think the watch is a great place to look at photos anyway and that's a reasonable limitation for the battery life you get in return. What I guess they really needed was a much stronger backlight, even if that would have cut the battery life in half.

Also the actual backlight illumination is kind of flaky to turn on, you can set it to on by default all the time but that is way too much (though I would do that if it helped much).

Don't know if that's the display technology or just an availability/price issue

I'm sure it's a price issue because no-one else is using color e-ink that I know of, so probably even that small increase in size would have been a pretty large increase in cost.

Whether it is a failure or not depends upon Apple's expectations for the device.

Since it was on backorder for months that obviously means sales beat internal expectations by a large margin, or they would have manufactured more to start with.

Why should Pebble have to spend the CPU cycles, RAM, and battery life on that?

Because it makes a device they are trying to sell substantially more useful.

They have no control over what Apple does or does not do security wise - you can debate until the universe dies about the wisdom of user apps being able to arbitrarily intercept notifications, but that doesn't change the fact that Apple DOES NOT allow that, nor will they probably any time soon (they may sometime, just as once they did not allow third party keyboards and now they do).

Given the reality of what is, Pebble can opt to make the device a fully featured competitor, or basically cede the market to Apple for smart watches. If it were my business, I know what I would do - because I make things work when they can instead of bitching about how hard something is.

P.S. It's not even that hard, a simple string lookup against a hash table, so it;'s not like it's a world-ending problem on a device with 7x the battery life to start with...

Cmake are scons require that they already be installed.

This is assuming that a shell capable of running ./configure is available on all of your platforms.

I should correct that: automake builds things by creating makefiles. The configure script created by autoconf is concerned with configuration rather than building, but its output is input to automake.

CMake, Scons, etc. are mainly targeted at dependency-based building of programs. Autotools doesn't really build anything. It goes through a long list of system facilities, determining if each is present. For many, perhaps most of them, it builds a little C program that exercises the facility, and sees if it compiles.

Now, there's another poster who says you really can do this with CMake, which I'll have to look at.

I've used my Apple Watch many times until 2-3am... please do some research before you complain about problems real people do not have, or you look like an idiot.

P.S. don't worry about the tag, I've done that before so I totally understand. :-)