These planets are at the stable lagrange points, not in orbit with each other.
Which, by the way, is perfectly fine with regards to the IAU's definition. These planets have cleared their orbit nicely, and are gravitationally bound to each other.
The article describes the brake override system as "immediately cutting engine power if the brakes are applied". I certainly hope they are wrong.
There are several situations where brake and throttle need to be applied at the same time. The one I have to do irregularly is to dry out the brake system after traveling through water - Drive slowly while applying brake force until the disks dry out. My Astra has fly-by-wire throttle, and it cuts accelerator input after a few seconds of brake application. This does not cause any problems.
The other one I can think of,namely, left-foot braking, really shouldn't be necessary on the road.
Lastly, i vastly prefer fly-by-wire to an old style throttle cable. They regularly stick when seals crack, dust gets in and lubricants dry. Fly-by-wire is much more reliable, and far more flexable.
As it is an external stent, around the outside of the arota, not inside it like a endovascular stent, I wouldn't think that thrombosis would be an issue.
In related news, Firefox's spell-check doesn't know much about things medical.
From reading the theengineer.co.uk article, it seems that it is a precisely created wrapping around the outside of the bulging aorta, supporting it. The 'breakthrough' is using medical imaging and 3D printing to make a model of his aorta, so the wrapping can be made accurately before the operation. Previous attempts where the aorta had to be measured and the support created during the operation had been tried unsuccessfully.
I just thought that everybody used these services (WebJet in australia) to research flights and prices, and then went to the airline's own sites to book? You might on a rare occasion find the flight you chose booked out in the few seconds it took you to switch sites, but, if that happened, you'd just go back and choose a second flight.
It seems like, in this case, living in that street seemed like just cause. And the results, both in the arrests, prosecutions, and tangible benefits to the law-abiding citizenry (ie, you), seem to justify that.
The mess they left of your flat was inexcusable, but they probably were well out of patience by the time they arrived at your door.
I agree with the point about "magic-just-ignore-this code". But that comes from teaching non-OO programming in an OO language.
My point is the OO is as much - maybe more - of a basic concept as iteration and branching. A programmers first 'hello world' should be taught as giving a string object to the system object.
Teaching OO as a basic concept leads more quickly into displays and graphics, even simple games rendered in 3d.
Of course, choosing your language is critical. Many OO languages have a history of being procedural with OO extensions. You end up programming that way, especially if your history is the same: Learning procedural programming, and adding OO to it.
There is noting inherently complex with OO, unless you already have a head full of linear or procedural programming that you need to get rid of.
A nice, stripped-down OO language - I'd sugest parts of java if it was a free language - would be a good start. Even a graphical interface, although they are undeniable useless for real programming, would be useful for starting off.
The only reason we don't have permanent nuclear waste repositories is every time they identify another perfect site, it get NIMBYd to death by local (where local = < 5000 km) uninformed 'interest groups'.
As for the 'very long term' thing: we only have to be really worried is the time it takes for the highly radioactive isotopes to decay. People seem to forget that you can have 'highly radioactive' short-half-life, short lived radioactive substances, or you can have long lived, long-half-life, low grade radioactive substances. You cannot have long-half-life highly-radioactive substances - the two are mutually exclusive.
Also consider pdfs with complex page layouts. Deciphering the text flow from them is often hard for eyeballs, let alone computers. 2 columns is enough to throw out many screen readers.
Not necessarily. PDF does not preserve text flow. It breaks up paragraphs into lines (or less if kerning has been altered), and places them accurately on the page. If you have a multi-column layout, then a pdf-to-text algorithm (first step in screen reading) is likely to put column-2-line-1 between column-1-lines-{1 and 2}. Best of luck sorting that out.
And the rest of us say "Get rid of it". We do not access government documents to be blown away by their totally rad page style. We access them for information, and extracting the information from the glumph that encases it is sometimes hard for the best of us.
html all the way. Any formatting you cannot fit in a simple stylsheet can get left out.
And the evidence shows that they are. However, for some searches, they show an informative entry at the top, which includes information, like stock quotes, and links to various sources of more info. The only 'issue' is that their services are more prominent than other's services in that informative entry. After that are the unbiased search results.
Personally, I'd like them to add a little bias to the searches. I'd like to spend less time staring at yet another experts-exchange page, and have anyone caught spamming forums to be struck from Google entirely.
Re:Karma Whoring Post
on
2010 Geek IQ Test
·
· Score: 4, Informative
No, lsof. It lists open file handles, and any nework port that is open is also a file handle. With some grep and sed hackery, you'll have a simple list.
Reminds me of something I saw on.. oh, one of the classic crime dramas. The actor also narrated Danger Mouse. An episode finished with a quote by a consultant-type, which was a lot of waffle, but boiled down to: [system] is failing. [new system] is created to fix the problem. [New system] is based on [system]. [New system] also fails.
Yes, that is one way it is being explained. It helps sailing types get the concept. But it is not quite accurate. After all, you could achieve the same thing, if you could make it efficient enough, using a flat paddle-wheel-type arrangement instead of a screw.
You'll have to publish and/or patent your design. I cannot see any way to build such a craft without some form of turbine. No, just thought of it. A design using vertical blades that are moved backwards on a chain, and folding up for the return trip. But then the grandparents argument would still hold true: the vertical blades would have to have a negative wind speed.
You have a tail-wind. That tail wind pushes the craft forward. Not very well, mind you, as you do not have a large sail area. This turns the wheels. The turning wheels are then used to turn the prop, which pushes the craft forward *relative to the wind*. Do it efficiently enough, and you will be able to travel faster than the wind. In their case, 2.8 times faster. They are harvesting the difference between the crafts higher landspeed and its lower windspeed. Those who have a trouble with the concept probably also have trouble with the plane-on-a-treadmill conundrum. Which we will not discuss here!
This is what I first thought. But you are thinking of speeds gained in cross-wind situations, where sail-powered crafts easily travel faster than the wind speed.
This is faster than wind-speed in downwind situations, "spinnaker legs", in other words. Took me a few minutes to get my head around the physics, but the concept is simple once you have the idea. The grandparent is a very good, if a little long-winded (oh groan) explanation.
Well, anyone who wants that can program an IDE to do it: Show the NE symbol whenever it finds "!=" in the text, and save "!=" when it was displaying the NE symbol. Those who like pretty symbols (and I admit that they are nice) can have them, and those who want to type in != >= get their wish too. And if you don't want to change anything you do, you don't have to.
Everything that he stated in that article really sounds like 'more fancy IDE', to me. You want to break out a function to a side box, and colour it pink-on-blue-with-chartreuse-surround? Make your IDE do that for you. Put formatting codes in specially created comments if you have to.
So this means that you cannot touch-type in Japanese?
(clarification: touch-typing here not just meaning not looking at the keys as you type, but not looking at the output either. If you have to check the screen to see that it has entered the right 'kanji', then surely transcription is slow.)
I'm sure the hacks to enter [whatever the correct word to describe these 'symbolic' alphabets is] languages are very well resolved. It is just a pitty that they have to exist. But I have no idea what the perfect Japanese-entry device would be. Maybe a 'chord' keyboard, where two keys are pressed simultaneously - but the learning curve!
Slashdot Mirror
These planets are at the stable lagrange points, not in orbit with each other.
Which, by the way, is perfectly fine with regards to the IAU's definition. These planets have cleared their orbit nicely, and are gravitationally bound to each other.
The article describes the brake override system as "immediately cutting engine power if the brakes are applied". I certainly hope they are wrong.
There are several situations where brake and throttle need to be applied at the same time. The one I have to do irregularly is to dry out the brake system after traveling through water - Drive slowly while applying brake force until the disks dry out. My Astra has fly-by-wire throttle, and it cuts accelerator input after a few seconds of brake application. This does not cause any problems.
The other one I can think of ,namely, left-foot braking, really shouldn't be necessary on the road.
Lastly, i vastly prefer fly-by-wire to an old style throttle cable. They regularly stick when seals crack, dust gets in and lubricants dry. Fly-by-wire is much more reliable, and far more flexable.
As it is an external stent, around the outside of the arota, not inside it like a endovascular stent, I wouldn't think that thrombosis would be an issue.
In related news, Firefox's spell-check doesn't know much about things medical.
From reading the theengineer.co.uk article, it seems that it is a precisely created wrapping around the outside of the bulging aorta, supporting it. The 'breakthrough' is using medical imaging and 3D printing to make a model of his aorta, so the wrapping can be made accurately before the operation. Previous attempts where the aorta had to be measured and the support created during the operation had been tried unsuccessfully.
I just thought that everybody used these services (WebJet in australia) to research flights and prices, and then went to the airline's own sites to book? You might on a rare occasion find the flight you chose booked out in the few seconds it took you to switch sites, but, if that happened, you'd just go back and choose a second flight.
It seems like, in this case, living in that street seemed like just cause. And the results, both in the arrests, prosecutions, and tangible benefits to the law-abiding citizenry (ie, you), seem to justify that.
The mess they left of your flat was inexcusable, but they probably were well out of patience by the time they arrived at your door.
I agree with the point about "magic-just-ignore-this code". But that comes from teaching non-OO programming in an OO language.
My point is the OO is as much - maybe more - of a basic concept as iteration and branching. A programmers first 'hello world' should be taught as giving a string object to the system object.
Teaching OO as a basic concept leads more quickly into displays and graphics, even simple games rendered in 3d.
Of course, choosing your language is critical. Many OO languages have a history of being procedural with OO extensions. You end up programming that way, especially if your history is the same: Learning procedural programming, and adding OO to it.
loop while( true )
screen.print( "Hello World" );
There is noting inherently complex with OO, unless you already have a head full of linear or procedural programming that you need to get rid of.
A nice, stripped-down OO language - I'd sugest parts of java if it was a free language - would be a good start. Even a graphical interface, although they are undeniable useless for real programming, would be useful for starting off.
The only reason we don't have permanent nuclear waste repositories is every time they identify another perfect site, it get NIMBYd to death by local (where local = < 5000 km) uninformed 'interest groups'.
As for the 'very long term' thing: we only have to be really worried is the time it takes for the highly radioactive isotopes to decay. People seem to forget that you can have 'highly radioactive' short-half-life, short lived radioactive substances, or you can have long lived, long-half-life, low grade radioactive substances. You cannot have long-half-life highly-radioactive substances - the two are mutually exclusive.
Also consider pdfs with complex page layouts. Deciphering the text flow from them is often hard for eyeballs, let alone computers.
2 columns is enough to throw out many screen readers.
Not necessarily. PDF does not preserve text flow. It breaks up paragraphs into lines (or less if kerning has been altered), and places them accurately on the page. If you have a multi-column layout, then a pdf-to-text algorithm (first step in screen reading) is likely to put column-2-line-1 between column-1-lines-{1 and 2}. Best of luck sorting that out.
And the rest of us say "Get rid of it". We do not access government documents to be blown away by their totally rad page style. We access them for information, and extracting the information from the glumph that encases it is sometimes hard for the best of us.
html all the way. Any formatting you cannot fit in a simple stylsheet can get left out.
And the evidence shows that they are. However, for some searches, they show an informative entry at the top, which includes information, like stock quotes, and links to various sources of more info. The only 'issue' is that their services are more prominent than other's services in that informative entry.
After that are the unbiased search results.
Personally, I'd like them to add a little bias to the searches. I'd like to spend less time staring at yet another experts-exchange page, and have anyone caught spamming forums to be struck from Google entirely.
No, lsof. It lists open file handles, and any nework port that is open is also a file handle. With some grep and sed hackery, you'll have a simple list.
Reminds me of something I saw on .. oh, one of the classic crime dramas. The actor also narrated Danger Mouse. An episode finished with a quote by a consultant-type, which was a lot of waffle, but boiled down to:
[system] is failing. [new system] is created to fix the problem. [New system] is based on [system]. [New system] also fails.
It's a pattern that you see repeated constantly.
Yes, that is one way it is being explained. It helps sailing types get the concept. But it is not quite accurate. After all, you could achieve the same thing, if you could make it efficient enough, using a flat paddle-wheel-type arrangement instead of a screw.
Read the other explanations. Watch the you-tube explanations. Even see my ascii-art above.
The item is moving. Energy is harvested from that movement to push the craft forward.
----> Wind speed - 10
<-- Net air speed (ground speed - wind) 5
<- )
Propeller |-A
force 5 ( H
@ air speed H
O------------O < drag on wheel, 5, at ground speed.
------> Ground speed - 15
if input Ek 5*15 = output 5*5 - losses, vehicle will continue to travel.
You'll have to publish and/or patent your design. I cannot see any way to build such a craft without some form of turbine.
No, just thought of it. A design using vertical blades that are moved backwards on a chain, and folding up for the return trip. But then the grandparents argument would still hold true: the vertical blades would have to have a negative wind speed.
No. It works exactly as described.
You have a tail-wind. That tail wind pushes the craft forward. Not very well, mind you, as you do not have a large sail area. This turns the wheels. The turning wheels are then used to turn the prop, which pushes the craft forward *relative to the wind*.
Do it efficiently enough, and you will be able to travel faster than the wind. In their case, 2.8 times faster. They are harvesting the difference between the crafts higher landspeed and its lower windspeed.
Those who have a trouble with the concept probably also have trouble with the plane-on-a-treadmill conundrum. Which we will not discuss here!
This is what I first thought. But you are thinking of speeds gained in cross-wind situations, where sail-powered crafts easily travel faster than the wind speed.
This is faster than wind-speed in downwind situations, "spinnaker legs", in other words. Took me a few minutes to get my head around the physics, but the concept is simple once you have the idea. The grandparent is a very good, if a little long-winded (oh groan) explanation.
Well, anyone who wants that can program an IDE to do it: Show the NE symbol whenever it finds "!=" in the text, and save "!=" when it was displaying the NE symbol. Those who like pretty symbols (and I admit that they are nice) can have them, and those who want to type in != >= get their wish too. And if you don't want to change anything you do, you don't have to.
Yeah, this.
Everything that he stated in that article really sounds like 'more fancy IDE', to me. You want to break out a function to a side box, and colour it pink-on-blue-with-chartreuse-surround? Make your IDE do that for you. Put formatting codes in specially created comments if you have to.
All this has very little to do with the language.
So this means that you cannot touch-type in Japanese?
(clarification: touch-typing here not just meaning not looking at the keys as you type, but not looking at the output either. If you have to check the screen to see that it has entered the right 'kanji', then surely transcription is slow.)
I'm sure the hacks to enter [whatever the correct word to describe these 'symbolic' alphabets is] languages are very well resolved. It is just a pitty that they have to exist. But I have no idea what the perfect Japanese-entry device would be. Maybe a 'chord' keyboard, where two keys are pressed simultaneously - but the learning curve!