I'm often wrong, but I was really wrong on something I wrote six years ago.
John Kawakami's blog
Read Apocalypse No! by Juan Santos.
Rosemead just voted Wal-Mart into the city.
To say the least, I'm crestfallen.
After two years of fights, after seven months of meetings, and a couple months of intense organizing, we lost.
I can't say that I didn't see it coming. The only time that a big developer is opposed is with the support of the City Council, and it appears, from the start, that most of the City Council was siding with Wal-Mart.
Reports from people visiting the city offices seemed to indicate that there was a gag-rule about the project. They wanted to keep the project as secret as possible so that people wouldn't get up-in-arms about it.
The big disappointment, for me, was Margaret Clark. She said she was supporting it, but then whipped out her past positions opposing NAFTA/GATT and her seat on a clean air committee. If there's any company out there that exemplifies NAFTA and GATT, it's Wal-Mart. Just look at their China office.
The nice surprise was Bob Alarcon, who did address some of the concerns in his questions. That was something. Gary Taylor, who had managerial ties to Wal-Mart through his family, was especially defensive.
I was a little bummed out about the amount of rancor in the room. People's helplessness and disgust with the system were palpable, and it came out with angry statements. I sat on the right side of the room, where the pro- side sat, for a while a while, and the smugness there was also palpable.
I was reading up on calendar data structures and came across something I hadn't thought about in years: the 2038 problem.
This is more serious than the year 2000 problem that was supposed to lead to the collapse of technological society. Out in my neck of the relatively modern woods, all that Y2K meant was that a few applications started displaying 19100 instead of 2000, and a few others showed the wrong time or date. They were fixed with minimal incident.
Y2038 is more serious. It's a problem a lot of Unix applications will suffer if they're still running in 34 years. Now, that might sound far-fetched, but, consider this: many important parts of Linux were written in the early 1990s, and haven't yet been updated. Many of these programs were originally written in the early 80s, and the origins of Unix as we know it go back to 1970.
We're already past the halfway mark: Unix is 34 years old, and there are only 34 years left until 2038. So, let's be conscious of this issue, and start dealing with it now, before it's too late.
The Year 2038 Problem
It's better and more confusing than the soap opera. It's my adventures at General Hospital LAC+USC. Let's get caught up on the story.
Rosa's spleen is enlarged, and she's caught up in "the system". Her boyfriend, John, is tagging along, marvelling at the Byzantine system that is LAC+USC. They both worry that the condition can be polycythemia, a rare condition where the marrow produces red blood cells nonstop, and if left untreated, will lead to thrombosis, and death. It could also be a bruised spleen from a fall.
This morning, I got a call from Rosa requesting a ride to the hospital. She'd talked to a nurse there to get her blood test results. Simple enough, I thought. I get that kind of info over the phone sometimes. But, no, she had to go in person.
When I drove her there, it took a few minutes for Rosa to be told that, no, the results would not be given out. The doctor needed to talk with her. So an appointment was scheduled. Also, they would not schedule her to CT scan her spleen, despite the fact that the doctor requested it last time.
That seemed stupid. The scan was requested at the prior appointment. They should just send the request, so it can be performed before the doctor appointment. That would knock out two birds with one stone.