Any decent language has full PCRE support these days. Perls days as regular expression king are in the past. Sure it may have set the standard for how it's done, but now it's no longer a selling point. Plenty of other nicerlanguages exist.
You'd definatly need a pressure suit. As for reentry....I'm not sure. It'd depend on the speed, which I don't know offhand. Probably not too horrible, since unlike the Space Shuttle most of the velocity is vertical, unlike the Space Shuttle which a huge horizontal factor.
Because to fly it unmanned you need either A: Advanced computerized flight systems or B: A reliable remote control setup. Either A or B is far more likely to cause problems than it's worth.
Well, actually it would depend on the exact altitude and speed. Up above 100,000ft, there is so little air that the actual windblast would be fairly low, no worse than a conventional skydive. Being supersonic would make things interesting of course, but there's no reason that I can see why it wouldn't work. The biggest problem I would see is getting the parachute to deploy cleanly. Should be okay at 150k ft or below (round numbers), as there is still enough atmosphere for aerodynamic devices to function.
Well, let's work it out. Assuming an ion Drive can produce a net thrust of 0.01g (.0931 m/s). LEO is around 7600m/s. That gives 81362 seconds, or 22 hours. Obviously they're planning on much lower accelerations than even that, but low forces build up over time.
The username of an email address is only up to the first plus sign, but the whole thing goes through. So you can send mail, to say, tyler+amazonDOTcom@foo.com, and it goes to tyler@foo.com, but the headers are preserved so you still maintain the tracking/filterable aspect.
It's not IE that holds back W3C standards. It's that the standards are positively byzantine, and so complicated to implement that it's simply not worth the effort.
Answer: Not that much. The load is positioned on or near the aircraft's center of gravity. Thus the plane becomes lighter, and may gain a bit of altitude, but it's not suddenly going to become tailheavy or anything.
The problem with your (fatally flawed) example is that the resource producer loses money because there was a marginal cost to produce the food eaten. That isn't true with downloading.
That's 2.5GB a day. Not much at all. Sounds like it at first, but it isn't. That's roughly 100MB per hour, 1.5MB per minute, 0.25MB / 250Kb / 2Mbit a second. Most cable connections could support that.
Slashdot Mirror
Any decent language has full PCRE support these days. Perls days as regular expression king are in the past. Sure it may have set the standard for how it's done, but now it's no longer a selling point. Plenty of other nicer languages exist.
Last time I looked at the Google Zietgiest, it showed OS X at 3%, and Linux at 1%
So, wait, you're running a year old kernel with known exploits on your entire server farm?
The problem is line of sight. This thing is only 12 miles up. Doesn't take too long for the curve of the earth to wipe that away
Huge difference.
Was? He is still alive as far as I know, and he was still flying as recentl as a few years ago (and I have no reason to suspect that he has stopped)
Uh, yea it is. 10.3 switched. (Thank goodness...) (But zsh is still better than both)
You'd definatly need a pressure suit. As for reentry....I'm not sure. It'd depend on the speed, which I don't know offhand. Probably not too horrible, since unlike the Space Shuttle most of the velocity is vertical, unlike the Space Shuttle which a huge horizontal factor.
Because to fly it unmanned you need either A: Advanced computerized flight systems or B: A reliable remote control setup. Either A or B is far more likely to cause problems than it's worth.
Well, actually it would depend on the exact altitude and speed. Up above 100,000ft, there is so little air that the actual windblast would be fairly low, no worse than a conventional skydive. Being supersonic would make things interesting of course, but there's no reason that I can see why it wouldn't work. The biggest problem I would see is getting the parachute to deploy cleanly. Should be okay at 150k ft or below (round numbers), as there is still enough atmosphere for aerodynamic devices to function.
The Dead *NEVER* allowed bootlegging. They allowed *NON-COMMERCIAL* recording/trading. That's a huge difference.
Notice the word 'net' acceleration. Meaning AFTER all losses due to mass, drag, etc.
Well, let's work it out. Assuming an ion Drive can produce a net thrust of 0.01g (.0931 m/s). LEO is around 7600m/s. That gives 81362 seconds, or 22 hours. Obviously they're planning on much lower accelerations than even that, but low forces build up over time.
Ever considered that just having a 'gres' doesn't make it French?
Ingres rhymes with In-gress
PostgreSQL is post-gres-que-el
Not a good reason.
The username of an email address is only up to the first plus sign, but the whole thing goes through. So you can send mail, to say, tyler+amazonDOTcom@foo.com, and it goes to tyler@foo.com, but the headers are preserved so you still maintain the tracking/filterable aspect.
It's not IE that holds back W3C standards. It's that the standards are positively byzantine, and so complicated to implement that it's simply not worth the effort.
Answer: Not that much. The load is positioned on or near the aircraft's center of gravity. Thus the plane becomes lighter, and may gain a bit of altitude, but it's not suddenly going to become tailheavy or anything.
Memory? A 320x240x16bit screen is 153,600 bytes per frame. At 30fps, that's 4.39MB per second.
You can probably pick up a used iBook for under $500. I can't imagine wanting to read large volumes of text on any PDA.
The problem with your (fatally flawed) example is that the resource producer loses money because there was a marginal cost to produce the food eaten. That isn't true with downloading.
Nitpick: Jenna Yeager (Voyager) is NO relation to Chuck.
You'd be surprised how quickly programming/sysadmin time can factor out differences in hardware cost.
It'd help if I did my math right....
1.5MB/min = 25kb/sec = 200Knit sec. That's barely above ISDN.
5000x a day is nothing.
Let's assume the file is 500k.
That's 2.5GB a day. Not much at all. Sounds like it at first, but it isn't. That's roughly 100MB per hour, 1.5MB per minute, 0.25MB / 250Kb / 2Mbit a second. Most cable connections could support that.
I agree, but here's what I want:
EASE OF PROGRAMMING.
All the existing toolkits have APIs that are daunting to say the least.