Showing posts with label software. Show all posts
Showing posts with label software. Show all posts

Thursday, June 4, 2009

Ubiquity fun (at the Scripting Challenge)



The PSW command I told you about in the previous post was my entry for the Scripting Challenge at the Scripting and Development for the Semantic Web Workshop, which took place on Sunday, in Crete, collocated with ESWC 2009. The challenge idea is to create a < 1000 lines script which uses the Semantic Web to create real-world applications.

I couldn't go there to present it, so I created a screencast / demo to replace my live presentation:



Unfortunately I didn't win, it was the Researchers map that took the prize this year, but I got quite nice feedback (thanks everybody!) and new Twitter friends :). Also, it was very fun from one end to the other: from creating the script, to the paper describing the script, to creating the screencast (interesting experience, long live recordMyDesktop and mencoder) and getting feedback about it almost live on Twitter and Facebook, as the scripts were presented at the workshop and I was home having (late) lunch.

I'm now working on advancing the idea, to also have it a part of my MSc (that's why blogging takes a while, because MSc takes the other whiles in my life :) ).

Thursday, November 13, 2008

Google Talk has Voice Chat... NOT



As you probably all have already found out, Google has launched voice & video chat from GTalk.

Here's what a friend got when he discovered it and, excited by this great news, tried to share it with me:



q.e.d.

Sunday, September 7, 2008

Wrong operating system?



I love this world: I love the new software and technology launches, the fuss around new services and new applications, the way we use technology, the way we combine it, etc. I start thinking that I'm living the best possible worlds and sometimes I feel so surprised and somehow proud of being contemporaneous and partially part of this.

This week brought us, among so many others, Chrome (the oh-so-talked-about Chrome) and the new Picasa (namely 3) + Picasa web . Nice stuff from google, cool things to play with.
Today I wanted to install the new Picasa and, of course it is not available for Linux, yet. Not to mention that Chrome is only available on Windows. Not to mention how much did I wait for Picasa 2.7 with (finally!) upload to web albums for Linux and how thrilled I was to have it this spring.

And I could mention such a long list of applications following the same pattern...

With so many cool applications available on Windows and Mac and the application developers completely ignoring Linux users, I found myself wondering today: am I using the wrong operating system for my software needs? I mean, maybe the type of user I am, the software I need and the way I use my computer in conjunction with the web is not the stuff that a Linux user would do, or what Linux is made for. It's not about not knowing or not wanting, I can tweak stuff, I can hack my Linux system, sometimes I get too involved in trying to make a webcam work or fixing sound / network / etc drivers problems, etc but I might be too social (wtf other would I need a photo management program for?) or too "trendy" for a Linux (wtf other would I want Chrome for?)

But still, I am using Ubuntu (8.04!), the Linux for girls ;) and given its popularity I should have more!

Yeah, I know my problem is obsolete in the context of the web operating system (or whatever the name of the concept is) but still, some doubts darken my clear skies of hope: Chrome on Linux? Firefox on Linux at the same level as for other OS? Plugins?

Don't get me wrong, I love my operating system, I love its openness, I love its freeness, its ubiquity (being able to have it everywhere just the same and for the same 0 charge) but I'm wondering whether we're the right one for each other.

I understand it's all about money and business (why the hell would application developers write Linux versions of the applications when Linux OSs users are so few (supposedly) and can wait anyway since they use a free operating system and should not expect too much from life because they don't pay?) but I just wish we lived in a (more) perfect world...

Sunday, April 20, 2008

Software doesn't matter?



The kid published tonight a post in which he stated that the software doesn't matter, it's the final result that people achieve with the software that does matter and that software will not make things happen if users are not set up to so good software's main quality is not being in the users way towards their goal.

While I very much agree with the first part, there are some things I would put in a different light for the second.

Indeed, nowadays software is just a tool (like almost everything in the world, actually): no one makes software for the software, or maybe some computer scientists in some laboratory -- that's the main difference between computer science and software and that's why I love the latter. We build software to help people do something, as good as we can, as good as they can: we give our best to create the best software we can to help people take maximum advantage of their possibilities.

And now we get to the second part: is the software that does not stand in your way the best software?

On one hand:
Is your friend that never criticize you your best friend? If we look at the question with user eyes, yes, it's most of the times like that: regular users generally don't have a particular attraction to learning new things and dealing with "the damn computer" or "the stupid software". I say that the software has to have an opinion, its purpose is to show the user "the good way" into computers and to help him getting better and better every day (remember, as good as they can), even against his/her will.
Our job is to really implement "the good way", to make sure our software does not create bad user habits or doesn't cultivate them, au contraire. There are situations when we have to take risks, we have to implement the good way even if everybody will hate us for it (that sounds so socially familiar) and nobody will use the software hence we'll get no money -- like persisting in caring for web standards when users use the browser that doesn't implement them . It might pay off at one point in the future, in which case we'll take the pride (and money) of being amongst the chosen few pioneers, it might not.

On the other hand:
Building a software that just doesn't stay in the way of it's users , isn't it a little too low for an aim? Why just that when we can do more? Yes, we start with that as a basis, always, we need to sell our software, people have to love it but let's set our minds to amaze them, user just satisfaction should be at the other end of the feature list. Why not propose to make the user fall in love with the software and do things he had never done before and go places he had never gone before?  (that sounds socially familiar, again) Achieving this is a challenge, we have to take it and use it as a doorway to slip into our souls, both as users and developers, the joy of going beyond what we used to call "our limits".

Blogged with Flock