My mother was one of the first female programmers at Honeywell back in the `70s. Back then, IT companies recruited their programmers from the ranks of mathematicians (like mom).

Grace Hopper was a big hero to her, and one of the things I remember best is mom coming home with a short length of wire given out by Adm. Hopper at a speech -- sized to represent the distance electricity would travel in a nanosecond.

Mom is still coding, by the way, writing custom software for my dad's business in Python/Django/PostgreSQL. Dad complains that she's obsessed with the programming and won't do anything else. Sounds like me...thanks for the genes, mom!

You're mischaracterizing Brendan's position on DRM, as I'm sure he would tell you if you just asked him personally. I strongly recommend you do so.

He doesn't like DRM, and neither does anyone else at Mozilla, but you do realize that he was CTO and then CEO while most of the negotiations with Adobe were happening, right?

Fact: There are very few "traditional" tech companies around Sacramento.

Fact: The pones that are there, know that and they consistently offer ~50-60% of Bay Area wages. They only want to hire recent college grads, not experienced people.

Fact: I recently left and won't be heading back. Besides, there are lots more good looking women here in the Bay Area. :)

We've tried sandboxing the plug-in process Flash runs in. It breaks all sorts of existing Flash-using stuff, unfortunately.

The benefit of having a sandbox from day 1 is that you don't have that problem.

The difference is that the CDM will be sandboxed in a low-privilege process with no direct access to the OS and kernel, which is not at all how Flash works.

You really think this sort of decision, complete with all the negotiations involved, was made over the course of a month?

1) A third party is writing the plugin.
2) We did wait until it was inevitable. Every single other browser is already shipping it, Netflix is using it, and other sites are starting to use it. The only alternative to shipping this was to make sure Netflix and other video sites continued to work with Flash or Silverlight _and_ that Flash and Silverlight continue to work indefinitely.

Interestingnow that I reflect on it, my experiences are similar.

Perhaps it is because humans dislike change?

One reason lectures are so popular is that they are far, far easier for the instructor. Putting together a useful interactive activity is much harder than simply planning what to say. Even incorporating someone else's pre-designed activity is difficult to synchronize with one's own lesson plan. At the grade school level, I believe there is considerable room for improvement through teachers learning how to share and use activity plans.

At the college and graduate school level, it gets much harder on the professor as potential sources of planned activities thin out and specialization increases. Increasing interactivity demands much more time of these professors since most such improvements will have to be custom-designed for the class. Given the social structure of university compensation (research counts, teaching doesn't), I find it hard to see interactivity at the college or grad school level increasing very quickly.

That said, college and grad school courses are perhaps more interactive than they are given credit for. They often meet just a few times a week, reducing the boring lecture hours, and assign a lot of homework, increasing interactivity in a way that fails to appear in the studies cited.

For context, I am an adjunct professor (at the graduate school level). Based on this daily of studies I try to include some interactivity but it's really hard, so that mainly degenerates into a few intra-class status quizzes. My classes tend to meet for 2.5-3 hours per week, and have 5-20 hours of homework on top of that.

That's not a very bright statement. What you should wish to avoid is for something bad to happen. One way that can happen is indeed for a gun to fail when it needs to work, but there are others, for example having an unseen companion assailant seize the gun and shoot you with it.

It's all about the probabilities of various scenarios, and anyone failing to incorporate that that in their evaluation is not worth listening to. (For the record, I have no opinion about what those probabilities are, but live in such a safe place that I don't consider bothering with a gun.)

Mozilla decided to create B2G for several reasons, but one of them is because most of the world's population in the near future will be accessing the internet from a phone or _maybe_ a tablet, not a full-on laptop or desktop. And people using phones or tablets don't install non-default web browsers, statistically speaking, not least because storage is pretty limited on phones, so if Mozilla wanted to be in the market at all it needed to be shipping the default browser on a phone people would use.

There was also the reason of wanting a phone/tablet marketplace without vendor lock-in, which requires apps to be portable between phones from different vendors. That's where web apps come in. And yes, apps that you can move to your new phone even if you get it from a different manufacturer are intrinsically more valuable than apps that you lose if you move from iOS to Android or vice versa.

As for why you'd go for Firefox OS over Android, one answer is it performs better on limited hardware (think a phone with 256 megs ram, and yes, it's pretty hilarious what counts as "limited hardware" nowadays). If you say you're not likely to be buying a phone with those sorts of hardware specs, then you're not the target market. Remember what I said about "most of the worlds population" above? Well, the total population of Europe and North America is about 25% of the population of the world. The other 75% is not out to buy $600 phones. Neither are parts of Europe and North America, of course...

As a cyclist who commutes year-round in Chicago, I just want to give a little shout out to the motorists, who are almost all incredibly polite. It's human nature for us to notice and remember the jerks (and I recall a few) but the incredibly vast majority of motorists are accommodating, friendly, and (when paying attention) cautious.

If I have one request of motorists, it's to get off the cell phones, something I am sure every road user -- pedestrian, cyclist and motorist agrees with.

Agree!....I despair of ever managing to lay a good caulk bead.

The search bar is there for a simple reason. It's to allow a place to do searches with search autosuggest without sending every single URL you type to the search provider.

Chrome adopts the "send all the URLs the user types to the search provider" approach by default, unsurprisingly.

Of course if you don't care about the search autosuggest feature, you can just customize away the search bar.

Actually, they do not have that right. Employers in California are explicitly prohibited from doing that. See California Labor Code section 1102 at http://www.leginfo.ca.gov/cgi-...