Why it took X-Wrt to make a decent webif for OpenWrt

The X-Wrt project. and specifically webif^2, has been a phenomenal success. For those unfamaliar, webif^2 is the next generation webif we're developing for OpenWrt. Already its made OpenWrt accessible to a whole new class of users.

Why has there not been a better webif before now?

One might wonder why a better webif has never been developed for OpenWrt. Why did it take an external project to extend OpenWrt in such a seemingly obvious way? Couldn't this work have been done from within the OpenWrt project? The answers lie in a deep-seated difference in development philosophies, and perhaps also in an elitist attitude by those who don't themselves use the webif (and therefore consider all who do somehow inferior to themselves).

Deprecating code without offering a replacement
..or.. you know, *I* could do it better

For at least a year OpenWrt's default spartan webif has been abandoned. New contributions to it have met with resistance in the forms of claims that this entire webif will be thrown out 'soon' as part of a massive rewrite. Of course, this rewrite never began, and now it seems less necessary than ever. This is typical of OpenWrt though, they like to do rewrites, necessary or not, because they want to achieve the most perfect product they can, without concern of delivery schedules or other more practical issues. Unfortunately, when developers deprecate code without actually writing new code, the end effect is nothing gets done.

Elitism
..or.. you lame webif users

A big problem of many young geeks is that they have an elitist attitude. The lower the level at which you write code or use the system the more 'elite' you are and the more 'lame' those who utilize higher level systems are. As a low-level programmer myself, I once held this attitude, but grew out of it as I matured to realize the world is about getting things done, not proving how smart you are.

For a long time now people who requested a better webif or developed for the webif have been ridiculed and thought of as inferior because they actually 'have' to use a webif. Many users who are perfectly competent at the command line prefer a webif, and there is no doubt that it is quicker to learn a graphical interface than a command line interface. Despite this, there has been no acceptance given to these 'lamers' who want ease of use in the form of a webif. You'll still see people qualifying any comment about a webif with things like "my friend would like a webif" or "I just don't have time right now, that's the only reason I'm using a webif".

People need not make excuses for using a webif. The fundamental direction ANY technology should take is that it should be made easier to use and more accessible wherever possible. To intentionally keep a system harder to use as an attempt to prove some sort of eliteness is just childish.

X-Wrt to the rescue

I wish that 'traditional' OpenWrt developers and users would read this statement and think, "oh, yea, what AM I trying to prove with this unproductive attitude", and then change their ways. But, that is not likely to happen. Instead, this statement will be seen as an attack of some sort, even though its not at all.

Never fear, X-Wrt is here to give users solutions.

X-Wrt Blog

Welcome to the X-Wrt blog of Jeremy Collake. The intention of this blog is simply to provide a place to report on the latest thoughts and developments regarding embedded firmwares. For those unfamiliar with X-Wrt, see here.

Whether or not I actually utilize this blog remains to be seen, but for now, here it is.