Following Greg’s recent posts on Sugar, I’m playing with running it a bit; might even try to use it as my dominant platform for a while. Some thoughts, all written from within Sugar:
- The journal is not perfect yet but is a much more useful primary interface than the stock win3.1/macOS/GNOME desktop. Would be even better if it allowed organization into tasks. (I’m told there is some work on tagging, but I prefer to think ‘tasking’ rather than ‘tagging.’ Tagging is nebulous; tasking could be tied into a GTD approach to things which would be terrific for kids.)
- conceptually, the single-window-single-app and simplified UI design choices are appealing to me, but in practice it still seems very rough- like there was a vision here, but one that was not well communicated and hence implemented very unevenly. Hopefully that will improve with time.
- You never know when you’ll miss having a clock.
- copy/paste seems to use the shelf metaphor Seth advocated for ages ago, but I can’t fully figure it out.
- For this to succeed as an actual educational tool, and not just an interesting experience in a new desktop shell, will require massive investment in – and rethinking of – virtually every single application in this new context. The included moon phase calculator is a very depressing example of this. A moon phase calculator intended for children could (for example) be used to show the sun, moon, and earth, demonstrating the relationship between the three, ideally implicitly educating the youngest kids in the nature of the solar system, and when appropriate explicitly educating older kids in the physics of light and gravity. Instead, what you get is… basically a screenshot of the moon and some meaningless numbers; not even links to explanations, much less to something interactive. Not a bad app, per se, but much work is needed (design and then coding) before it achieves its potential.
- Sugar uses trac for bug tracking. Trac is a fine app which I have recommended for small projects, but Sugar is not (or rather should not be) a small project. The sooner they get migrated to a serious bug tracking tool1 the better it will be for the project.
Two major observations I take away from this:
- It was tremendously ballsy of the original design team to make so many radical, paradigm-shifting changes to the user interface and (more importantly) to the mental interaction model. It seems important that this succeeds if we ever want to evolve our interaction models from the one we have now- if nothing else, we need to learn how to wrap our heads around different models, and learn what implications changes have for design, education, etc. You can see that this comes at a cost, though- the polish is low (in part because so much has had to be written from scratch) and the cost of porting applications is high (because you have to change them so much), so out of the box the functionality is pretty limited. The ceiling has been raised- once fully realized this will be a better tool for education than a standard OS. In the mean time the experience is not great, and hitting that high ceiling will take years.
- Despite the near total lack of apps and many rough edges I could still use this as my default desktop. Why? Because it has a web browser, and that is where so much of my life lives now.2 Among other things, this reminds me that if you’re working on a desktop shell that doesn’t treat website-applications as a peer to traditional apps (as Sugar does, albeit roughly, in the journal) you should probably rethink what you’re doing. Unfortunately, I’d also guess that the easy reliance on web apps will slow first-world developers from working on applications that work well on a third-world network.
Unfortunately, I don’t think I can use Sugar full time yet (there are a few apps that I need that won’t run under it, as I understand things) but for those of you who are slightly more flexible it seems like it might be a worthwhile project to use and get involved in.