Which is one reason Flightgear has never really made a major impact. Or, for that matter, Linux gaming in general.
What, because you were the last person in the world too stingy to go out and buy a mouse with a middle button, and couldn't figure out how to enable ChordMiddle?
Stubby helical aerials on radios work pretty badly, and they just plain don't work at all when you've got a stubby on a handheld that's clipped to your belt.
I wonder how poor performance will be when the aerial is pressed up against a big wet conductive thing?
You use a sliding average over, say 10-30 seconds, to get a reasonable estimate of current average speed, and then estimate based on that.
Have you noticed how when the network goes away, the "Estimated Transfer Time" starts to decay towards *really really long*, taking about 30 seconds to level off at "never"?
Exactly - Photoshop is an unusable piece of crap *simply because of this stupid single-window thing*. I already have a perfectly good window manager. Let *it* manage the damn windows, and stop trying to run another half-assed excuse for a window manager *inside a damn window*, of all the retarded places to do it.
That's fine if you're using a hands-free kit. If you're trying to hold the phone with one hand and drive with the other, you are a danger to yourself and other road users because you don't have proper control of your vehicle. If you're trying to dial a number or look up a contact list, you're not looking at the road.
You'd be amazed how many accidents are caused by people just not paying attention to the road. Fiddling about with phones doesn't help this.
A car is no harder to repair than a bike. For both, you need the right tools.
Really you should be driving an old car, mid-80s or earlier - certainly made before they were required to have catastrophic converters in the exhaust. They're much cleaner and easier to fix than modern cars.
I tend to log GPS data for uploading to OpenStreetMap so I stick very closely to the speed limits, and slow down when I'm negotiating complex twisty side streets so I get better resolution.
But it's the same with a bad GUI. You've got an angry fruit salad of little symbols to click on with no real idea of what they do or why you'd want them.
Bad software is bad software, whether it's GUI or CLI. It's a hell of a lot easier to write a bad, confusing GUI app, though.
Not really, because then you have to wrap your head around the Byzantine complexity of the GUI. It's pretty much always easier to specify what you want, rather than having to click on squiggles and sigils that all look alike, and try and guess what they mean.
Get an FM broadcast radio with an external aerial socket, and a Yagi antenna such as you would use for fringe area reception. Aim it more or less towards the radiant of the meteor shower, and up at about a 30-40 degree angle. Now tune to a station well out of range, in roughly the direction you're pointing.
When a meteor burns up in the atmosphere it will leave a trail of ionised particles, which will reflect radio waves. This is called "meteor scatter", and will show up as little "pings" of signal from the distant station that pop up out of the noise for a few seconds.
Listen carefully, and make a note of the times of the pings so you can plot how frequently they occur. Congratulations, you're doing science.
In means in about a ~100 years, a human won't have the freedom to drive their car -- they will delegate the safety of driving and managing traffic density to an automated vehicle. You will put in their destination and dedicated roads that will ONLY accept computer-controlled cars will minimize the time needed to travel to your destination.
That sounds great, can't happen soon enough. I really enjoy driving, so as soon as the bulk of the ovine plodders are bimbling along automated guided motorways in only a little more of a trance than they are now, the better.
Then we enthusiasts can have the back roads to ourselves.
Slashdot Mirror
Which is one reason Flightgear has never really made a major impact. Or, for that matter, Linux gaming in general.
What, because you were the last person in the world too stingy to go out and buy a mouse with a middle button, and couldn't figure out how to enable ChordMiddle?
Stubby helical aerials on radios work pretty badly, and they just plain don't work at all when you've got a stubby on a handheld that's clipped to your belt.
I wonder how poor performance will be when the aerial is pressed up against a big wet conductive thing?
I wonder when we will start hearing about CmdrTaco-Sex.xxx.
I'd pay good money to never see that.
Is it not something like 120mph winds, though? Why are they causing this much disruption?
Here in Scotland we call that January...
You use a sliding average over, say 10-30 seconds, to get a reasonable estimate of current average speed, and then estimate based on that.
Have you noticed how when the network goes away, the "Estimated Transfer Time" starts to decay towards *really really long*, taking about 30 seconds to level off at "never"?
Yeah. I thought you might have.
Exactly - Photoshop is an unusable piece of crap *simply because of this stupid single-window thing*. I already have a perfectly good window manager. Let *it* manage the damn windows, and stop trying to run another half-assed excuse for a window manager *inside a damn window*, of all the retarded places to do it.
Maybe, maybe not. It's not something I actually set out to do, though, and I can't really understand why you'd want to.
I don't, I've never used Windows so I'm not really aware of what Windows users do.
I've used various different Linux desktops, but never felt the need to change the "skin".
Why would it? Does anyone actually use "custom skins"?
50 "lbs" is about 25kg. Quite why that should be considered such a problem, I don't know.
And if it's the U.S. Navy, you're probably going to need a *lot* of firepower on your little oil rig
... assuming they can persuade the UK to pay for the diesel, *again*.
That's fine if you're using a hands-free kit. If you're trying to hold the phone with one hand and drive with the other, you are a danger to yourself and other road users because you don't have proper control of your vehicle. If you're trying to dial a number or look up a contact list, you're not looking at the road.
You'd be amazed how many accidents are caused by people just not paying attention to the road. Fiddling about with phones doesn't help this.
I don't know about where you are, but in the UK the driver in an emergency vehicle isn't allowed to fiddle with the MDT while driving.
A car is no harder to repair than a bike. For both, you need the right tools.
Really you should be driving an old car, mid-80s or earlier - certainly made before they were required to have catastrophic converters in the exhaust. They're much cleaner and easier to fix than modern cars.
I tend to log GPS data for uploading to OpenStreetMap so I stick very closely to the speed limits, and slow down when I'm negotiating complex twisty side streets so I get better resolution.
No, quite the reverse. If you've got lots of sources it's quite easy to find them simply because you've got a better chance of finding one.
But it's the same with a bad GUI. You've got an angry fruit salad of little symbols to click on with no real idea of what they do or why you'd want them.
Bad software is bad software, whether it's GUI or CLI. It's a hell of a lot easier to write a bad, confusing GUI app, though.
But the signal is more-or-less continuous, so you are trying to locate the source of a very powerful continuous buzz.
This is trivial to DF.
Not really, because then you have to wrap your head around the Byzantine complexity of the GUI. It's pretty much always easier to specify what you want, rather than having to click on squiggles and sigils that all look alike, and try and guess what they mean.
Actually, a command-line interface would be *better*, because then it would be easy to write your own GUI launcher, or call it from XBMC or whatever.
Think in terms of a little shell script that just meant you could run a ROM as if it was a normal app.
Yes, of course.
delicious cake
Get an FM broadcast radio with an external aerial socket, and a Yagi antenna such as you would use for fringe area reception. Aim it more or less towards the radiant of the meteor shower, and up at about a 30-40 degree angle. Now tune to a station well out of range, in roughly the direction you're pointing.
When a meteor burns up in the atmosphere it will leave a trail of ionised particles, which will reflect radio waves. This is called "meteor scatter", and will show up as little "pings" of signal from the distant station that pop up out of the noise for a few seconds.
Listen carefully, and make a note of the times of the pings so you can plot how frequently they occur. Congratulations, you're doing science.
... years ago:
http://lalists.stanford.edu/lad/2008/01/0446.html
For some reason I got accused of being silly about the issue of selling media containing GPLed software...
In means in about a ~100 years, a human won't have the freedom to drive their car -- they will delegate the safety of driving and managing traffic density to an automated vehicle. You will put in their destination and dedicated roads that will ONLY accept computer-controlled cars will minimize the time needed to travel to your destination.
That sounds great, can't happen soon enough. I really enjoy driving, so as soon as the bulk of the ovine plodders are bimbling along automated guided motorways in only a little more of a trance than they are now, the better.
Then we enthusiasts can have the back roads to ourselves.
... and configure your devices to work in the 13cm "high speed data" segment.