Tag: usability

Intellectual dishonesty

one of the OSDN editors has a little piece on moving from desktop Linux to desktop Windows. interesting, i thought, maybe it is a piece that ventures outside the conventional wisdom of OSDN. the next 2 sentences read: I have now used Windows for an entire week. This story marks the end of that week, and I’m glad it’s over. uh-oh.
consider this gem:

First, a question: What’s up with all this “Ctrl C” and Ctrl V” copy/paste stuff? In almost all Linux programs, when I want to copy a block of text (or a graphic or whatever) I just highlight the original, then click both mouse buttons (or the middle button if I have a 3-button mouse) where I want to paste it. This is fast, easy, and takes little hand motion on my laptop keyboard. All this Ctrl key action slows me down. I don’t know about the rest of the world, but I need to work quickly if I want to earn a living, and I don’t see why Windows wants me to go through all those extra hand motions just to paste a URL into a story. Geh.

never mind that there is no global clipboard on linux that can deal with non-text content.
mr miller goes then on to complain about the security updates windows strongly suggests you install. at the same time, OSDN complains about users not applying security updates. which one is it?
“roblimo” complains about the sorry state of certain windows shareware applications. you would assume that someone using linux is well prepared to do his research and locate the best application for a job. but no, zealotry prevails, and mr miller insists on using internet explorer, only to eventually install mozilla.
it goes on like this. intellectual dishonesty, as displayed in this article, puts people on my shit list. i am sure mr miller has some interesting ideas i’d like to hear, but my crap filter will probably prevent it.
just to be clear here: i switched back to windows in 2001 after 2 years of compiling, messing with the system fun. a very nice learning experience i do not want to miss. at some point, i was getting bored with setting up the obvious stuff all over again, and thus went back to windows, where stuff just works, including my peripherals. in the meantime, i have found a nice balance between my operating system layer (strictly windows on the desktop, linux on the server) and my application stack, which is mostly open source by now.

  • Mozilla
  • Thunderbird
  • Eclipse
  • OpenOffice
  • sharpreader

In addition, i run freely available software like Trillian and Acrobat Reader. I pay for only 1 program, the excellent Mindmanager.

idiot keyboards considered harmful

i have been heaping a lot of praise on my thinkpad x31 recently. i just noticed a friggin stupid feature: there are 2 special keys right beside the arrow keys that seem to be intended to go back and forward in the browser, respectively. (never mind the stupid access ibm button, at least i don’t have a shopping or email button). these buttons are not only fluff, they are harmful. if you are editing within a web form (i bet you do that as often as i do), you just have to hit the wrong button, and your form is gone. who comes up with such “innovations”?

simplicity drives adoption

i joined meinbild.ch today after bernhard had some interesting things to say about it. bernhard argues that simplicity can drive adoption, and that simplicity may help to even the gender balance online:

And what is noticeable are 2 things: 1. It is really, really basic and lacks many features of the usual dating sites. 2. It is quite successful.

now, with its friends feature, one could imagine this service to emit FOAF somewhere. granted that’s totally against the simplicity argument, but it could be hidden at first.

Xaraya

I tested the new smartphones last night. I had to check into this site, of course, and it rendered not bad at all. I’m inclined to do a simpler, one column layout without the sidebars if I ever decide to buy one of those. I still think their GUI sucks ass (its based on tiny buttons with illogical function mapping). I’d much rather have a phone with a touch screen, but they are very bulky. So I guess I will skip this generation of mobiles. The picture is almost original size. It’s highly alarming that every mobile device is demoed with sports scores. Who gives a fuck about sports scores?


2002-11-05: Xaraya is now public. Initial reactions are very positive. I’m glad we didn’t do any forums, because forums attract scum. In other news I did an interview with internet intern, a german mass market internet rag (some 400k circulation). I talked about the reasons behind Xaraya and why Xaraya will succeed where other php cms will fail:

  • skilled developers
  • a real architecture
  • no incompetent advocates

The article should be up in 2 weeks.
2002-11-09: I opened a whoopass can’o’worms when I outlined my plans to implement workflow for Xaraya early next year. I want to start very simple (actually the work would be done for a client project) because I knew from preparing the web services talks that workflows are a very complex topic. Gary suggested I look into wfmc which is the industry standard for workflows. Very nice, but I guess implementing it would keep me busy for a year. Workflows might be a topic for oscom too. Both wyona and zope already implement some support for xml-defined workflows.
2002-11-28: I created my first WSDL file today, with the help of some tools. I’m pretty sure my WSDL is invalid. Scripting languages with their weak type systems and WSDL don’t exactly mix well. I hope to eventually enable web services to call into the APIs that Xaraya offers. At this stage, it is merely a nice idea, but I’m slowly making progress.
2003-01-25: I took the plunge, and am now running a current Xaraya snapshot again. Lots of new toys to play with 🙂

Yeah I know I have been slow with updates, but a) live has been hectic b) Xaraya is not yet very convenient for blogging.

On the bright side, comments should now be fully functional, with a nice tree view.
2003-02-12: Another one joins the MT love. Marcel is a buddy from the Xaraya PMC, and the 2 of us should really be using our own dogfood, but alas it is not there yet re: blogging comfort. One day soon, though.
2003-02-12: Xaraya Usability Recommendations is probably one of the more extensive studies about usability in the open source field. And we are not even at 1.0 yet. Kudos to Doug and Drew for this fine doc. If we follow through with this one, good things are in store for the web layman.
2003-02-21: This feed validates as RSS. I took the plunge, and fixed the RSS feed for Xaraya. Unlike postnuke, Xaraya will ship with a rich feed that makes use of the 2.0 format. We now also have SOAP support. Mike pushed a changeset that enables to call Xaraya API methods over SOAP. Here is the relevant part from the WSDL.
<wsdl:arrayType=”xsd:string[]” />
<xsd:complexType name=”wsModAPIFuncRequest”>
<xsd:sequence>
<xsd:element name=”module” type=”xsd:string” />
<xsd:element name=”func” type=”xsd:string” />
<xsd:element name=”type” type=”xsd:string” />
<xsd:element name=”args” type=”xsd:xsdl:myelement0″ />
</xsd:sequence>
</xsd:complexType>

2003-02-27: Aye, Kevin, we will work extra hard on usability.

The PN user registration process is plain silly. It is one of the things that I was hoping to see the last of in eventually moving to Xaraya. I have a suggestion for anyone working on the end-user (non-admin) aspects of the core modules. Pretend that the typical user is my mother who gets very flustered when web site processes aren’t as easy and straightforward as possible. And Mom cries when she gets flustered. Please folks … don’t make my Mom cry.

2003-04-21: congrats team.

It is my pleasure to announce the first Beta Release of Xaraya (.900). This release is the culmination of nearly a year’s worth of hard work and undying dedication to creating. All of the developers on the project have devoted many hours to reach where we are today. The first Beta release for Xaraya is intended to capture a baseline of what needs to be accomplished before the final release. This is merely another step in the long journey that began with PHP Nuke, and then PostNuke for many of us.

2003-06-25: My friend John Cox is being interviewed about Xaraya:

With the articles system combined with the dynamic data system (both written by Michel), a webmaster no longer has to wait for developers to dream up new modules. All a webmaster has to do is dream up what they want to display, and from there it’s just a matter of adding 2 templates into the system and creating a new publication type to gather the data.

I just installed Xaraya again after neglecting it for a while, and I must say, very impressive. Time to mop up the nuke market with their silly systems.
2003-06-30: Looks like everyone and his dog is converging on XML pipeline processors these days. With more powerful XSLT editors, maybe the time for these technologies to appeal to a more mainstream audience has come.

2003-07-02:

KAYWA
No anagrams found.
WYONA
AN YOW
NOWAY
NAY OW
ANY OW
YAW ON
YAW NO
WAY ON
WAY NO
XARAYA
A RAY AX
LENYA
LAY NE
LAY EN
AN LEY
AN ELY
AN LYE
ANY EL
NAY EL

2003-07-20: Xaraya goes new ways again. They now use phing, a php clone of ant, to maintain build files for the distribution. Very neat. The more standardization, the better. Apache Lenya is using ant more and more for various scripting tasks too. This nicely leverages the very good ant documentation and literature, and means you have to learn fewer concepts.
2003-08-02: Xaraya is now bitkeeper project #6 by number of change sets.
2003-11-04:

Trolling through the Bitkeeper tree on the site, looking at the change sets, the different names, the comments, it just sort of occurred to me this is beginning to look like a factory, chugging merrily along I’m noticing more and more people on the public mailing lists wanting to take the bk plunge. The collective consciousness has apparently reached a critical mass conclusion and internalized that this is the normal way of life around here. Quick rewind to 8 months ago, when most everyone (me especially) were still trying to figure out how to do a merge… You’ve come a long way, baby.Marc

I am very happy that we made the decision to establish sound processes, use bitkeeper instead of cvs, and aim for quality. It took longer than the usual crappy php project, but then again it is of much higher quality. We are now the number 3 user of bitkeeper, only surpassed by MySQL and the Linux kernel. Amazing.
2003-12-12: This post led to an avalanche. Wow, 19 months later, the repercussions are still working its way through the php cms community 🙂
2007-06-20: linux.com is now running on Xaraya, a CMS I co-founded