It's common knowledge here in the San Francisco bay area, that the google maps traffic progress data is largely based on pickups of people's ezpass information along the highway at various points. This allows them to estimate flow by seeing how long it takes for cars to go from given points along the highway, which lets them determine if the highway is operating at reduced speeds.

Many people do not keep their ezpass available. Some do. Generally people seem happy that some tracking occurs to provide the public with a useful service.

Maybe that's the key difference. If NYC was providing realtime data to the public as a result, the public opinion would probably be different.

I believe brain patterns typically alter when the head is separated from the body.

Your milage may vary.

*slightly* bigger datapoint. Work bought around 10 ocz drives for shared build machines. 3 failed within the first 6 months. This was around early 2012.

I wasn't really paying attention to the choices being made around then or would have warned away from that choice. I only found out after I started doing my own research into card-based flash storage that I asked about what we used (the second pass was violin cards) and found out we'd used ocz drives for the first failed experiement.

Sure, you can compile in RAM, (my commercial work project with a ~4GB build tree does this whithout a ramdisk just fine) but linking in ram is right out.

And since in C++ linking is the slowest part by FAR on rotating disks, SSD offers an immense benefit.

If in some other language like pure C or ocaml, then this may be less true.

But then again just building the dependency graph for make wins so hard on SSD, there's still no reason to forgo it. And if you have to build ANYTHING with visual studio, the whole-project link-time optimizations make linking so expensive that you really desperately want the SSD.

Using msdos since 1990, /slash switches are overall less common on msdos and its children than -minus switches were.

Nevermind that / is a poor choice due to its meaning as a directory separator. (Yes, windows supports / as dir separator for the last ten years or more).

But please, parade your lack of familiarity with your platform more.

It's quite likely there were two.

The issue was simple.

In VxWorks, when you create pipes for IPC, you get to choose what kind of semaphore you want, because people want the shortest deadlines possible (at least classically).

JPL selected simple mutexes, which led the priority inversion.

Pipes were, generally speaking, far less well exercised in the codebase at the time, and Wind River engineers explicitly advised the use of message queues which would offer the necessary functionality and would not have had the problem encountered.

There are solutions to these problems. xrpa is one of them.

It doesn't look much like the X protocol, but that's fine.

On any single monitor, more than two applications can be run simultaneously. Instead of Windows 8's fixed split, where one application gets 320 pixels and the other application gets the rest, the division between apps will be variable. It'll also be possible to have multiple windows from a single app so that, for example, two browser windows can be opened side-by-side.

This is sounding a lot like a tiling window manager to me.

That markup also makes the document more comprehensible to users of gui displays.

No, really.

The gui mail client markup is so catastrophically bad that the text mode stuff is much more understandable. People freuqently are impressed by the clarity I produce in mutt using vim as compared to all my outlook-weilding cavemen.

Are you at SUNYA?

Btw, the economy may seem horrible in Upstate New York (because it is) but there are other parts of the country doing a lot better. Don't set your sights too low.

Read the law in question, which was from 2009 and amended in 2012. It's made with modern phones in mind, and it was specifically written to combat texting:

As used in this section “write, send, or read a text-based communication” means using an electronic wireless communications device to manually communicate with any person using a text-based communication, including, but not limited to, communications referred to as a text message, instant message, or electronic mail.

Using GPS is not manually communicating with a person. The law does not apply to reading text on a phone in any context other than communications with another person.

If you can't see that this is DRM, ask yourself:

Is this game fundamentally multiplayer? (If you don't realize it isn't, you certainly haven't played it.)

Once you realize there's actually almost nothing multiplayer about it, ask yourself why you can't just play offline.

At this point, you realize it's DRM.

Yep, it's DRM.

It's DRM that they can plausibly convince dupes that it's not because it theoretically has some utility value.

Don't bee fooled, or be a fool.

You clearly didn't read my post, nor understand the issue.

We didn't choose to do the smart thing, so our needs are irrelevant.

I'm in regular contact with a larger percentage of large enterprise IT shops, probably over 20% of the total base of sizable IT departments, and I speak from the experience of what *they* choose.

Meanwhile, if you need to deal with virtualization management at large scale, vmware is worse in terms of staff efficiency, because you can't do custom automation in a reasonable way.

Your numbers are about optimization for some medium-sized business, and it may well be the right choice there, but that's just barely "enterprise".