There was a Windows 97 as well (service pack + enhancements really), but it set the example of MS using year numbers to indicate versions.

That fell apart with Windows ME and XP, but not Win2k. (I had uniformed people swear to me that they were on Win2K because they were running WinME)

And back in 1999, who would have thought that Microsoft would return to major release numbers instead of using the year? If they stuck with the year nomenclature it wouldn't have been a problem for another 90 years.

No.... this really comes down to not knowing, and not using, the API provided to you by the OS for handling version detection. Relying on string (or worse, numeric) comparison to do your detection is a recipe for disaster. This is exactly why all modern Javascript libraries do feature detection instead of relying on User-Agent strings.

Unfortunately it hasn't stopped AT&T from throttling the speeds of their grandfathered unlimited plans. If you go over 2GB of data in a month, they throttle you to Edge speeds.

How does that argument work? It's entirely possible to have things installed and enabled which are going unused. Whether or not something is intentionally being used has no bearing on whether it is a security risk.

You can do this pretty easily, and I'm sure Tesla has done the math already for you (assuming you take them at their word).

1) Take lifetime costs for your typical car in a similar price range (so you can assume parts and service costs are equitable).
2) Check Tesla's fluid replacement schedule - much longer intervals, and much fewer fluids to replace. Only user-serviceable fluid is the windshield washer. Everything else is effectively sealed like a VW transmission.
3) Subtract anything involving drivetrain maintenance or rebuilds.
4) Subtract anything involving replaceable parts (hoses, belts, sparkplugs, filters, etc) as the Tesla has extremely few equiavlent parts
5) Subtract anything involving engine maintenance or rebuild.
6) Subtract anything involving exhaust maintenance. Don't forget smog checks!
7) Subtract out traditional battery replacements - you'll be accounting for it below in the battery swap - no double counting!
8) Keep tires and brakes the same, as that doesn't change.
10) You can leave in the alternator. In fact, double it, because you have regenerative braking system to account for.
11) Add a battery swap if you think it's needed - but be fair, and make sure your gasoline-equivalent lifetime goes as far as the lifetime of the Tesla *after* the battery is swapped. eg - if the swap is at 100K miles, make sure to set the lifetime of both cars to 200K miles to cover the full useful life of 1 battery swap. Don't forget to include any "core" credits for recycling that massive battery back.

I had a 14 hour flight to Hong Kong with those. Even with free entertainment and meals on a brand new plane, it was the worst flight of my life.

That slump-to-recline is literally unusable for tall passengers.

Developers are already using the tag today with javascript libraries to backport to noncompliant browsers. As browsers adopt the standard, the transition will be seamless.

https://github.com/scottjehl/p...

The tag gives a standard way of doing it, and javascript is used already for backporting the functionality to noncompliant browsers.

Fantastic.

Except I have never seen a web client that handles JPG this way. Not a single one will stop at target resolution, and will continue to load until they have all the bytes of the image. Furthermore, there's plenty of reasons to download the full image size. Perhaps the image needs to resize dynamically after being loaded. Perhaps I rotated my device from portrait to landscape and now I need a larger image to fill the space. There's no pause/resume mechanism in the format to handle this, and the resulting interpolation during a resize effect would look horrendous. Oh, and btw, depending on the image contents, progressive format JPG can actually result in larger file sizes than non-progressive. Lastly, with responsive design, the contents of the image may actually need to be different for different resolutions. For example, embedded text or iconography may not be legible at smaller sizes.

Now solve for GIF and PNG.

<picturefill /> is at least a format-agnostic approach that doesn't require extra implementation on the server side, addresses all the above concerns, and can be implemented on browsers that don't currently support it using a little bit of javascript.

That doesn't require a union to fix. Get off your ass and leave. As plenty of other people have pointed out, there are tons of non-union shops that respect their employees and don't pull that crap.

Optical is already used in those scenarios for line-of-sight networking. How does engineering a wind tunnel around a laser improve the effectiveness in any of those scenarios?

By contrast to get even the same small warhead to geostationary, with guidance and course course correction ability, will require a rocket very similar to that used to put geostats into orbit in the first place.

I think you just backed up my claim. Reread what I wrote. If you can get a satellite to a specific point, you can get a weapon there as well.

By payload I am referring to the use type, not the mass. Assuming equivalent mass, it doesn't matter if you're throwing up a few kilograms of circuitry or a a few kilograms of rock.

If you can put a satellite there, you can put a weapon there as well. Payload has little to do with the capability to get there.

Yeah, I have KeePassX 2.0 as well. The UI is kinda flakey (hence why it's been in Alpha status for several years now)

I love KeePass, but the community needs some help...

There's a myriad of client apps for it, but the 1.7 vs 2.X database formats fragments the market.

2.X requires Mono if you want to run it on Linux or OSX.

I wish they had a central dev team with first-class OSX, Windows, and Linux versions like VLC or Transmission.

Uh, no.

A warrant means that law enforcement has the legal standing to search and seize evidence in your control (forcibly if need be).

A subpoena means that you, the targeted party, are required by law to provide the evidence demanded.

Jurisdictional boundaries aren't the difference. A warrant can be issued internationally. The key difference is authorizing a government-operated search versus a legal demand that you provide evidence. The entities involved and their roles is the key distinction.