For those who are keen to know a little history. WDW’s first issue was sent out on the 1st of July 2011 with about 15 subscribers. That’s over 4 years ago! Today, the subscriber count is around 23,400 and growing on an average of 150 a week. Each week contains about 20 links, so that’s about 4,000 awesome links that have been sent out worldwide.
To think that over 23,000 people let me email them once a week is truly astounding. This is something that I cherish and gives me the incentive to continue to make sure each and every issue of WDW is top notch.
For most developers, text editors are just as sacred as discussing the proper way to say “gif.” Sublime Text has been the heavy hitter for some time and for good reason. As an avid Sublime user I decided to see where Atom stood since I last looked; the time of early beta stages.
What follows is my experience during a period of five days using the Open Source code editor from GitHub told through the perspective of a seasoned Sublime user.
For most web developers we are knee deep in CSS on a daily basis. This can be a good or bad thing. It really depends on the state of the CSS. A well-organised codebase can be a pleasure to work with but, generally speaking, most CSS is a complete nightmare, especially on larger projects.
This is a lightweight, simple solution for adding sharing buttons to your site. Like many things, there are many ways to achieve this but the main goal of this solution is performance.
Every major social network provides an easy way to add sharing buttons to your site, but the downside of many of these is each button loads various scripts and stylesheets increasing the page weight. Generally speaking, say you wanted to have 4 sharing buttons (Twitter, Facebook, Google+ and LinkedIn) it’s more than likely you will be loading 8+ extra resources.
Using the provided solutions from the major networks is convenient, but less then ideal if performance is a main priority.