With the renaming of Paradise Pier, none of the opening day lands of Disney California Adventure remain.
This does not mean that all attractions, buildings, or theming of the original lands have been replaced. It means that every land existing on opening day has at least been renamed, with many rethemed, and some reassigned to other lands.
On opening day, DCA guide maps listed four lands: Entry Plaza1, Hollywood Pictures Backlot, Golden State, and Paradise Pier. These are all now gone.
Golden State was divided into areas, mini-lands within a big land: Grizzly Peak Recreation Area, Condor Flats, TheBay Area, Pacific Wharf, and Golden Vine Winery. These were not full lands when the park opened. Over time, some areas have disappeared as separate areas (The Bay Area, Golden Vine Winery), while others have become lands of their own (Grizzly Peak, Pacific Wharf), and one area even managed to do both (Condor Flats).2
I believe DCA is the only Disney park that has replaced or renamed all of its opening day lands.3
Research for the timeline was done using my collection of guide maps from the park as well as online announcements or news articles of land and attraction openings and closings. Please feel free to send me any feedback or corrections at https://jamesdempsey.net/contact.
Also feel free to contact me at https://jamesdempsey.net/contact if you have guide maps from the early years of DCA that you are willing to sell – or send photos of. I am particularly trying to find DCA maps between late February and late May 2001 to pinpoint the change from Entry Plaza to Sunshine Plaza.
I’ve enjoyed witnessing the transformation of Disney California Adventure over its seventeen year history and hope you enjoy this visual history of its lands. •
About me: I’m a Disney, Pixar, and Apple history hobbyist. I worked at Apple for fifteen years then set out on my own as a software developer, technical trainer, speaker, and musician. I write humorous songs about technical things. My album debuted at #5 on the Billboard comedy album charts and was the #1 comedy album on iTunes in the US, UK, and Canada. If you or someone you know (or someone in Disney Imagineering) needs an original song with clever lyricscontact me!
1 Yes, Entry Plaza. The opening day DCA guide maps use this name. Within months, the name on the maps changed to Sunshine Plaza. ⏎
2 Golden Vine Winery is a good example an area which is still very similar to opening day, but has technically ‘disappeared’. This was originally an area, or sub-land, of Golden State. When the Seasons of the Vine attraction closed and became reopened as Walt Disney Imagineering Blue Sky Cellar, the reopened attraction was now listed as part of Pacific Wharf, where it remains as of 2018. ⏎
3 Pacific Wharf is the only remaining original land or area that has not been renamed. But it was not a land on opening day, it began as an area of Golden State and was not promoted to a full land until 2012. Grizzly Peak Recreation Area was renamed to the much simpler Grizzly Peak when it also became a full land in 2012.⏎
I’ll be doing a few things next week at WWDC and wanted to pass along my schedule. Hope to see you at one or more of these happenings!
Tuesday: Speaking at the NextDoor Conference
Tuesday morning, I’m speaking at the Next Door conference, located, remarkably enough, next door to WWDC.
I’ll be talking about two of the more glamorous aspects of app development: build settings and xcconfig files. In the session, we’ll cover the why and how of giving your build settings an out-of-project file experience to make build settings easier to manage.
Wednesday night, my band, James Dempsey and the Breakpoints, performs our 7th annual LIVE near WWDC show. The party starts at 7 pm—tickets include an open bar. The band goes on at about 8:30 pm, playing a full concert of original, humorous, programming-oriented, and yes, even chart-topping music.
But the night is more than just music and fun—it’s a benefit concert for App Camp For Girls, with ticket proceeds going to support their programs. Come on out on Wednesday night to a great event for a great cause!
I’ll be closing out the week at AltConf with my fifth annual WWDC Week In Review, a lighthearted look back at the announcements and events of the week.
After a week front-loaded with announcements and technical talks—this easy-going closing session of AltConf combines humor, music, and a bit of perspective. I hope you join me to be entertained and maybe occasionally enlightened.
And, as usual, there will be a bit involving a ukulele.
As usual, it will be a busy WWDC week with plenty of new announcements and technology to wrap our heads around. If you see me out and about during the week, please say hello!
I hope you can make it out to one or more of these events—see you at WWDC! •
I have a sad update. Wilbur Dempsey, my father, passed away yesterday afternoon.
He died peacefully without pain in the hospital. He was surrounded in his final hours by his children and a few other loved ones.
Ten days before he died, Dad at 92 years old was still mentally sharp, still living on his own, and still driving. He drove down to my sister Ann’s for their usual Sunday dinner. He would always stay overnight and drive home to Milltown in the morning.
The next morning he was not feeling well, so he stayed with my sister. His decline happened quickly over the next week. He found it increasingly difficult to walk, becoming more tired and losing energy and his appetite.
Tuesday morning he was unresponsive and taken to the hospital. I arrived late in the evening that same day and we spent the night with Dad in the hospital.
Dad never regained consciousness, but during that time we had our chance to tell him how much we loved him, to share our favorite memories with him, and tell him through tears how much we would miss him.
The photo below is of Dad ten days ago on March 18th.
The world has lost a truly kind, selfless person who brought so much joy, laughter, and sunshine to everyone around him.
As software developers, we all screw up. We all check in software with accidental bugs. We’re all constantly coming up to speed with new frameworks, tools, APIs, language features, concepts, and best practices. We’re all trying to accomplish a lot in a limited amount of time.
I think the hashtags Dave used, #BeNice and #DontBeAJerk, convey the sentiment that we should have empathy for each other as developers and as human beings.
Of course, all software has room for improvement and I also think it’s perfectly valid to vent frustrations about the tools you use professionally.1
But I don’t think disparaging the people who work on the software or attributing bad motives to them is helpful at all.
That said, I think it’s fair that the same principle should extend to Xcode itself, especially something that has bothered me for a long time: Blame.
Blame is “responsibility for a fault or wrong” — a word with a very negative connotation.
In Xcode, every line of code is a mea culpa.
Blame is pointing fingers without solving the issue at hand.
In Xcode, the Blame view and the Show Blame For Line menu item imply that the code you or anyone else writes is a reason to be embarrassed and ashamed.
According to the Xcode user interface, every line of code written for Apple platforms is something that should be apologized for—every app in the App Store built from culpable actions and misdeeds.
Blame doesn’t belong in the user interface of Xcode.
Words Matter
There’s a reason it’s not called Flounder.
You could certainly make the case that it’s just a word and no big deal. But I believe words matter.
If you clicked on this article based on the title, thinking you would be reading an accusatory, negative piece about Xcode, then you have just experienced the power of the word blame.
And folks at Apple know that words and their connotations matter. There’s a reason it’s called ‘Swift’ and not ‘Sloth’ or ‘Flounder’. There’s a reason we’ll probably never see ‘macOS Death Valley’ even though, like Yosemite, it’s a National Park in California.
That’s How Git Does It
Author! Author! in an Xcode without Blame.
You could also make the case that blame is the command name in git. But the git command diff corresponds the Comparison view in Xcode. So using exact git terminology in Xcode is not sacrosanct. Even if it was, git has the equivalent and less pejorative annotate.2
Of course, Apple has a long history of forging its own path, regardless of what others in the industry are doing. One could imagine taking the same approach as with the Comparison view and using a name that has nothing to do with an existing git command. The icon in the Version editor pop-up menu already shows the outline of a person. That view could possibly be called the Author view, with a corresponding Show Author For Line menu item.
Just A Joke
You could also say that blame is just a wry bit of humor and if everyone knows it, then it lessens the negative connotation.
But not everyone is necessarily in on the joke. An example is people who are just learning to write code and develop apps. Learners, whether children or adults, can have a fear of failure when trying something new, compounded by a fear of being ridiculed for failing when trying. People new to programming don’t know all of our witty little inside jokes, they just know that Xcode is assigning blame to their efforts.
Apple has been touting the Everyone Can Code program for a few years now, including courses on building apps in Xcode. It think it is great that Apple is making such efforts to teach programming skills to a wide audience. But blame doesn’t belong in a learning environment.3
This wasn’t so customers would know who to blame. This was because artists sign their work.
Similarly, as software developers, our names are embedded in every commit. They are a record of our work and effort, a record of every success and failure, a record of every hard-won lesson learned.
Whether you are a complete newcomer or an experienced coder, you should be able to take pride in your work as a developer. Your tools should do their best to help you. Your tools should acknowledge and, if possible, even celebrate your authorship, not disparage it.
Please take the blame out of Xcode.
It’s one small change in a .strings file, but may be one giant leap for our coding culture. •
I filed a Radar about this issue in June 2011 while still working at Apple—it was closed as Not To Be Fixed. Today I filed another bug report which you can see on OpenRadar. Feel free to file duplicates.
UPDATE: In the Xcode 9.3 betas, blame has been removed from Xcode. From the release notes:
Renamed user interface elements to clarify the information presented. In the Version editor “Blame View” is now “Authors View” and in the Source editor “Show Blame For Line” is now “Show Last Change For Line.” (35031446)
1 But don’t expect venting to change anything. The best approach is still to file a bug. That’s no guarantee your issue will be addressed, but you’ve provided the constructive feedback. Of course, the opacity of the Apple bug reporting system has its own frustrations and is its own can of worms.⏎
3 In Xcode 9, ‘Show Blame For Line’ is no longer in the code editor contextual menu in Xcode Playgrounds, but it’s still in the Editor menu. But students also want to build apps, and outside of Xcode Playgrounds, blame is still in full force.⏎
Last week at WWDC 2017, Apple announced a new build system for Xcode, with an opt-in preview in Xcode 9. The new system is written in Swift and promises to be a significant advance in a number of areas including performance and dependency management. The new system is built on top of the open source llbuild project and lays the foundation for integrating the Xcode build system with the Swift Package Manager.
You opt in to the new build system per project or workspace. To do so in the Xcode 9 beta, open a project file and then go to File > Project Settings… and in the sheet that appears, choose New Build System (Preview) from the Build System popup menu. Note that the menu item will be File > Workspace Settings… if you are working with a workspace.
Opt-in to the new build system for a project in File > Project Settings… (For a workspace use File > Workspace Settings…)
The big news of a new build system made me curious to see if there were any changes I would need to make to BuildSettingExtractor.
BuildSettingExtractor helps you move to xcconfig files.
If you are not familiar with it, BuildSettingExtractor is an open source utility that helps you move to using xcconfig files. It reads the build settings embedded in an Xcode project file and extracts the settings into xcconfig files. It can also extract the Xcode help for each build setting to produce automatically documented configuration files. (Read my prior post Generating Xcode Build Configuration Files with BuildSettingExtractor for more about the benefits of using xcconfig files.)
My investigation led me to look more closely at what was changing and what was staying the same when it came to the new build system and build settings in Xcode 9.
When it comes to build settings, there are two big operations: Defining build settings and using build settings.
As developers, we spend our time on the first part, defining build settings1. In a complex project or workspace, this can be an involved process. Defining build settings includes all of the following:
Build settings defined for each target and for the project itself
Variable substitution to define derived build settings using ${} or $()
Conditional build settings based on build configuration, architecture, and SDK
Optionally using xcconfig files to define build settings
Understanding the well-defined hierarchy of how build settings are inherited and used
In the end, these intricate and flexible mechanisms for defining build settings resolve into a big dictionary of key-value pairs that is passed to the build system.
The build system is what uses the build settings to help direct how it builds a target. The build system coordinates the various tools required, such as the compiler and linker. It uses a target’s build phases and build settings to generate a build product (e.g. app, extension, framework, library). It understands all of a target’s dependencies and builds them as well. The build system is a complicated beastie with a lot of responsibilities and it is what is being modernized beginning in Xcode 9.
New build system. Same build settings.
On a number of my projects, I’ve switched from the current build system to the new build system in Xcode 9 to investigate. It appears that everything about defining build settings remains unchanged. Moving between the old and new build systems did not cause any build setting changes or recommended changes. The mechanisms for generating that giant bucket of key-value pairs known as build settings seem to be just the same as before.
This is great news. As developers, we don’t need to learn a new complex system for defining build settings. We get to enjoy the benefits of a new, faster, modern build system with our existing build settings left intact.
As the developer of BuildSettingExtractor, this is also great news—no big changes required. After doing some testing and a tweak here and there, BuildSettingExtractor is now updated to work with the Xcode 9 beta. I invite you to check out BuildSettingExtractor and the new build system in Xcode 9. •
