In the fast paced world of Front End Engineering, change reigns supreme. Dormant for years, the Browser Wars are back and have broken web development wide open. Led by competing vendors championing their own implementations of HTML5, CSS3, and other Web Standards, they’re unchaining us from the desktop computing environment. We’re seeing web browsers in our favorite Mobile Phones, E-Book Readers, and Tablet devices. Does your web site work with the Android Browser? On the iPad? How about the Kindle browser? IE9? Do you even know what version Google Chrome is on?
As web programmers, how do we keep up with this blistering, nauseating pace while still taking time to improve our skills? I’ll go through a set of principles and guidelines I use to simplify the world of Front End Engineering. These criteria will help you write better future-compatible flux-resistant code. They will help you evaluate new toolsets, APIs, frameworks, and even file formats and codecs. They will improve the quality of your web sites and applications.
Adding Git bash into console2 is pretty easy as you will see.
Then you will add a new tab and name it “Git Bash”. The previously mentioned target url will go in the “Shell:” field without the quotes. You can set your startup directory to whatever you like. Then hit “Ok” and give it a try.
$('head').append($('<link rel="stylesheet" type="text/css" />') .attr('href', 'http://www.somedomain.com/css/cool.css'));
var link = document.createElement('link'); link.href = 'http://www.somedomain.com/css/cool.css'; link.rel = 'stylesheet'; link.type = 'text/css'; document.getElementsByTagName('head').appendChild(link);