Earlier quoted context omitted.
What's interesting about this rebuild is it tell us Apple tightly couples it's services. I would except at Apple's scale they would have followed a Service Oriented Architecture. This doesn't seem to be the case at all. And whatever happened to static hosting for videos/downloads.
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 detail…
Apple Developer System Status
51–60 of 72 posts
Re: Apple Developer System Status
#52Earlier quoted context omitted.
What's interesting about this rebuild is it tell us Apple tightly couples it's services. I would except at Apple's scale they would have followed a Service Oriented Architecture. This doesn't seem to be the case at all. And whatever happened to static hosting for videos/downloads.
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 detail…
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.
Re: Apple Developer System Status
#53Ughhh. Just noticed that I can't install the XCode Command Line Tools because the dev center is down... no stdio.h on my system. What is this, the dark ages!? :)
I successfully installed the XCode command line tools on a new machine yesterday via the Preferences dialog box in XCode. The web installation route is definitely unavailable, but the Preferences route appears to continue to work.
Re: Apple Developer System Status
#54Earlier quoted context omitted.
I successfully installed the XCode command line tools on a new machine yesterday via the Preferences dialog box in XCode. The web installation route is definitely unavailable, but the Preferences route appears to continue to work.
If you don't yet have XCode though... out of luck? Man, I'm glad I bought and setup my new mac two weeks ago, and not one week ago.
Re: Apple Developer System Status
#55Re: Apple Developer System Status
#56Earlier quoted context omitted.
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 detail…
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 yea…
Re: Apple Developer System Status
#57Does anyone know when the current iOS beta expires? If they don't get it together by then, going to be a lot of sad eager adopters...
Re: Apple Developer System Status
#58Earlier quoted context omitted.
In 1993, you were almost certainly going to have to pay money to write software on or for Mac OS. In 2013, you most certainly do not have to pay money on or for Mac OS X. Xcode is free-as-in-beer. You can install this if you want to avoid Apple's tooling: https://github.com/kennethreitz/osx-gcc-installer Ruby, Python, Perl and other interpreters come standard with OS X. As does a terminal. Things are better, not wors…
>In 2013, you most certainly do not have to pay money on or for Mac OS X. You have to join the Apple Developer Program, which costs $99/year, in order to distribute software that will run on OS X with default Gatekeeper settings. The registration for that program is currently down.
1. Using a browser other than Safari
2. Holding Option while opening the dmg
3. Changing the Gatekeeper settings
In practice #1 means that many people never even notice Gatekeeper.
Re: Apple Developer System Status
#59Does anyone know when the current iOS beta expires? If they don't get it together by then, going to be a lot of sad eager adopters...
Re: Apple Developer System Status
#60Earlier quoted context omitted.
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 detail…
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.
Steve Jobs used to hawk it on 486s while wearing ripped jeans. http://www.foxnews.com/static/managed/img/World/Steve%20Jobs...