Bytecode, sourcecode, a rose by a different name...

Erh... I don't really know the exact specs of your application now, but so far I can't think of any constellation in which this isn't a security risk waiting to explode.

Well, buy a new car. Planned obsolescence at work!

Care to inform us what car so that others may learn from your mistake and avoid that brand?

*handwave*

You do not need those profiles.

1mbit? You're veeeeeery optimistic.

Hello? How the fuck do you plan to get vendor lock-in down with an open platform?

I wouldn't get my hopes up for that "standardization". If anything, it will ensure that you can't do jack yourself and HAVE TO buy some kind of overpriced solution because ... umm... safety. Yeah, we'll go with that reason. Safety is always a good enough reason when it comes to getting you to spend ten times of what's necessary on your car.

How much of it is under my control and how much of it is under its maker's?

That's the first question you'd have to answer before I even ponder thinking about remotely considering getting maybe a little bit excited.

Needn't be too accurate, any 8 year old on a management chair will easily be identifiable.

Very well, but you do NOT want to know where the milk comes from.

Hey, thanks!

Because most of the time you can somehow shed the blame somehow, or mitigate the cost. It's a risk management game: How much do we save by hiring the cheap idiots, how likely is it that they fuck up and how much would it cost if they do.

If the equation works out, get the duds.

Whatever you call the "too dumb to understand but good enough to learn by heart" degrees that deal with business instead of legal.

Boobies ain't for little kids!