The hard part is going to be making the brakes survive spinning at 10,000rpm, not dissipating the energy from slowing down.
Finally someone who gets it:) But that's not even the hard part. The hard part is making a much larger diameter wheel that will survive this. The brake disc is, comparably speaking, peanuts.
"There are 100 ways I can think of for stopping a car without having brake disks."
You miss the forest for the trees. The article is just mumbo-jumbo. The wheel itself is a much larger diameter metal structure, subject to much larger stresses. Since the wheel isn't a problem, seemingly, then the friction disc brake isn't either. Remember that the disc brake doesn't have to operate at 1000mph, and doesn't have to endure the high centrifugal forces while being hot. Operation at 160mph is peanuts. Why did they goof and go with carbon discs I don't know, but the brakes aren't an issue at all. If the wheel survives, a similarly constructed brake disc will, too. The entire reason for having a separate braking disc and not using the wheel itself is the wear. The wheel has much larger diameter than the brake disc, so any braking wear on its circumference would require wheel rebalancing. That's an expensive, time consuming operation, since the wheel has to be balanced better than a hard drive spindle is balanced.
Of course if you actually looked at what you propose you'd realize that any inductive system still needs to use bulky rotors. It's the rotor's survivability that is the problem. The fact that it's a friction brake is rather inconsequential here. It's not the braking that is the problem. It's mere survivability of a disc brake at rotational speeds of an enterprise hard drive.
They do, although they are not really called cars anymore. The problem isn't 160MPH nor 6 tonnes. The problem is that the brakes have to survive "storage" (not braking) at 10kRPM, since the car will be going ~1000mph at some point. Everyone is focusing at the low speed or relatively forgettable weight. Those are not the problems, even my "little" Volvo XC90, when loaded, weighs about 2.5 tonnes, and I'm sure its brakes would survive slowing it down from 160MPH with a 3 ton brakeless trailer attached to it. Meh. But I don't really know if the front brake discs would survive being spun up to 10kRPM.
It's much easier than it was in the year 2000, as far as I can tell. There are quite a few products at the local dollar store that are, in fact, made in the U.S.A. Same goes for home improvement stores - I've started to find U.S.-made tools.
Assuming that you have an internet connection and a networked printer at those locations, something like eFax would make much more sense. Or just set up your own Asterisk at some central location, use a T-38 VOIP provider, and send the print jobs to printers "out there".
It's not like an RHEL system will magically stop working because the licensing is messed up. Updates from RHEL servers will be unavailable for the time being and that's it.
Heck, I don't even know who would need solder paste without actually using a laser-cut stencil and, you know, actually printing the paste like it was meant to be - in quantity? What's the point? You don't even need or want a fine-tipped soldering iron. For reflowing anything with leads, you in fact want a nice 3mm-5mm wide, short tip with good thermal conductivity. You don't need solder paste, you do need a flux pen.
"people get sick as a consequence of bad behaviour" Ah, circular reasoning FTW. In absence of STDs and Christian morality having bareback sex is not bad behavior anymore, you know.
So, there is your answer. The oscillators used here are not stable, and there must be a good reason for it. One possibility: those pingers are tuned electromechanical transducers. If anything, the electronic oscillator uses the transducer itself as the resonant circuit. Why? Because a perfect quartz-driven signal feeding a detuned transducer will not produce much in the way of hydrophonic output. It will be at the perfect frequency, but too faint to detect at any reasonable distance.
In the USA in CCD all the bees just disappear from the hives.
That sounds to me more like a skunk feeding on them at night than CCD:) Yes, seriously, damn skunks can wipe out an entire hive in a couple of nights. The bees are too silly to resist the skunk's scratching on the bottom of the hive, it seems. They just walk out on the surface of the hive, since they don't fly at night, and the skunk just eats them. I've seen it happen, and it's both sad and silly-looking.
lots of people won't take a job where they wear a sealed up thick hot suit in the blazing sun all day
This problem has been solved, lemme think, about the time we were doing our first EVAs in LEO. Just because the beekeeping industry is more than half a century behind the times doesn't mean the problem hasn't been solved many times over.
A modern industrial robot on a moving base with a modern industrial vision system should handle that very efficiently. Possibly more efficiently than the bees themselves.
IIRC, such an implosion is not unlike an explosive device going off -- it sends shock waves that shatter things, send shrapnel out, etc. It's likely that the tether that was close to the imploding vehicle was got cut up as well.
IOW: There's no reason for it not to be 100% legit, except it's not a meteorite, it's a random rock from the place where the chute was previously packed. Possibly even not most recently packed.
Yeah, they're writing technical reports on shit that someone has packed into a chute. Oh, how easy it is for experts in field A to assume they have been born with knowledge from field B. Namely, those meteor experts who just don't get what every skydiver learns after a while: shit sometimes get packed into the chute. This whole thing is just so full of fail I don't know whether to laugh or cry.
it fails to address how the rock got to the speed of several hundred km per hour by the time it flew past him
You can address it yourself. Gravitational acceleration is 9m/s^2. 300 km/h is 83m/s. The rock could have easily been going less than that, say 50m/s. It takes 6 seconds for it to accelerate to that speed from rest. It didn't start at rest.
He was professional long enough. It didn't work. Kay doesn't seem to care enough if you're nice to him. As a leader, you have to use what works. Demonstrably, being nice to Kay was leading to nowhere. Granted, being not nice to Kay may not work either, but it's definitely worth trying. It's also worth it to let everyone else know that this kind of shit attitude (like Kay's) is not going to be taken lightly.
He was trying discipline for the longest time with Kay. Eventually, he had no option but resorting to invectives. Sometimes you have to scream at your kid. Same here.
Yea, but if you mess up and do something he declares "STUPID", it's off to the public stocks for you in a flurry of expletives. IMHO Stuff like that just lacks class and reflects badly on him.
On the contrary, I think this doesn't reflect badly on him. Kay has been pushing it for ages, and there was nothing else to be done. It's in everyone's best interest that the public is warned a) not to try such tricks, b) to stay away from Kay until he improves his behavior. Remember, Linux kernel is developed in the open. Public scorn is to be expected. You don't like it, maintain your own fork, that's what git is for, you know.
Slashdot Mirror
The hard part is going to be making the brakes survive spinning at 10,000rpm, not dissipating the energy from slowing down.
Finally someone who gets it :) But that's not even the hard part. The hard part is making a much larger diameter wheel that will survive this. The brake disc is, comparably speaking, peanuts.
"There are 100 ways I can think of for stopping a car without having brake disks."
You miss the forest for the trees. The article is just mumbo-jumbo. The wheel itself is a much larger diameter metal structure, subject to much larger stresses. Since the wheel isn't a problem, seemingly, then the friction disc brake isn't either. Remember that the disc brake doesn't have to operate at 1000mph, and doesn't have to endure the high centrifugal forces while being hot. Operation at 160mph is peanuts. Why did they goof and go with carbon discs I don't know, but the brakes aren't an issue at all. If the wheel survives, a similarly constructed brake disc will, too. The entire reason for having a separate braking disc and not using the wheel itself is the wear. The wheel has much larger diameter than the brake disc, so any braking wear on its circumference would require wheel rebalancing. That's an expensive, time consuming operation, since the wheel has to be balanced better than a hard drive spindle is balanced.
Of course if you actually looked at what you propose you'd realize that any inductive system still needs to use bulky rotors. It's the rotor's survivability that is the problem. The fact that it's a friction brake is rather inconsequential here. It's not the braking that is the problem. It's mere survivability of a disc brake at rotational speeds of an enterprise hard drive.
They do, although they are not really called cars anymore. The problem isn't 160MPH nor 6 tonnes. The problem is that the brakes have to survive "storage" (not braking) at 10kRPM, since the car will be going ~1000mph at some point. Everyone is focusing at the low speed or relatively forgettable weight. Those are not the problems, even my "little" Volvo XC90, when loaded, weighs about 2.5 tonnes, and I'm sure its brakes would survive slowing it down from 160MPH with a 3 ton brakeless trailer attached to it. Meh. But I don't really know if the front brake discs would survive being spun up to 10kRPM.
A Piston console with a bit of external storage is probably all one needs. It'd be physically very, very small.
It's much easier than it was in the year 2000, as far as I can tell. There are quite a few products at the local dollar store that are, in fact, made in the U.S.A. Same goes for home improvement stores - I've started to find U.S.-made tools.
Assuming that you have an internet connection and a networked printer at those locations, something like eFax would make much more sense. Or just set up your own Asterisk at some central location, use a T-38 VOIP provider, and send the print jobs to printers "out there".
It's not like an RHEL system will magically stop working because the licensing is messed up. Updates from RHEL servers will be unavailable for the time being and that's it.
Heck, I don't even know who would need solder paste without actually using a laser-cut stencil and, you know, actually printing the paste like it was meant to be - in quantity? What's the point? You don't even need or want a fine-tipped soldering iron. For reflowing anything with leads, you in fact want a nice 3mm-5mm wide, short tip with good thermal conductivity. You don't need solder paste, you do need a flux pen .
Huh? Pi can do great precision timing, you just have to run it as a bare-metal system.
"people get sick as a consequence of bad behaviour" Ah, circular reasoning FTW. In absence of STDs and Christian morality having bareback sex is not bad behavior anymore, you know.
So, there is your answer. The oscillators used here are not stable, and there must be a good reason for it. One possibility: those pingers are tuned electromechanical transducers. If anything, the electronic oscillator uses the transducer itself as the resonant circuit. Why? Because a perfect quartz-driven signal feeding a detuned transducer will not produce much in the way of hydrophonic output. It will be at the perfect frequency, but too faint to detect at any reasonable distance.
at makes it even worse if the main mode of failure is buckling
This!
In the USA in CCD all the bees just disappear from the hives.
That sounds to me more like a skunk feeding on them at night than CCD :) Yes, seriously, damn skunks can wipe out an entire hive in a couple of nights. The bees are too silly to resist the skunk's scratching on the bottom of the hive, it seems. They just walk out on the surface of the hive, since they don't fly at night, and the skunk just eats them. I've seen it happen, and it's both sad and silly-looking.
lots of people won't take a job where they wear a sealed up thick hot suit in the blazing sun all day
This problem has been solved, lemme think, about the time we were doing our first EVAs in LEO. Just because the beekeeping industry is more than half a century behind the times doesn't mean the problem hasn't been solved many times over.
A modern industrial robot on a moving base with a modern industrial vision system should handle that very efficiently. Possibly more efficiently than the bees themselves.
IIRC, such an implosion is not unlike an explosive device going off -- it sends shock waves that shatter things, send shrapnel out, etc. It's likely that the tether that was close to the imploding vehicle was got cut up as well.
I personally find Linus's post to be reserved. I'd have probably written "U fucking mad?" :)
IOW: There's no reason for it not to be 100% legit, except it's not a meteorite, it's a random rock from the place where the chute was previously packed. Possibly even not most recently packed.
Yeah, they're writing technical reports on shit that someone has packed into a chute. Oh, how easy it is for experts in field A to assume they have been born with knowledge from field B. Namely, those meteor experts who just don't get what every skydiver learns after a while: shit sometimes get packed into the chute. This whole thing is just so full of fail I don't know whether to laugh or cry.
it fails to address how the rock got to the speed of several hundred km per hour by the time it flew past him
You can address it yourself. Gravitational acceleration is 9m/s^2. 300 km/h is 83m/s. The rock could have easily been going less than that, say 50m/s. It takes 6 seconds for it to accelerate to that speed from rest. It didn't start at rest.
He was professional long enough. It didn't work. Kay doesn't seem to care enough if you're nice to him. As a leader, you have to use what works. Demonstrably, being nice to Kay was leading to nowhere. Granted, being not nice to Kay may not work either, but it's definitely worth trying. It's also worth it to let everyone else know that this kind of shit attitude (like Kay's) is not going to be taken lightly.
The ongoing issue is Kay. I expect everyfuckingone to have an issue with him!
He was trying discipline for the longest time with Kay. Eventually, he had no option but resorting to invectives. Sometimes you have to scream at your kid. Same here.
Yea, but if you mess up and do something he declares "STUPID", it's off to the public stocks for you in a flurry of expletives. IMHO Stuff like that just lacks class and reflects badly on him.
On the contrary, I think this doesn't reflect badly on him. Kay has been pushing it for ages, and there was nothing else to be done. It's in everyone's best interest that the public is warned a) not to try such tricks, b) to stay away from Kay until he improves his behavior. Remember, Linux kernel is developed in the open. Public scorn is to be expected. You don't like it, maintain your own fork, that's what git is for, you know.