|Browsers As A Web Development Tool|
Since the beginning, browsers are performing this basic need of view source by providing enough tools. Just like other technologies on the web sphere, browsers too evolved with the pace of time and now many experts eyeing to make it a web development tool with some amazing capacities. Before discussing on the debate of browsers as a web development tool, let’s check its evolution history.
Evolution of Browser TechnologiesAs we know browsers have used as an instrument to view source. When we view source along with its rendering results, we simply learn one or two things in our coding and its debugging by experimenting with code and its tools. Therefore, browsers act as a learning tool rather than building tool. Thus, I can say that when we intended to write or test our scripts or markup in browser, we have many limitations.
Later on Google has achieved same capabilities in Chrome using its developer tools and begun a new era of offering developer tools in each modern browser. In fact, the craze of developers tools seems somewhat illogical, as we have highly advanced standalone separate IDEs to perform our writing and even testing tasks quickly and accurately. Why we should run behind the browsers like things were challenges are infinite and progress is slow?
Now, question is that should we think of visual CSS editors, accessibility auditors, or an entire FTP/SFTP client in the browsers. What about the size of source code of browsers, their performance, and their basic functionality to render code? Should we send every process to the servers to save clients and their resources? Are we heading towards miniature of browsers in tiny handsets still capable to do entire coding of a website or web application using server resources and cloud technologies?