Interesting analysis. I just finished creating a online book collaboration website. I chose to break the Wiki, Blog model to make the platform more suitable for writing novels. I have read all your thoughts carefully and can tell from first hand experience that it takes time to sell a radically different concept and 10. is the most difficult thing to achieve in sites like this. I am in a chicken-and-egg situation because of 10. Firstly, there has to be good content for ppl to come back to the site, but on the other hand I need quite a few ppl to come to the site to write the founding stories. The other major problem I have is to find out what are people thinking when they see and use the site - log files are helpful but it would have been so much better if anyone had cared to use the "Send Feedback" button. Will appreciate it if you can look and comment.
Is it really that difficult for Google? In addition to the website caches, they have the complete Deja archive at their disposal to train any kind of learning software. Plus, this problem is already solved in Gmail.
I agree it hurts when you just spent a few hours writing a blog and the first message you get is "Wow that is really nice! I will read it again. Please see my mortgate site here..."
When can we learn that the "process" behind building bridges, buildings, and other lifeless hardware doesn't apply to life or software? These are fuzzy and constantly evolving processes - boxing them into processes, steps, or rules is not the right approach.
Can't the postal authority check my mails if they want? Why should we not accept it if it happens in the net too? It is a perfectly safe thing to do for the overall good. Of course, the authority falling in the wrong hands will be too dangerous.
As a separate point, I think the future of the net lies in requiring all users to have true identity. The net need not be some sort of secret area where everyone is wearing a mask. I believe that in 5-10 years there will be no anonymousity in the internet and everyone will require to have one and only one identity - his own identity.
AJAX was there for such a long time but nobody cared to use it until Google showed the way with their Gmail and Google Maps and now everyone is writing AJAX books and creating "frameworks" around it. All the web designers were previously focusing on getting their pages browser complaint and even reach all those user who use no-frame, no-javascript, no-cookies old browsers with little screens. Google took us a step forward by being bold and re-introducing AJAX to the world. Thanks to Google, we will see users change their behaviour, browsers standardize, and lot of interesting rich applications.
Slashdot Mirror
Interesting analysis. I just finished creating a online book collaboration website. I chose to break the Wiki, Blog model to make the platform more suitable for writing novels. I have read all your thoughts carefully and can tell from first hand experience that it takes time to sell a radically different concept and 10. is the most difficult thing to achieve in sites like this. I am in a chicken-and-egg situation because of 10. Firstly, there has to be good content for ppl to come back to the site, but on the other hand I need quite a few ppl to come to the site to write the founding stories. The other major problem I have is to find out what are people thinking when they see and use the site - log files are helpful but it would have been so much better if anyone had cared to use the "Send Feedback" button. Will appreciate it if you can look and comment.
Is it really that difficult for Google? In addition to the website caches, they have the complete Deja archive at their disposal to train any kind of learning software. Plus, this problem is already solved in Gmail. I agree it hurts when you just spent a few hours writing a blog and the first message you get is "Wow that is really nice! I will read it again. Please see my mortgate site here ..."
No not XML, it is Google. People saw Gmail and Google Maps, and now AJAX is all over the news.
When can we learn that the "process" behind building bridges, buildings, and other lifeless hardware doesn't apply to life or software? These are fuzzy and constantly evolving processes - boxing them into processes, steps, or rules is not the right approach.
Can't the postal authority check my mails if they want? Why should we not accept it if it happens in the net too? It is a perfectly safe thing to do for the overall good. Of course, the authority falling in the wrong hands will be too dangerous. As a separate point, I think the future of the net lies in requiring all users to have true identity. The net need not be some sort of secret area where everyone is wearing a mask. I believe that in 5-10 years there will be no anonymousity in the internet and everyone will require to have one and only one identity - his own identity.
AJAX was there for such a long time but nobody cared to use it until Google showed the way with their Gmail and Google Maps and now everyone is writing AJAX books and creating "frameworks" around it. All the web designers were previously focusing on getting their pages browser complaint and even reach all those user who use no-frame, no-javascript, no-cookies old browsers with little screens. Google took us a step forward by being bold and re-introducing AJAX to the world. Thanks to Google, we will see users change their behaviour, browsers standardize, and lot of interesting rich applications.