Actually, the amount of lead expended by hunters during hunting season is arguably a lot more than old fishing weights and lead figures. But no, give us lead-free solder that grows tin whiskers and makes electronics actually wear out over time... http://en.wikipedia.org/wiki/Tin_whiskers
... The designs are different enough that it isn't easy to just substitute automobile engines for aircraft use. Its been tried, and has worked in some cases, but not many.
Basically aircraft engines turn slowly (usually 2700 rpm max) because the propeller tips need to stay subsonic. Gear boxes are very heavy because of the large moment of inertia of the propellers and haven't worked very well in most installations. The low engine speed means that it needs very large displacement (9 liters is not uncommon) to get the required power. Light weight / high airflow give you air cooled, aluminum-finned engines. The aircraft engines are actually very efficient at their normal operating point. Part of this is due to the high compression allowed by high octane fuel.
I appreciate your content-rich post -- I got a couple of good solid facts out of it I hadn't known before, and that always pleases me.
Question -- has the idea of swept (as in swept-wing) propellor tips caught on? I understand the airfoil configuration of a straight prop is complex enough, but with modern modelling and manufacturing methods I'd think the costs of those props could come down, potentially allowing higher RPM engines. How's that gone?
Up until a couple of years ago VMS was still used in a large Australian national grocery chain to handle the back-end supply chain. They were attempting to replace it while I was there. I think they decided to port it more because they were concerned by end-of-life issues than any shortfall in performance or reliability. OLTP was handled by ACMS, and it just worked. I don't think the production systems went down at any point for the duration of my contract.
There was a reason why it was originally called VAX/VMS -- the operating system and the Vax architecture were developed simultaneously; the hardware supported KESU (Kernel, Executive, Supervisor, User, for those of you who are non-aligned), the x86 chip didn't. I think this is the root of the security problem that WNT suffered when VMS was ported to Microsoft's product. Each mode allowed a subset of the total instruction set, with certain instructions (such as writing to device drivers, for example) denied to outer modes. For this reason, Microsoft hackers could write code where they shouldn't. For this reason, VMS hackers couldn't.
And yes, WNT was just VMS with a UI and a slightly updated memory model. Many unique memory-oriented SYSGEN parameters were duplicated in WNT.
Also, VMS was very much an operating system consisting of handling interrupts; Unix wasn't this way back then (being a more general-architecture OS, in Unix stuff was polled a lot).
I will miss DCL and all those lexical functions I could (and frequently did) recite in my sleep.
And a foreign key is just a copy of a primary key in another table, plus constraints. Learn that one:-)
If you want to give your employer a bit of value in your SQL experiments, show him an Iron Speed demo. Ain't free, but it's cheap, and you can pump out a lot of web-based reports for them quickly (Bosses love reports, and they love quickly). You'll also learn your way around IIS (yes all you out there, Apache rocks, I know, I've heard it, I've supported it. Give the guy a break, ok?) which means you can learn about Exchange's outlook web access at the same time, if they're running Exchange - and most businesses will, for a while longer anyway.
Also, if you're on an intranet (not talking about DMZ here) you definitely want to specify Active Directory security integration, and don't muck with the default collating order unless you really know you want it.
As long as there are penalties for 'losing' key footage. Whether by the officer or higher in the chain of command. Otherwise it becomes a selective evidence tool that is easily biased.
This is a problem which can easily be dealt with in the courts. Footage missing? Cop must be lying.
Back when I was pressing my nose against the glass of The Byte Shop (San Mateo was it? Buggered if I can remember, I lived in Redwood City and it was nearby) wishing I could afford one of those nifty Apple ]['s, I saw an Apple I in the shop, under glass, listed for a cool $1 Mill. It was a board, with components. Not terribly impressive, but the ][ had only been out for a few months iirc. I don't think he ever really wanted to sell it.
I went to work for Apple shortly after, got one of their loan-to-own units with a floppy disk and VisiCalc. Wasn't much, but damme, I was empowered.
Bad idea yes, but being kicked out of school and retorted to police isn't a proportional punishment.
The right answer would be a figurative slap on the wrist for "borrowing" chemicals from the lab, and some detention exercises to calculate the reaction results, and the pressures/temperatures generated in the containment vessel.
Yes, this. Punishment designed to correct, not a reaction based on anger.
Kids like this are not the ones you want to filter out of the system.
You mean we're not supposed to still be doing that?
Anyone who doesn't have a sculpture of pivoting 10base2 connectors, and know how to turn them into a replica USS Enterprise, is insufficiently senior to talk to.
Well, we had to have a look at W8 because we have a few thousand users who buy their own PC's. We have a say in what we can support, though, and that carries a lot of weight.
After our ISD team had a look at it, and after we stopped laughing, our chief decision-maker said: "Well, we skipped Vista..."
Major change fear isn't just a Luddite thing, it's a major cost for us. We're talking $millions if we were to move to W8 in training cost, and that doesn't include the rather expensive productivity dip as we cycle customers through a training program, for which we would have to bear the cost. There is no way we could avoid substantial training, as our users just simply aren't that adept and would completely freeze at a new interface.
You can take that back to your boss at Microsoft, Geekoid, and tell them that W8 sucks because it would cost us too goddamn much money to implement.
Let's see -- was that 99% serfs and 1% czars?
Where have I heard that number before...
Actually, the amount of lead expended by hunters during hunting season is arguably a lot more than old fishing weights and lead figures. But no, give us lead-free solder that grows tin whiskers and makes electronics actually wear out over time... http://en.wikipedia.org/wiki/Tin_whiskers
... The designs are different enough that it isn't easy to just substitute automobile engines for aircraft use. Its been tried, and has worked in some cases, but not many.
Basically aircraft engines turn slowly (usually 2700 rpm max) because the propeller tips need to stay subsonic. Gear boxes are very heavy because of the large moment of inertia of the propellers and haven't worked very well in most installations. The low engine speed means that it needs very large displacement (9 liters is not uncommon) to get the required power. Light weight / high airflow give you air cooled, aluminum-finned engines. The aircraft engines are actually very efficient at their normal operating point. Part of this is due to the high compression allowed by high octane fuel.
I appreciate your content-rich post -- I got a couple of good solid facts out of it I hadn't known before, and that always pleases me.
Question -- has the idea of swept (as in swept-wing) propellor tips caught on? I understand the airfoil configuration of a straight prop is complex enough, but with modern modelling and manufacturing methods I'd think the costs of those props could come down, potentially allowing higher RPM engines. How's that gone?
You say you *want* to remain on a single lump of rock?
HAHAHAHA!!!!
(translated from the Glertish)
Up until a couple of years ago VMS was still used in a large Australian national grocery chain to handle the back-end supply chain. They were attempting to replace it while I was there. I think they decided to port it more because they were concerned by end-of-life issues than any shortfall in performance or reliability. OLTP was handled by ACMS, and it just worked. I don't think the production systems went down at any point for the duration of my contract.
There was a reason why it was originally called VAX/VMS -- the operating system and the Vax architecture were developed simultaneously; the hardware supported KESU (Kernel, Executive, Supervisor, User, for those of you who are non-aligned), the x86 chip didn't. I think this is the root of the security problem that WNT suffered when VMS was ported to Microsoft's product. Each mode allowed a subset of the total instruction set, with certain instructions (such as writing to device drivers, for example) denied to outer modes. For this reason, Microsoft hackers could write code where they shouldn't. For this reason, VMS hackers couldn't.
And yes, WNT was just VMS with a UI and a slightly updated memory model. Many unique memory-oriented SYSGEN parameters were duplicated in WNT.
Also, VMS was very much an operating system consisting of handling interrupts; Unix wasn't this way back then (being a more general-architecture OS, in Unix stuff was polled a lot).
I will miss DCL and all those lexical functions I could (and frequently did) recite in my sleep.
The courts do not permit "fishing expeditions".
I would suggest following this issue through Groklaw. If there are legal alarms being raised, they're likely to be covered there.
And a foreign key is just a copy of a primary key in another table, plus constraints. Learn that one :-)
If you want to give your employer a bit of value in your SQL experiments, show him an Iron Speed demo. Ain't free, but it's cheap, and you can pump out a lot of web-based reports for them quickly (Bosses love reports, and they love quickly). You'll also learn your way around IIS (yes all you out there, Apache rocks, I know, I've heard it, I've supported it. Give the guy a break, ok?) which means you can learn about Exchange's outlook web access at the same time, if they're running Exchange - and most businesses will, for a while longer anyway.
Also, if you're on an intranet (not talking about DMZ here) you definitely want to specify Active Directory security integration, and don't muck with the default collating order unless you really know you want it.
And don't use auto-shrink. At all.
I've found SQL Server Central to be useful sometimes http://www.sqlservercentral.com/ -- go there and start reading.
i.e. The guy with the gold makes the rules.
"These walls are solid Krell metal" said Dr. Morbeus. He waved his hand over the electrode and the walls slammed quickly into place.
-- Forbidden Planet
You're joking, right? We export that crap so we don't have to drink it.
Want a good Australian beer, try something from Malt Shovel, Cascade or Mountain Goat.
"I've got half a mind to close my eyes and let this string go..."
-- Loggins & Messina, "Sailing the Wind"
From the recent series, I'd think the actor playing The Doctor would need to be young enough to run. As in ... RUN!
As long as there are penalties for 'losing' key footage. Whether by the officer or higher in the chain of command. Otherwise it becomes a selective evidence tool that is easily biased.
This is a problem which can easily be dealt with in the courts. Footage missing? Cop must be lying.
Destruction of evidence is a crime, too.
My guess would be that they're including a bit of major civil infrastructure change in the cost of the car.
... If they create, say, a fighter with the performance of the F-35, then it's a real problem.
I'd think that the ability to find weak points and develop countermeasures would be more pertinent than the ability to copy the design.
Back when I was pressing my nose against the glass of The Byte Shop (San Mateo was it? Buggered if I can remember, I lived in Redwood City and it was nearby) wishing I could afford one of those nifty Apple ]['s, I saw an Apple I in the shop, under glass, listed for a cool $1 Mill. It was a board, with components. Not terribly impressive, but the ][ had only been out for a few months iirc. I don't think he ever really wanted to sell it.
I went to work for Apple shortly after, got one of their loan-to-own units with a floppy disk and VisiCalc. Wasn't much, but damme, I was empowered.
Bad idea yes, but being kicked out of school and retorted to police isn't a proportional punishment.
The right answer would be a figurative slap on the wrist for "borrowing" chemicals from the lab, and some detention exercises to calculate the reaction results, and the pressures/temperatures generated in the containment vessel.
Yes, this. Punishment designed to correct, not a reaction based on anger.
Kids like this are not the ones you want to filter out of the system.
You mean we're not supposed to still be doing that?
Anyone who doesn't have a sculpture of pivoting 10base2 connectors, and know how to turn them into a replica USS Enterprise, is insufficiently senior to talk to.
Entangled Object Oriented language? Certainly you'd need parameter overloading.
I think that's a pretty Ploor effort.
By that time, we should have the ability to move the planet back to a more favourable orbit, if we so desire.
Or, perhaps, combine it with our farming planets into a Klemperer Rosette, and flee.
Sintered ceramic teeth -- dentures and bridges, faster and more accessible dentistry.
I think Mr. Markram is one lab accident away from a supervillain.
Well, we had to have a look at W8 because we have a few thousand users who buy their own PC's. We have a say in what we can support, though, and that carries a lot of weight.
After our ISD team had a look at it, and after we stopped laughing, our chief decision-maker said: "Well, we skipped Vista..."
Major change fear isn't just a Luddite thing, it's a major cost for us. We're talking $millions if we were to move to W8 in training cost, and that doesn't include the rather expensive productivity dip as we cycle customers through a training program, for which we would have to bear the cost. There is no way we could avoid substantial training, as our users just simply aren't that adept and would completely freeze at a new interface.
You can take that back to your boss at Microsoft, Geekoid, and tell them that W8 sucks because it would cost us too goddamn much money to implement.