Web Two Point Oh So Frustrating
31st of January, 2006
The term web 2.0 has become so cliche that people hating it because it’s cliche has become cliche. That’s why I’ve avoided talking about it. I was just so sick of seeing the phrase ‘web 2.0′ displayed on my screen, whether it was talking about it’s greatness, trying to tell me what it really means or just shooting it down as though it killed their own mother. It was the quickest rise and fall of a buzz word in the history of buzz words rising and falling.
What frustrates me the most isn’t the word, it’s what it might be referring to. It feels like I learnt PHP on the exact day that it was superseded by Ruby on Rails. That, and I ignored Javascript. I didn’t just ignore it either, I didn’t like it and for no good reason. It annoyed me that I had finally learnt something that made me feel like I was inline with internet technology and then the next day I was a complete two or three languages behind.
I want to know if the people at Flickr and 37 Signals feel like they are on the absolute bleeding edge of internet technology? Do they go to work each day with the peace of mind they don’t need to learn anything new to keep up. But really, how does anyone keep up at all? If I start learning Ruby today by the time I’m done there will be something new and my knowledge will be useless. I want to know if Ruby is the future. I just want things to settle down for a little while, let the server-side language boom plateau for a little while.
All the javascript effects aren’t even produced by new technology, it’s just plain old javascript used in a way that it never has been before.
When the E-Mail section of Saturday’s Weekend Shopper starts talking about ‘web 2.0′ you know that it’s old news.
If you make a website today that has refreshing pages you’re using old technology. You’re using the industry standard that’s used by the huge majority of internet programmers, but it’s still old. The trick is to be one step ahead the trends but that takes guess work.
So here’s my guess, Scalable Vector Graphics (SVG) are the future. Once browser’s start supporting the SVG standard the internet will be in it’s ideal place. Pages, including pages filled with large amounts of graphics will barely ever weigh more than 1 or 2kb. As internet connections get faster and page sizes get tiny, page refreshing will become irrelevant because it will be closer to instant than a page without refreshing using AJAX. Screen resolution, browser window width and operating system will also become irrelevant as everything will scale perfectly whether on dual 30″ LCDs, a 14″ laptop, 3.5″ PDA or 1.5″ Mobile phone screen. And because of pages only being text, everything will be more accessible than ever.
It will be SVG for the client-side anyway, it will sort of become the new javascript but it will be so much more important. Images will finally be dynamic. What’s used on the server side I don’t think will matter. Because all that will be getting parsed is text everything will be ligthning fast and the Rails framework won’t be required to perform effects and asynchronous calls. I’ve also read that PHP is faster than Ruby on Rails. I don’t think it will matter which one is used on the server as long as it’s not ASP.






