Larger headphones like what? Impedance should matter there, not size, and it would surprise me to learn that there are high-Ω headphones that an iPhone can drive effectively, but the adapter can't.
A sysadmin I work who has had Apple-everything for years (iMac, MacBook Pro, MacBook Air, iPhone, Apple Watch...) with walked in last week without his Apple Watch.
Asking him about it, he pulled out a new Pixel and said it was for op's very reason. In particular he noted that the pixel had a much better DAC than any one iPhone he'd ever had - and in particular that it could drive all of his higher end headphones. He also mentioned that the new iThing adapter has it own DAC inside the adapter... it's apparently powered by the lightning port with its own drivers - and that he had tried it out anyway but found it incapable of properly driving any of his nicer headphones.
Destroying those components would render the machine useless without external inputs and outputs, maybe their intention was simply just to disable the machine, executed in a rather odd manner.
We apologize for the significant inconvenience caused by our developer website downtime. We've been working around the clock to overhaul our developer systems, update our server software, and rebuild our entire database. While we complete the work to bring our systems back online, we want to share the latest with you.
We plan to roll out our updated systems, starting with Certificates, Identifiers & Profiles, Apple Developer Forums, Bug Reporter, pre-release developer libraries, and videos first. Next, we will restore software downloads, so that the latest betas of iOS 7, Xcode 5, and OS X Mavericks will once again be available to program members. We'll then bring the remaining systems online. To keep you up to date on our progress, we've created a status page to display the availability of our systems.
If your program membership is set to expire during this period, it will be extended and your app will remain on the App Store. If you have any other concerns about your account, please contact us.
As of now right now (~1374712460) there are two systems that are online: iTunes Connect and Bug Reporter. And both seem to use the cannot-be-killed* WebObjects. You can clearly see that in the URLs as they mention "WebObjects" and end in ".woa" (assuming it means Web Objects Application).
*I've no idea what WebObjects are but I've heard people poke fun at their mention. Would be interesting if someone had more details to share.
Side Note: If you are looking to install Command Line Tools and seem to be unable to install Xcode from the App Store. You can go to Xcode > Preference and install it. Screen shot from a couple of minutes ago: http://i.imgur.com/KEhjkE3.png
WebObjects is kind of like Rails, but 20 years earlier. (Seriously, it's actually very similar to Rails, in it's bones. I don't know if dhh had seen WebObjects, or they just both had seen some smalltalk mvc framework)
They inherited it from NeXT, and it seriously was really ahead of it's time originally. Hell, it was a technically competent and competitive web framework through, oh, 2002 or 2004, maybe even a few years after that. (Can you tell I used to develop for it?)
But it ended up not being a market Apple wanted to be in, selling a web development framework, and it didn't get much attention, it withered on the vine. (Even if it had... 20 years of legacy is not good for a web framework, it would probably still suck by now -- and who wants a proprietary rather than open source web framework, if they can avoid it?). But they kept using it internally anyway long after they stopped marketting it or selling it externally.
Anyhow, it's really hilarious if the legacy WebObjects part of Apple's web infrastructure are actually the parts that are still up. Hilarious in a pleasant way for those of us who used to use and love WebObjects back in the day.
I was brought in as a contractor in the last few months, so I didn't get much of an overview, but I wrote template code (each page, and each component of a page, had three associated files: .wos for 'scripting', .html for templating, and .wod for 'declarations' to tie the other two together).
It was streets ahead of anything I'd previously used (mainly PHP code with intermingled HTML), and led me to build my next major project using XSLT to provide some insulation between the logic and presentation.
That _could_ be a prime example of security by obscurity. Who would spend time looking for a WebObjects exploit if you can spend that time looking for a Rails exploit?
WebObjects is a web application framework. It's OLD old. It's about ten years older than Ruby on Rails, putting it on par with PHP and Ruby itself. NeXT made it and Apple decided to make it free. It was Objective-C and is now Java.
I used WO in the late nineties and it was way ahead of its time. Enterprise Objects (which morphed into Core Data) was an amazing tool for working with databases. Today it's pretty obsolete and it's not easy to find people.
It's not any older than Interface Builder and other stuff in the Mac OS dev toolkit, as all of that came from NeXT. I would guess though that it has not been maintained or updated.
I don't know about you, but I can't convert epoch time in my head and I don't know anyone who can. What's benefit is there to posting epoch time instead of in ISO 8601 format?
Yeah, I noticed the WebObjects apps were back quick and first. With all of the iOS 7 bugs filed and the App Store in active use, I'm not at all surprised that they are too big to die for the time being. As for the rest of it, my money is on some Ruby descendant, based solely on the fact that all of the Passbook sample code was Ruby based, with a Sinatra app being the server and a signing gem bundled. I think some of Mavericks server utilities are Ruby based, too.
Isn't the developer portal written in Java too, probably with a mix of frameworks for different components (it certainly had a heterogenous feel on the front end)? I seem to remember some of the signon urls had .woa in them, and one of the former Struts developers mentioned a vulnerability which sounds like a likely candidate:
The article states that the website is back up but as of now 24/07 11:08GMT that is not the case.
This is terrible timing for me since I came back from travelling on Thursday and haven't been able to get on with working in iOS 7. I really wish Apple were able to provide us with more information on time-scales.
Especially terrible timing for me. I hadn't gotten around to updating my phone off the original iOS 7 beta. Guess what expired yesterday? The original iOS 7 beta. My phone is essentially a brick now until I can update to a non-expired version of iOS.
I noticed today that the resolution center also isn't working right. I can receive/view messages but get an error when I try to send them. Unsure if it's linked to the dev center being down but I would guess it is.
Remember not everyone can afford the latest beast of a machine that can accommodate 16GB RAM, some people still have laptops that can hold a maximum of 4GB by design limitation; it's more likely to be those people worrying about Chrome's RAM usage.
I suspect the power penalty of RAM is made up for by the fact that you don't have to hit the hard disk to get that data back (firing up the HDD will suck a lot of juice). It also appears the needs are pretty much tied to the chip, so a 4GB and 8GB module use about the same amount of power.
Before, I would never consider moving to Android after having used the iPhone since it came out and invested a reasonable amount of money in iOS Apps. Now, I'm considering a switch as for me, the maps app was one of the most useful things on the phone for finding my way once I had become lost, out on my bike.
Apple really has done a bad job on the maps for my area just north of London in the UK. Towns are mislabelled, villages will have their label shown while zoomed out, while larger towns won't be labeled at all on any zoom level.
Google may do well to hold out on making their maps accessible iOS6 to try and bring current previous generation iPhone users over to their operating system and its devices.
I am afraid the Maps for small countries like mine will be even worse.
A quick solution for you might be to use a third party GPS app/maps. Usually they are better than Google Maps (you do miss the integration with the other iOS apps though).
I wonder how much of the low quality is due to Apple (bugs of the new Maps app, which can be easily fixable) and how much is due to Open Street Map data being subpar (which needs much more time and work to fix)?
