No idea why this was marked insightful. The OS has nothing to do with tethering, it's the carrier. The iPhone OS has officially supported tethering since 3.0, it's just that AT&T hasn't allowed it because they're afraid it will bring their fragile network to its knees.
If you use an Android phone to tether with AT&T or Verizon with an "unlimited" data plan, you are breaking their rules and stand to be charged extra for using the tethering feature.
This post reeks of bull shit. I've been using OSX for 10 years straight (since developer preview 3) as my primary and I have NEVER had to manually edit a plist file because "some part of OSX was failing". If you forget your password, just boot to the damn CD and reset it. What's so hard about that?
The dock connector on the bottom of every iPhone / iPad / iPod is USB2 - along with other things like power, video, audio, etc.
The problem though, is the host / client nature of USB. When the iPad is connected to your computer for syncing, its the client. When you connect your camera to it to download pictures, its the host. The question is, is that connector simply a pin-out change, or is there actually circuitry in it that allows the iPad to act as a host?
If I "found" an iPhone pre-production phone, I would sure as hell try and sell it for as much $$ as I possibly could to the highest bidder. I'm sure it's worth a decent chunk of change, just think of how many hits this "exclusive" story must have generated for Gizmodo.
Their manure is used as fertilizer to grow food (either for the cows or for us). Sure, it may be supplemented with chemical fertilizer, but no farmer throws away manure. It's like black gold.
Human error led them to believe that they were armed. They mistook a DSLR with a big zoom lens and a shoulder strap for an AK-47.
I'm not excusing their actions, but you can't just say that they fired on a crowd of unarmed people. I don't have enough back story or context to draw valid criticism with.
There are plenty of UI design concerns as well. Currently there is no standard UI for dealing with apps running in the background. The phone gives you a green bar across the top of the screen. The iPod gives you a special alert with buttons when you double click the home button and a play icon in the top right of the screen. The calendar doesn't have any UI at all, it just alerts you with a message. The Mail app displays a numeric badge and plays a sound (a feature available to all 3rd party apps using the notification API).
It will be interesting to see how they unify the UI for running multiple apps at once without compromising the usability of the device.
My guess is that everything will basically look and function the same, except the App's icon will have a glow or a badge indicating that it is running in the background. Each app will have to explicitly be granted permission to be able to run in the background by the user (same way each app has to be allowed to send notifications now).
I would be more interested in seeing the wiring diagram. My guess is that there is no redundancy in the throttle position system and it's not closed loop. There should be 4 throttle position switches, 2 in the gas pedal and 2 on the throttle body. The ECU should do a consistency check between the 2 signals coming from the pedal and a check between the 2 signals coming from the throttle body. If it detects two different signals coming from the pedal, or two different signals coming from the throttle body, it should go into limp mode.
This is how all VAG (Volkswagen Audi Group) cars are designed.
From what I have read, the Toyotas work on the honor system. The ECU trusts the signal coming from the pedal with no way of knowing if the signal was generated by a short circuit, interference, etc.
Not to mention that any developer (including would be flash game developers) can release a free app via the app store. This argument that flash apps would cut into Apple's app store revenue makes absolutely 0 sense.
Disallowing the use of private APIs ensures that your software will continue to function with new versions of the iPhone OS. The private APIs might change, but the public ones will not.
The real questions is whether or not there should be a public API for CoreSurface.
Well, I've owned over 20 VWs so I think I know what I'm talking about. But if you don't want to take my word for it, I suggest you simply go try it. Get going 60mph and stomp the throttle and brake pedal simultaneously. Let us know what happens.
Slashdot Mirror
But that photo is from the past...
I would never trade OSX's column browser view for the Classic Finder's spatial view. I find it to be MUCH more efficient.
But if you test it with a multimeter, you will find that there is already continuity between the two antenna halves...
No idea why this was marked insightful. The OS has nothing to do with tethering, it's the carrier. The iPhone OS has officially supported tethering since 3.0, it's just that AT&T hasn't allowed it because they're afraid it will bring their fragile network to its knees.
If you use an Android phone to tether with AT&T or Verizon with an "unlimited" data plan, you are breaking their rules and stand to be charged extra for using the tethering feature.
This post reeks of bull shit. I've been using OSX for 10 years straight (since developer preview 3) as my primary and I have NEVER had to manually edit a plist file because "some part of OSX was failing". If you forget your password, just boot to the damn CD and reset it. What's so hard about that?
The dock connector on the bottom of every iPhone / iPad / iPod is USB2 - along with other things like power, video, audio, etc. The problem though, is the host / client nature of USB. When the iPad is connected to your computer for syncing, its the client. When you connect your camera to it to download pictures, its the host. The question is, is that connector simply a pin-out change, or is there actually circuitry in it that allows the iPad to act as a host?
Or is it just stripping the FLV container off of the H.264 video stream embedded inside?
Yes, they have Flash - and it f'ing sucks to be perfectly honest.
Exhibit A
If I "found" an iPhone pre-production phone, I would sure as hell try and sell it for as much $$ as I possibly could to the highest bidder. I'm sure it's worth a decent chunk of change, just think of how many hits this "exclusive" story must have generated for Gizmodo.
Their manure is used as fertilizer to grow food (either for the cows or for us). Sure, it may be supplemented with chemical fertilizer, but no farmer throws away manure. It's like black gold.
I hope you didn't bet money on that...
Human error led them to believe that they were armed. They mistook a DSLR with a big zoom lens and a shoulder strap for an AK-47.
I'm not excusing their actions, but you can't just say that they fired on a crowd of unarmed people. I don't have enough back story or context to draw valid criticism with.
I think you missed peragrin's point.
Why can't they just support the codecs installed on the system?
There are plenty of UI design concerns as well. Currently there is no standard UI for dealing with apps running in the background. The phone gives you a green bar across the top of the screen. The iPod gives you a special alert with buttons when you double click the home button and a play icon in the top right of the screen. The calendar doesn't have any UI at all, it just alerts you with a message. The Mail app displays a numeric badge and plays a sound (a feature available to all 3rd party apps using the notification API).
It will be interesting to see how they unify the UI for running multiple apps at once without compromising the usability of the device.
My guess is that everything will basically look and function the same, except the App's icon will have a glow or a badge indicating that it is running in the background. Each app will have to explicitly be granted permission to be able to run in the background by the user (same way each app has to be allowed to send notifications now).
Higher efficiency and lower emissions
A modern VW 2.0T makes 2x as much power with 1/2 the emissions while achieving the same MPG as a 2.0 NA motor from a 90's
I would be more interested in seeing the wiring diagram. My guess is that there is no redundancy in the throttle position system and it's not closed loop. There should be 4 throttle position switches, 2 in the gas pedal and 2 on the throttle body. The ECU should do a consistency check between the 2 signals coming from the pedal and a check between the 2 signals coming from the throttle body. If it detects two different signals coming from the pedal, or two different signals coming from the throttle body, it should go into limp mode.
This is how all VAG (Volkswagen Audi Group) cars are designed.
From what I have read, the Toyotas work on the honor system. The ECU trusts the signal coming from the pedal with no way of knowing if the signal was generated by a short circuit, interference, etc.
Not to mention that any developer (including would be flash game developers) can release a free app via the app store. This argument that flash apps would cut into Apple's app store revenue makes absolutely 0 sense.
Same situation where I'm from. The entire town has time warner cable except for our street, which has about 20 houses on it. Total BS.
Disallowing the use of private APIs ensures that your software will continue to function with new versions of the iPhone OS. The private APIs might change, but the public ones will not. The real questions is whether or not there should be a public API for CoreSurface.
Except that in this case X.264 is technically superior to the open alternatives, unlike PNG vs GIF.
Until the patent submarine surfaces, then it's really going to suck!
Well, I've owned over 20 VWs so I think I know what I'm talking about. But if you don't want to take my word for it, I suggest you simply go try it. Get going 60mph and stomp the throttle and brake pedal simultaneously. Let us know what happens.
Here's some proof backing up my claim.
It is prettying simple actually - just take a reading from the vehicle speed sensor. If you're going less than 10mph, no automatic throttle cut.
This is something VW figured out 10 years ago.