ChrisH3677 said:
In it's current incarnation, Konfabulator is better than Dashboard.
1) K 1.7 has the bring all to the front (which was released before Tiger announcement but I'd reckon K had inside knowledge that function was coming which is why K 1.7 came out on Sunday). Tho, who wants to bring all their widgets to the fore anyway? You'd usually just want one - eg calculator or calendar or weather
Bringing all of them to the foreground is useful because finding one of them is too difficult unless you adopt your workflow around keeping your K widgets always visible.
IMHO, if you ever really only want one of your K widgets, Konfabulator's the wrong solution for you. But more on that later.
2) With K, I my widgets are always visible if I want, so if i lay my screen out right, i can always see the calendar or cpu processes, say, or have access to my iTunes remote. If Dashboard doesn't include the option to have widgets always on-screen, then it will be inferior to K. Obviously 12" screens don't get this value from K - but they won't from Dashboard either.
IMHO, that's the key difference between the two, which reveals the underlying design goals. Dashboard is for getting to common utility widgets fast. And, oh, it can do stuff that you might want to monitor on occasion like stock prices and a web cam ... but it's not for something you're going to be staring at all day. Konfab is designed around the principle that there are lots of little bits of information you want to have in your face 100% of the time. It's awkward to start up new widgets, or close existing widgets (especially if they are in the "float" layer, which apparently disables all interaction, at least in 1.7). They aren't aimed at "quick utilities"; they are aimed at low-overhead monitoring apps.
Now, personally, if I'm going to be monitoring CPU usage or whatever, a small, lightweight app makes about as much sense as having a fairly heavy-weight toolkit with a super-lightweight widget running inside. It really only makes sense when you have multiple such widgets to run, where the savings per-widget makes up for the resources the toolkit itself takes up.
Again, personally, I just never have such a use for it. Weather checking? Yeah, that's nice too. But running a heavy-weight toolkit for something I just want to be easy to check on (I don't need the weather always staring me in the face ... if I wanted that I'd go outside!) is a bit beyond silly.
My desktop space is precious. Keeping things there that I don't need just doesn't make sense.
So, again, for me, Dashboard is the better fit. If Konfab is a better fit for you: great! That's kinda the whole point. You pick one, or the other, or even heaven forbid use both.
3) K widgets can do almost anything because of #2 above. Dashboard will be limited by being off screen.
Dashboard widgets can do almost anything because they can get completely out of my way when I want. K will be limited by staying on screen.
K is not a resource hog. Watching the CPU processes and KCPU, Safari is using more resources than K - and I've got 9 widgets running!
Well, no crap!
K makes lots of sense if you have lots of widgets running all the time (and you actually monitor the widgets). Good for you!
I think K would be in some major trouble if it took more resources than Safari, which is a full-featured web browser which could just as easily host all those widgets itself! The whole idea of K is that those bits of information are too small to justify going through a web browser with all its overhead to get to.
However, I've got a Rev A dual-2.0GHz G5. Konfabulator is running, with nothing but the it-shipped-with-it weather widget right now. Activity Monitor shows that K is taking 1.5-2% of my CPU resources. Completely idle. That's insane, if all I want is a weather widget, or a CPU monitoring widget, etc. That's insane, if all I want is a calculator widget handy when I need it and a calendar to glance at every once in a while.
Is K a resource hog? It is if you don't use it as designed. If you just need one or two widgets, or just need them open on occasion, K is a poor solution for you.