The basic problem is, every newfangled “try code out for yourself” site I hit is just failing in Firefox 11 and 12. Dabblet, for example, just returns a big blank page with the toolbar across the top, and none of the top-right buttons work except for the Help (“?”) button. And I write all that in the present tense because the problem still exists as I write this.

What’s happening is that any attempt to access localStorage, whether writing or reading, returns a security error. Here’s an anonymized example from Firefox’s error console:

Error: uncaught exception: [Exception... "Security error" code: "1000" nsresult: "0x805303e8 (NS_ERROR_DOM_SECURITY_ERR)" location: "http://example.com/code.js Line: 666"]

When you go to line 666, you discover it refers to localStorage. Usually it’s a write attempt, but reading gets you the same error.

But here’s the thing: it only does this if your browser preferences are set so that, when it comes to accepting cookies, the “Keep until:” option is set to “ask me every time”. If you change that to either of the other two options, then localStorage can be written and read without incident. No security errors. Switch it back to “ask me every time”, and the security errors come back.

Just to cover all the bases regarding my configuration:

1. Firefox is not in Private Browsing mode.
2. dom.storage.default_quota is 5120.
3. dom.storage.enabled is true.

Also: yes, I have my cookie policy set that way on purpose. It might not work for you, but it definitely works for me. “Just change your cookie policy” is the new “use a different browser” (which is the new “get a better OS”) and it ain’t gonna fly here.

To my way of thinking, this behavior doesn’t conform to step one of 4.3 The localStorage attribute, which states:

The user agent may throw a SecurityError exception instead of returning a Storage object if the request violates a policy decision (e.g. if the user agent is configured to not allow the page to persist data).

I haven’t configured anything to not persist data—quite the opposite—and my policy decision is not to refuse cookies, it’s to ask me about expiration times so I can decide how I want a given cookie handled. It seems to me that, given my current preferences, Firefox ought to ask me if I want to accept local storage of data whenever a script tries to write to localStorage. If that’s somehow impossible, then there should at least be a global preference for how I want to handle localStorage actions.

Of course, that’s all true only if localStorage data has expiration times. If it doesn’t, then I’ve already said I’ll accept cookies, even from third-party sites. I just want a say on their expiration times (or, if I choose, to deny the cookie through the dialog box; it’s an option). I’m not entirely clear on this, so if someone can point to hard information on whether localStorage does or doesn’t time out, that would be fantastic. I did see:

User agents should expire data from the local storage areas only for security reasons or when requested to do so by the user.

…from the same section, which to me sounds like localStorage doesn’t have expiration times, but maybe there’s another bit I haven’t seen that casts a new light on things. As always, tender application of the Clue-by-Four of Enlightenment is welcome.

Okay, so the point of all this: if you’re getting localStorage failures in Firefox, check your cookies expiration policy. If that’s the problem, then at least you know how to fix it—or, as in my case, why you’ll continue to have localStorage problems for the next little while. Furthermore, if you’re writing JS that interacts with localStorage or a similar local-data technology, please make sure you’re looking for security exceptions and other errors, and planning appropriate fallbacks.

My reason to bring this up is that I’m very interested by how TypeButter accomplishes its kerning: it inserts kern elements with inline style attributes that bear letter-spacing values. Not span elements, kern elements. No, you didn’t miss an HTML5 news bite; there is no kern element, nor am I aware of a plan for one. TypeButter basically invents a specific-purpose element.

I believe I understand the reasoning. Had they used span, they would’ve likely tripped over existing author styles that apply to span. Browsers these days don’t really have a problem accepting and styling arbitrary elements, and any that do would simply render type their usual way. Because the markup is script-generated, markup validation services don’t throw conniption fits. There might well be browser performance problems, particularly if you optically kern all the things, but used in moderation (say, on headings) I wouldn’t expect too much of a hit.

The one potential drawback I can see, as articulated by Jake Archibald, is the possibility of a future kern element that might have different effects, or at least be styled by future author CSS and thus get picked up by TypeButter’s kerns. The currently accepted way to avoid that sort of problem is to prefix with x-, as in x-kern. Personally, I find it deeply unlikely that there will ever be an official kern element; it’s too presentationally focused. But, of course, one never knows.

If TypeButter shifted to generating x-kern before reaching v1.0 final, I doubt it would degrade the TypeButter experience at all, and it would indeed be more future-proof. It’s likely worth doing, if only to set a good example for libraries to follow, unless of course there’s downside I haven’t thought of yet. It’s definitely worth discussing, because as more browser enhancements are written, this sort of issue will come up more and more. Settling on some community best practices could save us some trouble down the road.

Update 23 Mar 12: it turns out custom elements are not as simple as we might prefer; see the comment below for details. That throws a fairly large wrench into the gears, and requires further contemplation.

My hope is that the interview brings clarity to a situation that has suffered from a number of misconceptions. I do not necessarily hope that you agree with Tantek, nor for that matter do I hope you disagree. While I did press him on certain points, my goal for the interview was to provide him a chance to supply information, and insight into his position. If that job was done, then the reader can fairly evaluate the claims and plans presented. What conclusion they reach is, as ever, up to them.

We’ve learned a lot over the past 15-20 years, but I’m not convinced the lessons have settled in deeply enough. At any rate, there are interesting times ahead. If you care at all about the course we chart through them, be involved now. Discuss. Deliberate. Make your own case, or support someone else’s case if they’ve captured your thoughts. Debate with someone who has a different case to make. Don’t just sit back and assume everything will work out—for while things usually do work out, they don’t always work out for the best. Push for the best.

And fix your browser-specific sites already!

The other was the publication of the minutes of the CSS Working Group meeting in Paris, where it was revealed that several vendors are about to support the -webkit- vendor prefix in their own very non-WebKit browsers. Thus, to pick but a single random example, Firefox would throw a drop shadow on a heading whose entire author CSS is h1 {-webkit-box-shadow: 2px 5px 3px gray;}.

As an author, it sounds good as long as you haven’t really thought about it very hard, or if perhaps you have a very weak sense of the history of web standards and browser development. It fits right in with the recurring question, “Why are we screwing around with prefixes when vendors should just implement properties completely correctly, or not at all?” Those idealized end-states always sound great, but years of evidence (and reams upon reams of bug-charting material) indicate it’s an unrealistic approach.

As a vendor, it may be the least bad choice available in an ever-competitive marketplace. After all, if there were a few million sites that you could render as intended if only the authors used your prefix instead of just one, which would you rather: embark on a protracted, massive awareness campaign that would probably be contradicted to death by people with their own axes to grind; or just support the damn prefix and move on with life?

The practical upshot is that browsers “supporting alien CSS vendor prefixes”, as Craig Grannell put it, seriously cripples the whole concept of vendor prefixes. It may well reduce them to outright pointlessness. I am on record as being a fan of vendor prefixes, and furthermore as someone who advocated for the formalization of prefixing as a part of the specification-approval process. Of course I still think I had good ideas, but those ideas are currently being sliced to death on the shoals of reality. Fingers can point all they like, but in the end what matters is what happened, not what should have happened if only we’d been a little smarter, a little more angelic, whatever.

I’ve seen a proposal that vendors agree to only support other prefixes in cases where they are un-prefixing their own support. To continue the previous example, that would mean that when Firefox starts supporting the bare box-shadow, they will also support -webkit-box-shadow (and, one presumes, -ms-box-shadow and -o-box-shadow and so on). That would mitigate the worst of the damage, and it’s probably worth trying. It could well buy us a few years.

Developers are also trying to help repair the damage before it’s too late. Christian Heilmann has launched an effort to get GitHub-based projects updated to stop being WebKit-only, and Aarron Gustafson has published a UNIX command to find all your CSS files containing webkit along with a call to update anything that’s not cross-browser friendly. Others are making similar calls and recommendations. You could use PrefixFree as a quick stopgap while going through the effort of doing manual updates. You could make sure your CSS pre-processor, if that’s how you swing, is set up to do auto-prefixing.

Non-WebKit vendors are in a corner, and we helped put them there. If the proposed prefix change is going to be forestalled, we have to get them out. Doing that will take a lot of time and effort and awareness and, above all, widespread interest in doing the right thing.

Thus my fairly deep pessimism. I’d love to be proven wrong, but I have to assume the vendors will push ahead with this regardless. It’s what we did at Netscape ten years ago, and almost certainly would have done despite any outcry. I don’t mean to denigrate or undermine any of the efforts I mentioned before—they’re absolutely worth doing even if every non-WebKit browser starts supporting -webkit- properties next week. If nothing else, it will serve as evidence of your commitment to professional craftsmanship. The real question is: how many of your fellow developers come close to that level of commitment?

And I identify that as the real question because it’s the question vendors are asking—must ask—themselves, and the answer serves as the compass for their course.

I wil reiterate something I said on Twitter, though: the members of tech community, particularly those who are intimately familiar with the basic protocols of the Internet, need to keep working on ways to counteract SOPA/PIPA. What form that would take, I’m not sure. Maybe a truly distributed DNS system, one that can’t be selectively filtered by any one government or other entity. I’m not an expert in the area, so I don’t actually know if that’s feasible. There’s probably a much more clever solution, or better still suite of solutions.

The point is, SOPA and PIPA may soon go down to defeat, but they will return in another form. There is too much money in the hands of those who first drafted these bills, and they’re willing to give a fair chunk of that money to those who introduced the bills in Congress. Never mistake winning a battle with winning the war. As someone else observed on Twitter (and I wish I could find their tweet now), the Internet community fought hard against the DMCA, and it’s been US law for more than a decade.

By all means, take a moment to applaud the widespread and effective community effort to oppose and (hopefully) defeat bad legislation. When that’s done, take notes on what worked and what didn’t, and then prepare to fight again and harder. Fill the gap between battles with outreach to your elected representatives and with efforts to educate the non-technical in your life to explain why SOPA/PIPA were and are a bad idea.

Days of action feel great. Months of effort are wearying. But it’s only the latter that can slowly and painfully bring about long-term change.

Instead, I will reproduce here the letter I attempted to send via contact form to my state Senator this morning, and which I will print out and send by regular postal service later today.

Senator Brown:

I grew up in Lexington, Ohio. I moved to Cleveland in pursuit of a career, and found success. Through a combination of good luck and hard work, I have (rather to my surprise) become a widely recognized name in my field, which is web design and development. Along the way, I co-founded a web design conference with an even more widely respected colleague that has become one of the most respected and successful web design events in the world. This business is headquartered in Ohio—I live in Cleveland Heights with my family, and I intend to stay here until I either retire to Florida or die. Politically I’m best described as a moderate independent, though I do tend to lean a bit to the left.

As you can imagine, given my line of work, I have an opinion regarding the PROTECT IP Act which you have co-sponsored. The aims of PROTECT IP are understandable, but the methods are unacceptable. Put another way, if you wish to combat piracy and intellectual property theft, there are far better ways to go about it.

As someone with twenty years of technical experience with the Internet and nearly as many with the web—I started creating web pages in late 1993—please believe me when I say the enforcement mechanisms of the bill are deeply flawed and attack the very features of the Web that make it what it is. They are akin to making a criminal of anyone who gives directions to a park where drug trafficking takes place, regardless of whether they knew about the drug trafficking. You don’t have to be in favor of drug trafficking to oppose that.

This is not a case where tweaking a clause or two will fix it; correction in this case would mean starting from scratch. Again, the objection is not with the general intent of the bill. It is with how the bill goes about achieving those aims.

If you would like to discuss this with me further, I would be delighted to do whatever I can to help, but in any event I strongly urge you to reconsider your co-sponsorship of the PROTECT IP Act.

Thank you for your time and consideration.

Eric A. Meyer (http://meyerweb.com/)

Partner and co-founder, An Event Apart (http://aneventapart.com/)

If you agree that the PROTECT IP Act is poorly conceived, find out if your senator supports PIPA. If they do, get in touch and let them know about your opposition. If they oppose the bill, get in touch and thank them for their opposition. If their support or opposition isn’t known, get in touch and ask them to please speak out in opposition to the bill.

As others have said, postal letters are better than phone calls, which are in turn better than e-mail, which is in turn better than signing petitions. Do what you can, please. The web site you save might be your own.

I’m proud to have been a part of this effort since its inaugural launch back in 2007. It’s a major undertaking, mostly in analyzing the data and turning that into a detailed report, but it’s more than worth the time and effort. Before the Survey, we really didn’t know very much about who we were as a field of practice, and without it we wouldn’t have as clear a picture of who we are today.

There have been growing pains, of course, chief among them UCCASS, the survey software we’ve been using since the outset. Its limitations and lack of updates finally pushed us to find another platform, and we chose to move over to Polldaddy. Many thanks to the Polldaddy team for giving the survey a home and helping me figure out the best strategies for recreating the survey. (And also for putting up with my occasionally testy feature and support requests. Sorry, gang.)

Due to differences between UCCASS and Polldaddy, we ended up restructuring the survey into two distinct paths. I think this change actually speeds the process of taking the survey. I’m pretty sure just about anyone could get through it in under ten minutes.

Unsurprisingly, participation in the survey has dropped over the years; last year’s survey had a bit more than half as many respondents as the first-ever survey back in 2007. Tellingly, the actual results have been pretty consistent over the years. I’d really like to see how those results stand up to an increase of respondents, so please:

• If you haven’t taken the survey yet, kindly set aside ten minutes and do so.
• If you have taken the survey, thank you. Now, spread the word! If you could post a quick link to any mailing lists, web forums, newsgroups, or other professional communities in which you participate, it will be an enormous help. The more practitioners we have answer, the better the results.

As always, the survey will close a month after it opened; and as always, a detailed report will be published—feel free to peruse the reports from 2007 (PDF), 2008, 2009, and 2010—along with anonymized data sets for independent analysis. Together, they form a picture, but one that is still being drawn. Please help us to add the most essential detail—you!

Now available: the results from the A List Apart Survey for People Who Make Web Sites, 2010. This is the fourth industry snapshot we’ve compiled, and the story that’s emerged over that time is proving to be pretty consistent. You can get a high-level view from the Introduction, and then dive deeper into the results in the following chapters. And, as is traditional, the Addendum contains links to the full (anonymized) data set in three formats for your own analytical investigations. We’d love to see what you come up with!

Something that surprised me quite a bit was that in 2010 we got about half the number of respondents we’ve gotten in past years—not quite seventeen thousand participated in 2010 instead of just over thirty thousand as we saw in previous years. I’m not quite sure what to make of that. Is the industry shrinking? Did we not get the word out as effectively? Was it a bad time of year to run a survey? Are people getting tired of taking the survey? There’s no real way to know.

At least there weren’t any wild swings in the results, which might have indicated we’d lost some subgroups in disproportionate numbers. Whatever caused the drop in participation, it appears to have done so in an evenly-distributed fashion.

Regardless, I’d like to see higher participation next year, so if anyone has good suggestions regarding how to make that happen, please do let me know in the comments.

We plan to run the 2011 survey in the next couple of months (and I’ll post a bit more about that soon) but for now, I hope you find the 2010 results an interesting and useful look at who we are.

To be clear, when I say “Can CSS create art?” I don’t mean that in the sense of wondering if art, or artful designs, can be accomplished with CSS. I think we all know the answer there, and have known at least since the Zen Garden got rolling. What I’m doing here is using some basic CSS to generate art, using web sites as the medium. For the series I linked, I spun all of the elements on a page using transform: rotate() to see what resulted. Any time I saw something I liked, I took a screenshot. After I was done, I winnowed the shots down to the best ones.

As some of you old-schoolers will probably have recognized, I’m absolutely following in the footsteps of Joshua Davis here, and in fact my working title for this effort was “Once Upon a Browser”. I saw Josh speak years ago, and clearly remember his description of how he generated a lot of his art. My process is almost identical, albeit with a bit less automation and computational complexity.

Because this is me, I built a little commentary joke into the first images in the series. It’s not terribly subtle, but with luck one or two of you will get the same chuckle I did.

I’m already thinking about variants on this theme, so there may be more series to come. In the meantime, as I surf around I’ll stop every now and again to spin what I see. I’ll definitely mention any new additions via Twitter, and new series both there and here. And of course if you follow me on Flickr, you’ll see new pieces as they go up.

I hope you enjoy them half as much as I enjoyed creating them. And if anyone wants to use the originals as desktop wallpapers, as Tim proposed, feel free!

I just spent the last hour or so reading through the comments and, let me tell you, I can’t express how much they helped me! It is now clearly obvious to me that finishing my CS degree is the way to go. A CS degree can make me a better web developer by teaching me about algorithm design and analysis, performance issues, and just how to think like an engineer. Also, since the web changes constantly, a degree will help me embrace those changes. It will always be there for me to fall back on if the web industry doesn’t work out for me.

Thank you to everyone who contributed to the discussion, either in the comments here or elsewhere on the net. You made a positive difference in this world. Take pride in that, for it is the most important thing any of us can do.

A few days back, I got e-mail with the following questions:

…in your opinion, how useful is a computer science degree for a career in web development? I’m a second year CS major, and considering dropping out because I don’t see the value in it anymore. It’s just taking away my time from learning and doing what I love most–developing web apps. Will dropping out hurt me later on?

I chewed on it for a day or so and then ended up writing the following in response:

I wish I could give you a definitive answer, but the honest truth is that I’m conflicted. I’m not the only one, either: a recent survey of 26,000+ web professionals indicated that just over half felt their education had some relevance to what they do (http://aneventapart.com/alasurvey2009/#roe).

To use myself as an example, I got my degree (in History, as it happens), but that was before there was such a thing as a career in web development. The same is true for a lot of the people I think of as contemporary to me; that is, people about my age. Almost none of them have CS degrees, and many don’t have degrees at all. I got my job as webmaster of a respected research school because I worked there already and nobody else had ever heard of the web. I doubt very much that, were I just now exiting school and entering the market, I could do anything like that.

On the other hand, I will say that in the computer field in general, and web in particular, very few people seem to care what degree you do or don’t have. But here’s the rub: these days, it might be that having a CS degree is what gets you that first job or two.

On the other other hand, if you build some killer web apps, nobody will care about your schooling. They’ll care about your portfolio. I don’t know if that lies in front of you, of course. Maybe it does. Or maybe it’s a good idea to finish schooling so that you’ll be paper qualified for jobs that say “Requires CS degree or equivalent” if you need to seek them out.

So, to get back to your original question, “It is unless it isn’t” is about the best I can do. As someone who values education very highly and knows a degree can be an asset in job-seeking, my instinct is to tell you to finish your degree. As someone who has a lot of contact with successful people who didn’t do that, my intellect requires me to say it’s not critical.

A day past when I sent it, I still don’t feel any less torn. (And in re-reading what I wrote, I can see my indecision in the writing: scattered, whipping from one side to the other. Man, did that one ever need an editor!) I don’t really need to know what people think of what I said, but I’m really curious to know what you would advise this young person. Leave your thoughts in the comments, if you please, and I’ll make sure word of your input gets passed along to the student who wrote me. Thanks!

Addendum 12 Nov 10: please see “Degree of Influence” to see how things turned out.

The meme was the Cooks Source story, which I stumbled across relatively early in the day. I won’t recap the story here, as the original LiveJournal post by Monica Gaudio and Edward Champion’s very well-researched article do a much better job of that. The latter piece is particularly commendable if you’re new to the story, as it not only explains the genesis of the incident but also lays bare a number of other things that were discovered as the story went ballistic.

I’m not sure exactly where I first came across the story—probably a retweet of Adam Banks by a friend of mine—but at the time the meme was really just getting started. At that point there were quite a few people posting on the Cooks Source Facebook Wall to chastise the editor, and the rate of posting was accelerating. I threw in my own tweet on the topic and kept watching the Wall to see if there would be a response, if the Facebook page would be deleted, or something else. At the same time, I was seeing more and more tweets and retweets of the story, and based on just what I could see, it seemed primed to go crazy. I was rewteeted by swissmiss, who has four times as many followers as me (and way more influential followers than me), and it was hitting the feeds of more and more people I follow.

When it showed up on John Scalzi’s tweet stream, I actually got a little dizzy. This was the moment where I felt like the scientist at the beginning of a viral-apocalypse movie, staring at a monitor showing the sites of reported infection in red. Then, in a burst of tense, ominous music, the dots show up in New York City and around JFK. Game over.

I got that feeling because I knew that not only is Mr. Scalzi followed by both Neil Gaiman (1.5 million followers) and Wil Wheaton (1.7 million followers), but he is respected and therefore paid attention to by both. Furthermore, both, as net-savvy content creators like Mr. Scalzi, are exquisitely sensitive to such stories. It was only a matter of time before one of them passed the story on to their followers. And sure enough, within minutes, Neil Gaiman did so.

At that point, it seemed only a matter of time before traditional media channels took interest, and though it took a little while, many did. It literally became an international news story.

Throughout the day, I tracked the situation and tweeted about it as new developments happened. I almost couldn’t help myself; I was completely captivated by watching a meme unfold and spread in realtime. Eventually I hit on a crude measurement of the story’s reach, which I dubbed the Speed of Chastisement (SoC). This was measured by loading the Cooks Source Wall and then scrolling to the bottom of the page, down to the “Older posts” button. The time elapsed since the last of the Wall posts was the SoC. When I started looking at it, it was measurable in minutes, but as the day went on the interval dropped. At one point, it was as low as 34 seconds, and may well have dropped lower when I wasn’t looking.

I wish I could’ve automatically captured that number, say, every minute, because the timeline graph I could make with that data would be fascinating—especially if mapped against various developments, like Neil Gaiman’s retweet of John Scalzi or the time of various article publications.

One of the things I found most fascinating was how the outraged mob used Cooks Source’s own digital presence against it. I don’t actually mean all the Wall posts, which served as an emotional outlet but otherwise only indicated the story’s memetic velocity (the SoC I mentioned earlier). What people did was start new threads in the Discussions tab of Cooks Source’s own Facebook page to document the original sources of Cooks Source articles and to compile the contact information for all of the advertisers in Cooks Source. The speed at which the crowd operated was awesome in the older sense of that word as inspiring of awe, which is itself defined as power to inspire fear or reverence. As I told a friend, I was fascinated in the same way I’d be fascinated watching, from a distance, a predator hunting down its prey. Awe-struck. It was almost frightening to watch how fast people tracked down the various text and image sources, uncovering more and more evidence of bad behavior at full-bore, redlined Internet speed.

On a related point, I was very impressed by the quality of reporting in Edward Champion’s article about the story. Alone of all the articles I’ve seen (beyond the first couple of LJ posts), his laid out specific examples of repurposed content, and furthermore he had talked to people involved and gotten their perspective and to people at some of the sites and companies whose material had been re-used. Read the article, if you didn’t already follow one of the links. It is investigative journalism done far better than any reporter has yet done for any traditional, or even “new media”, news outlet.

I could write about all this for much longer, but I’m going to hold off. My day wasn’t all just observation and tweets, though. A few questions kept hovering in the back of my mind.

• What if the mob had been wrong?

  Imagine with me for a moment that a small crocheting magazine is accused of copyright violation by an author. The editor, knowing this to be false, sends a dismissive or even sarcastic letter (we’ve all done it). The author posts their side of the story and excerpts of the letter to their blog, people notice, and suddenly the Flash Mob of Righteousness is back in business.

  What then? Is it possible, once the rope is out and being tied into a noose, to put it away again?

• Did Cooks Source actually win?

  As I write this, about 24 hours after the story really blew up, the Cooks Source Facebook page has gone from 110 people who “Like This” to almost 3,400. Most of those are because in order to comment on the Wall, you have to Like the page, and a whole lot of people hit “Like”, commented, and then hit “Unlike”. Some of them are still listed because they’re still posting. Still, assume that by the time it’s all over, between people who want to keep harassing Cooks Source and people who just forgot to hit “Unlike”, they’ll have well over a thousand people listed. That’s a full order of magnitude jump in claimed like.

  Is that a measure of success? Will it, in fact, end up a net positive for Cooks Source as it tries to entice advertisers for future issues? Of course, that assumes the magazine survives the attention of lawyers from Disney, Paula Deen Enterprises, Martha Stewart Living Omnimedia, the Food Network, Sunset, National Public Radio, and so on and so on.

• What about Gene Simmons?

  A few weeks back, Gene Simmons (of KISS fame) said that anyone who illegally shares files should be “sued off the face of the earth” and that bands should be litigious about people copying their music. In response, his web site was cracked and a good deal of derision was directed his way.

  Interesting. In one case, a content creator who calls for vigorous defense of copyright is attacked for it. In another, a violator of copyright is attacked. How many of the people who Wall-bombed Cooks Source’s Facebook page were also cheering the anonymous crackers who harassed Gene Simmons? Why the disconnect?

  There are many reasons we could cite, and I think the most likely factor is that in both cases, the targets of attack were publicly arrogant and uncompromising about their positions. That, however, is absolutely no excuse. If you were outraged by Cooks Source, shouldn’t you cheer Gene Simmons’ stance? If you rolled your eyes Gene Simmons, shouldn’t you be on the side of Cooks Source?

  I imagine there are people who did one or the other of those things. But not many. The contrast says something about how we collectively view intellectual property, and it may not be something we want to face.

This isn’t the first time someone will set off an outrage swarm, and it won’t be the last. There is much to think about here, about both ourselves and the medium we inhabit.

It’s that time again: the 2010 edition of The Survey For People Who Make Websites is open and taking your input. If you’re someone who creates web sites, whether all the time or some of the time or even just occasionally, please take just a little bit of your day (as I write this, the average time-to-completion is just over 10 minutes) to let us know about you. Furthermore, please spread the word to any groups to which you belong—local SIGs, mailing lists, newsgroups, forums, message boards, and so on. I truly believe it’s important to the profession as a whole to have as many web folks as possible participate.

I was asked a little while back why we do the survey, and my answer surprised me not just for its content but also for how much passion I felt. I said:

I think it’s a vital investigation, a look into our profession that nobody else is even attempting and is… essential if we’re going to be taken at all seriously by anyone other than ourselves.

And even more vital than that, it tells us who we are, collectively speaking. We’re scattered. Many of us are solo. We don’t even know what kind of community we’ve joined. The Survey, though limited and imperfect, tells us something profound and essential about us.

That’s why I’ve wholeheartedly supported this effort from its very outset, putting in hours upon hours of thought and effort into its operation and approving the use of [funds] to pay for professional analysis. This matters.

Other professions have it easy: they require certification or degrees or membership in a professional organization before you can take part. Because of that, they can often estimate to a reasonable degree, or even count directly, how many of them there are. They can go to their membership rolls and survey a few thousand randomly picked members to find out their age, location, experience, salary, and anything else that seems interesting to know.

We who build the web don’t have that luxury. Our profession, just like the medium it serves, has no gatekeepers, no central organization, no clear boundaries. The Survey is our attempt to disambiguate ourselves.

So please, if you’re someone who makes web sites, take ten minutes to tell us about yourself. If you know people who make web sites, please point them to the survey and ask them the same. Thank you.

• Microsoft^†
• Mozilla
• Opera
• Safari^†

^†Lists more than just prefixed properties, values, and so on.

While there’s no guarantee of completeness or accuracy, these are at least what the vendors themselves provide and so we can cling to some hope of both. I was also pointed to the following third-party lists:

• Vendor-prefixed CSS Property Overview « Peter Beverloo
• qooxdoo » WebKit CSS Styles
• CSS Infos : Webkit CSS Properties
• CSS Infos : Firefox CSS Properties

If you know of great vendor-prefix lists that aren’t listed here, particularly anything from the vendors themselves, please let us know in the comments!

Somewhat if not obviously related: does anyone know of a way to add full Textile support to BBEdit 9.x? Having it be a Unix filter is fine. I know BBEdit already supports Markdown, but since Basecamp uses Textile and lots of people I work with use Basecamp, I’d like stick to one syntax rather than confuse myself trying to switch between two similar syntaxes.

…that having been the original working title for “Prefix or Posthack“, my latest article for A List Apart. (Sort of like Return of the Jedi had a working title of Blue Harvest.) In a fairly quick read, I make the case that vendor prefixes are not only good, they have the potential to be great and to deliver greater interoperability and advancement of CSS.

So far the reaction has been overwhelmingly positive, which frankly came as a bit of a surprise. The annoyance factor of prefixes is undeniable, and it’s been my experience that annoyance dramatically hardens opposition regardless of whether or not there are good reasons to oppose. I could flatter myself that the agreement is due to the Obvious Rightness of my argument, but I suspect it’s actually that I merely articulated what most people had already instinctively decided for themselves. Which isn’t a bad place to be.

Anyway, if you haven’t already, feel free to decide for yourself by reading the article—which, I feel like mentioning for no clear reason, is only the fourth piece I’ve ever written for ALA.