I consistently use duckduckgo and love it. Sometime if I think that I will get a better result from google I will simply use a bang such as !google test which then makes a request to https://encrypted.google.com/search?hl=en&q=test so your call is still encrypted.

I started to create a codepen and noticed the basic css was working. I looked further and found I had a :before added which contained content: " "; display: inline-block; which was causing the issue. Now I am hunting through my scss for the before addition to the icon class. Thank you for pushing me to create some sample code.

I once would say Node.js but now I feel that Go has more potential for several reasons: Performance, similar to C and C++ it can reach raw CPU performance. Both have promises of concurrency but Go is very well implemented with goroutines. Since Node is JavaScript and JavaScript is using the event-callback which is less than elegant. I remember Node.js being a little clunky when it comes to scaling up to a massive implementation and then I read that Go was built from the ground up to be scalable and concurrent. There are definitely downsides to both. Go does have a learning curve if you are coming from the JS side but the same goes for C and C++ developers going to the Node side. I think it really boils down to your apps needs. Use the right language and tools for the job and don't simply pigeonhole yourself into one language.

Atom.io seems to be left off of here. I would vote for that one.

I found the following site by Keith Clark helpful.