Infrequently Noted

Alex Russell on browsers, standards, and the process of progress.

Only 2 More Days!

Go! Go right now to and watch Dr. Horrible's Sing Along Blog (if you aren't already compulsively refreshing the page in the hopes that they post episode 3 a tad bit early). Joss Whedon does it again.

Fascinating Data

Note: this post is far afield of my usual discussions. In the interest of not distracting those who read this blog because I usually discuss web-oriented things, the content of the post is beyond the jump.

Via Mark Thoma, the SF Fed's briefing numbers look really odd. The inflation expectation numbers look to depend on an extreme version of the commonly held assumption that workers have lost their collective bargaining power, thereby removing the wage/price linkage that caused so much damage in the 70's. That might be good for "the economy" (as defined by what's good for bankers), but if true, it seems bad for you and me.

What it means to you and I is that our economy has a chance of beating the rap on the fundamental inability of private markets (bankers) to judge risk accurately only because some percentage of our annual incomes will be shaved off and there's nothing we can do about it. And that is the good news. Put another way, we're staring down the last of the Bush Administration's regressive taxes and we just have to take it. The well-off pay a 17%-ish percent maginal tax rate on investment income, while those in "the productive economy" (the people those stimulus checks are designed to help out) pay well above that on every additional dollar they earn. Of course, it's basic economics that if you are in a situation in which you spend more of your marginal income than you save, then any tax on consumption hits you much harder than those who can afford to save. So prices increases without attendant wage increases hurt the middle and lower classes, particularly when the price increases aren't related to "core" inflation. When "core" inflation goes up, it really starts to squeeze asset values, but non-core inflation simply implies that it costs more to buy things like food, fuel, and all of the other daily necessities. While "core" inflation seems a good metric to talk about projected long-term inflation rates and linkages and embedding, its effects aren't the ones currently being felt by Americans.

Inflation is generically decried most heartily by the wealthy because it hurts them by reducing the real interest rate on savings, i.e. it reduces the return on assets invested. But not all inflation is created equal. The current situation is laying bare the difference between the average person's concerns about non-core inflation (the price of gas) and economists concerns about asset allocation (what's the rate of return on investment?). Put tersely: the current bout of inflation is hurting the people who can least afford it and those who can afford it are using the occasion to decry policies which they personally dislike even if their relationship is tenuous to the current trouble. There seems to be a lack of proportionality at work in the public dialog which I find deeply unsettling. Where did our conception of an adversarial press corps go?

The odd take-away is that inflation isn't so bad when it's tied to increases in productive output and income for those most at risk and when those increases promote stability, a fact that the "Washington Consensus" missed time and time again in its disastrous large-scale experiments in emerging economies. If those most at risk of income shocks are insulated by very low unemployment rates and a system that allows those in trouble to keep most of their (minimal) wealth in times of trouble (employment insurance, bankruptcy laws that don't strip people of fixed assets, etc.), then inflation is a tax that hurts the rich more, who incidentally are much more able to cope with such effects.

But inflation like we're experiencing? It's of a different sort. Non-core inflation is still in-check, which is good, but headline inflation is hurting those least able to cope at a rate not seen in decades. It's the last, grandest, "fuck you" of the current administration's policies to those who need to work for a living. Logic and data suggest that voting for regressive taxes isn't in my interest, or nearly anyone else's. Why then does a party looking to cling to power field bumbling fools who stand up for regressive taxation when logic, electability concerns, and basic math skills make plain how foolish that really is?

I'm a "right tools for the job" kinda guy. John McCain's economic and fiscal policy proposals certainly are making him look like a tool, but absolutely the wrong one.

Dojo Developer Day Boston, Sept. 28-29

As Dylan just posted over on the official Dojo blog, we're having our next bi-annual Dojo Developer Day event in Boston just prior to the Ajax Experience conference.

Like previous DDD events, the first day will be somewhat contributor-oriented, and many decisions about the direction of the project are likely to get made there. The Monday event will be community focused with tutorials, presentations of new work, time to present your Dojo-based apps, and opportunities for Q&A with the developers who are hacking on the features you use every day.

Sound interesting? Sign up!

Power vs. Authority

More than a year ago I had the pleasure meeting a man by the name of Amit Green. At the time we got to talking about lots of things, and eventually his arguments helped turn the tide on making the big changes required for Dojo 0.9. As a part of of those discussions, he convinced me to read this book, which in 2007 read as part wise tome and part time-capsule from a simpler, slower time in business. Perhaps the most important thing I took away from it was the difference between power and authority. To quickly summarize, "power" is the ability to affect change while "authority" is the right to make any given decision. It's easy to see how these are different: the person actually doing the work has all the power while the person who signed off on the spec has the authority. Sometimes these things are embodied in the same person but the minute they're not you have a "management problem". The solution isn't to just assume that one person will do everything; you'll get no division of labor that way which defeats the entire point of modern economics. Instead, you have to get everyone to respect the other parties such that authorized decisions represent the interests of those with power and that those with power have some agency.

But what happens when that process breaks down? When those with power forget that they have (or should have) instigating new decisions or framing them correctly? Or when everyone on the outside assumes that those with authority are the ones who can really make something happen? I'll argue that you get the web as we know it today.

As a case study in putting your faith in the wrong idols, you can't do better than posts like this which "blame the W3C" (via Molly). Blaming the W3C for not pushing the web forward is both humorously off-target and distressingly common. I've written about this before, but fundamentally you can't blame the W3C for failing to act because it's not the W3C's job to act. An MBA should be able to tease this out a bit more effectively – any decision only requires that you have answers for five questions: why? what? how? when? who?

Answering these for pushing the web forward is straightforward, even on a simplistic level:

Figuring out "how" leads you directly to "who" in this case. The action we all want is the sole purview and responsibility of the browser vendors and they alone have the power to push the web forward. The "web standards community" has made it clear that they'll need the imprimatur of some authoritative body where agreement can be forced, but that hasn't kept the browser vendors from taking the initiative there, either. The big, open questions then center around how the "web standards community" can make enough room for renderer vendors to try out new stuff, since that's how we get new things. Demanding agreement on what to do before trying it out demonstrably doesn't work, so it's then imperative that there be a mechanism for the web to iterate prior to standardization. In fact, I'll argue that this is now the biggest reason that Paul Ellis isn't getting the improvements he wants out of the web: there's no mechanism in place by which any browser vendor can take significant risks without incurring the wrath of a swarm of WaSPs, or worse. Attempts to even begin to lay the groundwork for such a mechanism have been shot down forcefully by may folks who, like Paul, view "fixing the web" as the W3C's job.

Standards bodies are animated only by the needs of industry to reduce costs by forcing vendors to agree on things. Like Open Source, they can act as a back-stop to the monopoly-creating power of network effects by ensuring that the price of software commodities eventually does reach zero. In this context, then, the W3C's only effective function is to drive consensus when visions for how to go forward diverge or lead down proprietary ratholes. Asking the W3C for more is the fast path to continued disappointment.

The W3C is just a sail and all sails need the wind to function. You can't blame the sail for the wind not blowing.

A Lovely Box For Your Toolkit

I'm incredibly excited about the SitePen Dojo Toolbox AIR app that just launched. I've been using early versions for a couple of weeks now, and in that time it has earned a privileged place on my desktop. Being able to make local builds without delving to the command line is something that I've wanted to be able to show new Dojo users for years and this tool finally makes it easy. There's more work to do around configuring the profiles themselves, but the new tool demystifies many of the build configuration options significantly. Having a searchable API viewer available is also a godsend. Huge props to the team that put it together!

Edit: I forgot to note one of my favorite parts of the project, namely that because the Dojo build system is written in JavaScript (thanks to James Burke's awesome work), the build system in the Toolbox doesn't require Java. Instead, SitePen was able to port the few Rhino dependencies in the build tool to work with the native JavaScript engine in AIR. It's a minor thing, but it speaks to the excellent engineering behind Dojo's tooling and the power of having actual web-native technologies inside a desktop app.

Older Posts

Newer Posts