tags » I’ve never been a front-end girl. And even in the late 90s when client-sided programming was popular, I couldn’t enjoyed anything coming from it. The reason behind my behavior to client side computing is my lack of vision in its possible potentials. I was far from seeing them and worse by the year 2003, most of the back-end ninjas were in a similar situation as me. As xmlHttpObject became the phenomena and AJAX became the new cool kid on the block, everybody had to check its concept for a reason to stay alive.
I remember the first day I played a little bit with asynchronous requests and manipulate the DOM tree with the new content, back in the early 2005 I suppose. In a minute, I started crying from happiness and the magnificence behind the idea was so marvelous that it can even change everything I know about the existing web architecture. I asked for a while why we are not developing systems where back-end servers are only sources of raw data just like how my idea implemented into the reality with web app APIs today. Dynamically appending elements to DOM with info coming from servers and removing them were giving a lot better performances than re-requesting the full page again for minor changes - in fact even for major evolutions.
That old and junky looking JavaScript became my hero in the next few days and I decided to get into the design patterns and anything geek in the air about it. Today, JS, Adobe’s Flex and many more provides us to design better systems with less back-end connections. So why not? I believe there comes a day that back-end will become pure data and front-end will become the UI, just how it should work like.
JBF provides some new generation energy to the web. She is working on interesting stuff like increasing efficiency in data on the web and making content more machine readable. (
Made on a