
Drive the point home. Via DailyKos:
The Edwards proposal would cut off health care for the president, Congress and all political appointees in mid 2009, if a universal health care plan for all Americans has not been passed by then.
Finally, a policy I can understand.
There’s also that. Scott Rosenberg summarizes the Big Ball of Mud architecture:
Despite the best efforts of “best practices†advocates and methodology gurus, mud is everywhere you look in the software field. … Their answer: “People build big balls of mud because they work. In many domains, they are the only things that have been shown to work.â€
Yep.
Do some evil? What’s up with Yahoo these days? First they have to scare you into getting a Yahoo Mash account. And then spam on your behalf:
I imported my address book from GMail into Yahoo Mail today - and was HORRIFIED when Yahoo proclaimed that it was now going to spam all my contacts and tell them about my “new” Yahoo e-mail address.
What happened to their strategy to build compelling services?
Recently installed:
PulseAudio: A sound server to fix the deficiency that is aRts/ESound/ALSA. Works nicely, at least with Amarok (natively supported in the latest Xine engine).
CompizFusion: The new Beryl.
DD-WRT v23: Adds real time bandwidth graphs, I presume rendered in SVG, works flawlessly on Firefox. And DNS tunneling.
Google Presentation: Just kidding. This one just installed itself. Limited themes (read: they’re all ugly), but it does export nicely into HTML.
OPTIONS in Rails. Curiosity killed a few hours. The RESTful routing implementation in Rails 2.0 is not for the faint of heart, but with a few trials and errors, and Ruby is great for trying things out, I managed to spit out the right Allowed headers for each OPTIONS request. So yes, Rails can support this obscure and fairly unused HTTP feature.
Unfortunately, this all happens before filters (authentication, checks, etc), and I assume most developer will be oblivious and never bother to override the default behavior. I think this will be more trouble than it’s worth, so I filed it under”nice to know it can be done”, but no plans to release working code.
What did I learn? Rails 2.0 code is as thick as milkshake, but does not resist adding new features in odd places. And OPTIONS is a lottery feature.
Above, an Internet safety tips.