Horseshit.

There are two charges when it comes to narcotics:

Possession
Possession with intent to distribute

The difference between them is basically the seized quantity of the illicit substance. Both are prosecuted. Often.

You want your car to get intoxicated for you?

People under 25 don't have the money to afford all this bullshit - they buy either cheaper new cars, or slightly used cars.

At any rate, saying that Ford is going to go the way of IBM because of the software running the fucking radio is supremely retarded.

It actually does, now. They just reworked the aero and heating so that parts will explode if you expose them to too much air friction. Unless you use stability control or keep your heat shield pointing in the right direction manually, it will tumble and conceivably tear itself apart / burn to a cinder. If you come in too shallow, you will aerobrake and head back out to space in a lower orbit where you may lose power - Kerbals don't eat or drink without an addon, so electrical power is the biggest concern in that scenario.

I think I heard somewhere that it was part of a government launch contract that they needed to own the design so that they could second-source the motors if necessary. By licensing it and having the schematic, they probably checked whatever box that some bureaucrat was looking to check. They probably never intended to actually manufacture the things - just comply with some contractual requirement in the least useful way.

Lots of these use rechargeable NiCad or Li batteries, which would fail well before the PV cells or the LED.

The issue then would be degradation of the systems on the satellite from micrometeor impacts, radiation, heat, etc.

They wouldn't last forever - eventually the solar arrays would stop supplying the minimum voltage needed and it would turn into another orbiting chunk of metal. Or the electronics would burn out from too much radiation damage - shielding doesn't completely eliminate the problem forever, it just delays it really well.

So you're saying that they ripped out all the legacy shit that old IE-only apps (and malware) relied upon, and now they're blowing the trumpets about how secure they are?

I guess I'd be impressed if they got to a reasonable level of security without breaking every legacy app that they convinced people to write against their leaky web APIs.

Write against a vendor locked-in API, get vendor locked-in.

What's funny is that the smart-growth crowd doesn't call this "ravaging" but rather calls it "ingrowth" and "densification". It also "creates livable, walkable neighborhoods."

I guess Amazon just made the mistake of doing this in Seattle rather than Portland where it's called approved growth planning.

I'm a Chef admin, and there's no way we wholesale change out simple one or two liners in Ruby for the exhaustively verbose PowerShell equivalent.

You missed the point.

This isn't about being able to install PowerShell on Linux as some kind of bash replacement. This is about being able to have an agent on Linux that talks to the same "Desired Configuration Management" system you're already using on Windows servers, and have already scripted things in PowerShell.

This isn't for you, because you clearly aren't using Windows server with Microsoft's DCM solution, and you aren't looking to extend that solution to Linux instances. This is the Microsoft version of Chef or Puppet, with a cross-platform client. Using PowerShell.

Extingush Chef and Puppet - the two open and pre-existing ways to do what DCM does.

Now only if there wasn't a free way to do that before...

$_ is a stolen construct from Perl.

That was one of the things in PowerShell that I actually understood right away, from working with Perl for 10 years.