The first and only time I tried to make a reservation for el Bulli was in 2004 when I emailed them on January 7th for a table because I was told that they take reservations for the year starting in Jaunuary. Later, I found out that reservations for the following season are taken when the current season is completed, not at the beginning of the year as I erroneously thought. (Note: El Bulli is only open about six months per year in what they refer to as a "season," and each season starts and ends on different dates every year.) Of course they were unable to fill my reservation request.
I decided it's time to make a serious attempt at securing a reservation at el Bulli so I went to the reservation page on their website to determine when they will start accepting reservation requests for the following year.
I checked the reservation page out in mid-September and it said the 2009 season will start June 13th and ends December 20th and reservations will be accepted starting in mid-October of 2008, no exact dates given.
Not knowing what they mean by "mid-October," I sent an email (according to the reservation page, only email requests are accepted) to them on October 6th figuring that it's about a week into the month and maybe that's mid- enough for them. I asked for a dinner table for 4 for any available date for the 2009 season.
A day later I got my reply:
We do not take reservations for 2009 at this moment. You can send your request in mid October of 2008 to firstname.lastname@example.org as we never start the management until we have finished the season before.
October 14th-15-16th will be the first moment (there is not an exactly one to give the same option to the most possible of requests).
That sentence in parenthesis about not having an exact date was worrying but at least I have dates to work with now. So on the 14th at 2 p.m. (local time in Spain), I sent another reservation request. Again, I asked for a table for 4 for dinner for any available date.
There was no reply the next day like last time. I thought perhaps that's a good sign that they are working on fitting me into their reservation book. Because it would stand to reason that if it's full, they would just set some sort of auto-reply to all reservation requests coming in.
Two weeks later on the 28th I got my reply:
The demand that we have received at the first moment has again surpassed our limited possibilities for one season and we regret not to be able to full fill more reservation requests.
Son of a...
Their whole reservation process is so opaque that I can't even tell how I could improve my chances next year. You get one shot a year and it's very frustrating when you don't know exactly what you need to do in order to succeed.
Do I need to send my request at 00:01 on the first day of reservation? But when is that exactly? They gave me three dates and then said they can't tell me which one it is. So is it all a crapshoot? Should I have sent in a request at 00:01 on the 14th and then another on the 15th and another on the 16th? Then would I be in danger of annoying the reservationist and therefore getting my reservation canceled when three requests show up if they in fact started taking them on the first day? Send three requests on three different days from three different email accounts?
Do I get a better chance by requesting any dates or by requesting a specific date? Any date would seem more flexible and easier to accomodate but perhaps they don't want to deal with working with people who don't have firm dates?
Ah, just frustrating.
If you have a reservation, please tell me how you did it! Or better yet, let me join you! I'm crazy enough about food that I don't mind flying half-way across the world to eat with strangers! But seriously though, if anyone has a reservation that needs to be canceled, let me know, I'll happily take it.
I updated Figure-Ground.com with three buildings from Tokyo:
- Christian Dior Omotesando - SANAA
- Mikimoto Ginza 2 - Toyo Ito
- Tokyo International Forum - Rafael Viñoly
I still have about a half-dozen buildings that I have shot but have not had the chance to post.
As soon as I clicked "publish" on my previous entry complaining about excessive Mobile Safari crashing, I realized what I should have tried a long time ago: clear Mobile Safari's cache. And sure enough, after I cleared the cache and the cookies, I went nearly 2 hours of constant browsing before it finally crashed on me. Yes, it still crashed, but before clearing the cache, I couldn't even go 2 or 3 pages before it crashing.
My problem was that I kept thinking about the iPhone in terms of consumer electronics and phones and that it should "just work," thus I wasn't thinking in terms of troubleshooting the problem. It should just work, damit! Instead I should have been thinking about it in terms of what it really is—a tiny computer that makes phone calls. Computers crashing, that I have had plenty of experience with.
Now, if I could get the mail fetching to work again.
October 25, 2008 Update
Nope, not solved. It still crashes all over the place. With frequent purging of Mobile Safari cache, the frequency of crashes seems to be lower, but it still crashes way too often. I don't recall a single day without the browser crashing on me, and often it's multiple times.
The latest remedy I've tried is doing a hard reset (holding down the power and home buttons together for a few seconds) after the browser has crashed a few times in succession and that seems to make the crashing temporarily subside, but I'm not sure. The browser crashes so randomly that it's almost impossible to detect a pattern in order to identify a cause. It crashes on long pages, it crashes on short pages, it crashes on text heavy pages, it crashes on graphics heavy pages. It just crashes. Sometimes it can go for an hour without crashing. But then the crashes sometimes come in bunches. This is a typical scenario: Load page, finish loading, read, crash. Re-open Mobile Safari. Load a different page, during loading, crash. Open Mobile Safari again, load same page, finish loading. No crash. Yay! Load another page. Crash.
Maybe it just crashes whenever Mobile Safari runs out of memory which I assume is very easy to do since there's only 128mb of ram in the iPhone (what were they thinking?!). I think I read somewhere that Mobile Safari keeps running in the background until the OS needs the memory, so perhaps Mobile Safari just keeps crap in memory and grows and grows until it crashes.
I guess Mobile Safari is simply not ready to be used like I'm using it, which is usually at least an hour a day of browsing on it...
I haven't tried a complete restore from iTunes yet, but you know what? I don't want to spend days troubleshooting this damn thing!!! I give up. Forget about phones, even computers should not be this frustrating to use. It says something about the iPhone (its UI, its functionality, its packaging, and yes, its marketing... the Reality Distortion Field is strong with this one) that even with a major part of its functionality essentially broken (actually mail fetching is also broken, so that's two of its major functionalities), I can't even fathom giving it up and using another phone. I'm just going to have to suck it up and hope they fix it.
I have been using an iPhone 3G for just about a month and a half. It's been a decidedly up-and-down relationship with the device. On the one hand, it's the most amazing piece of consumer electronics I've ever used. On the other hand, it's the most frustrating one as well.
The bulk of my issues with the device (I hesitate to call it a "phone" because it is clearly much more than a phone) is that Mobile Safari is just too buggy. Firmware 2.1 did not improve on the stability, at least for me.
Sure, I browse the web on the iPhone when I'm out and about whenever I have some free time, but it turns out even more than a device to access the web when I'm not near a computer, the iPhone has become a go-to web access device even at home. It has taken the place of my laptop in bed right before I go to sleep, for example, and, yes, on the toilet if I'm having a... particularly big "download" queue.
But Mobile Safari crashes literally every few minutes for me. I haven't heard much of this issue being talked about online so I'm not sure if it's something with my particular iPhone. Bad memory perhaps? But nothing else on the phone appears to crash so it's limited to the Mobile Safari app (well, that and the NYTimes app, but I'm assuming that's using WebKit to render the pages so it's basically the same thing) which leads me to believe it's a software bug as opposed to a hardware one. It has crashed on basically every site I regularly visit (Google Reader, NY Times, Engadget, ESPN, to name a few). It crashes in the middle of doing nothing. For example, a page on NYTimes.com would finish loading and I would be in the middle of the article when Mobile Safari just quits to the home screen for no apparent reason.
Reading on a small screen in the palm of my hand turns out to be so satisfying for browsing the latest news that for the time being I'm putting up with the constant crashing, but it is extremely frustrating.
Phones and/or consumer electronics should not crash!
Putting aside the extreme bugginess (I've never used a web browser that crashed this much, literally every few minutes if I'm reading a lot of pages), Mobile Safari is s-l-o-w. The iPhone in general is no speed demon, but it really shows in Mobile Safari. I have a 10mbit connection at home, but you'd never know it if you judged it by the rendering speed on the iPhone.
But when it works, it's beautiful. It's like once you've used it, you can't go back to other phones, so you live with the slowness and crashiness just to experience the occasional high you get when it does work. It's like a bad drug.