Spring in Burbank
Mar. 26th, 2009 03:19 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
tealinFor two mounths out of the year there are actually green growing things in this parched valley. Rejoice! Frolic! Take pictures!
There's a field between the studio and the freeway – I don't know who owns it, but it's used by people exercising their horses. Every time I'd park my bike in the morning I'd see how much bigger the little green shoots had grown, taking advantage of the four or five rainstorms we've had this winter. Only just last week I actually rode my bike through the field and was surprised how much was out there. I thought I should take pictures before they mow it all down in a couple weeks for fire safety.
I don't know what the weed-that-looks-like-geraniums is called, but it's grown in some form nearly everywhere I've lived. I've never seen it grow as tall as me before, though, not even in lush green Canada. Must be all the horse poo.
Look, trees!
This is an overview of the field from the second floor of the studio:
And look, the hill! THERE IS GREEN ON IT!
We're on the wrong side of it to get foggy mornings most of the time, but it makes for a neat effect anyway:
I walked towards it every day two summers ago, and lived at its base for a couple months before I learned that the world-famous Hollywood sign is just on the other side of that flat bit with the antennae. It's just the hill in my backyard! Mind asplodey.
If you catch the right light and crop it cleverly, Burbank doesn't look half bad, sometimes...
Hey Mac users! Do you ever find that if it's been running for a while (like over 24 hours) Firefox gets, for lack of a better term, tired? Like, it'll stop loading images or page formatting and sometimes you'll get to a page and just ... none of the links work. If I quit and restart it works fine, but I don't like quitting Firefox becauseI am not a quitter I have stuff loaded that I need to refer to and if I close it I have to reload it all, which is a waste of time and server brainpower. Is this a Mac thing or is it just my own personal MacBook McBuggy over here?
There's a field between the studio and the freeway – I don't know who owns it, but it's used by people exercising their horses. Every time I'd park my bike in the morning I'd see how much bigger the little green shoots had grown, taking advantage of the four or five rainstorms we've had this winter. Only just last week I actually rode my bike through the field and was surprised how much was out there. I thought I should take pictures before they mow it all down in a couple weeks for fire safety.
I don't know what the weed-that-looks-like-geraniums is called, but it's grown in some form nearly everywhere I've lived. I've never seen it grow as tall as me before, though, not even in lush green Canada. Must be all the horse poo.
Look, trees!
This is an overview of the field from the second floor of the studio:
And look, the hill! THERE IS GREEN ON IT!
We're on the wrong side of it to get foggy mornings most of the time, but it makes for a neat effect anyway:
I walked towards it every day two summers ago, and lived at its base for a couple months before I learned that the world-famous Hollywood sign is just on the other side of that flat bit with the antennae. It's just the hill in my backyard! Mind asplodey.
If you catch the right light and crop it cleverly, Burbank doesn't look half bad, sometimes...
Hey Mac users! Do you ever find that if it's been running for a while (like over 24 hours) Firefox gets, for lack of a better term, tired? Like, it'll stop loading images or page formatting and sometimes you'll get to a page and just ... none of the links work. If I quit and restart it works fine, but I don't like quitting Firefox because
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2009-03-28 10:40 pm (UTC)What would happen is that you'd boot up and open a program which would grab a piece of RAM, and then when you were finished you would open up another, which would grab what it needed, but the first program wouldn't turn loose of all that it had grabbed because it was still open. So after a couple of hours and 3-4 programs, all still running, you would switch back to one of the ones you started with and try to do something and it would try to grab some more RAM to deal with the new commands you were giving it, and either there wouldn't be any, or what it got would be in two bits and they didn't necessarily work together very smoothly.
OSX has a *much* better internal memory management which generally smooths over the gaps and makes things work far better, but memory in bits is probably still memory in bits, and doesn't work as smoothly as memory in one big chunk.