Mozilla Partners with Yahoo!

I have always thought it was odd that Mozilla received a large portion of its revenue from Google as they are competitors for browser market share. So the move to Yahoo! as a default search engine is a good choice from a business standpoint. But is it good for users? I think most would say that Yahoo it is an inferior search engine.

I personally use Startpage as my search engine of choice and there has been no mention of removing the ability to change the default search engine in Firefox. So you will still be able to set your default search back to Google if you desire. It just means Mozilla wont generate any revenue off you.

Let's Encrypt - A Free Certificate Authority

A free and open certification authority backed by Mozilla, Cisco, EFF, and others. Coming early 2015. The potential of this personally excites me as moving to SSL can be very costly and time consuming, especially for a small business. But as more and more of our lives move to services online - encryption becomes all the more important.

I must say I’m skeptical about the ease of setup as SSL is always finicky. But they are claiming all that will be needed for installation is:

$ sudo apt-get install lets-encrypt

$ lets-encrypt example.com

That’s it. Example.com would then have encryption available.

I am actually really surprised Google hasn’t supported this as they have pushed for https so much this year.

Keeping Sass Components DRY with Maps

There are times in a project where you may have variations of components that need slight adjustments. In some situations the number of modifiers, though uniform, can be quite large. As of Sass 3.3 with we have a great feature for Maps (a list of key/value pairs) that makes managing this type of scenario quite straight forward. When combined with Sass’ @each directive we can significantly cut down on the number repeating lines in our source code.

Consider the following example:


$components: (
  alpha: "icon-alpha.png", 
  beta: "icon-beta.png", 
  gamma: "icon-gamma.png",
);

@each $component, $image in $components {
  .component--#{$component} {
    background-image: url("/img/#{$image}");
  }
}

…Compiles to:


.component--alpha {
  background-image: url("/img/icon-alpha.png");
}

.component--beta {
  background-image: url("/img/icon-beta.png");
}

.component--gamma {
  background-image: url("/img/icon-gamma.png");
}

This map can of course be re-used in other places, or reconfigured for other types of properties like font-size or color.

See this example in action on Sassmeister.

Summary of Apple's iPad/Mac Event from Sixcolors

This is an excellent concise write-up of what transpired at yesterday’s Apple event.

Possibly my favorite quote from Jason Snell in this:

…In the meantime, I shall stroke my iPad mini 2 and be grateful that I have no desire to upgrade it.

Fixing Homebrew on Yosemite

After installing Yosemite on my Macbook Pro (migrating from Mavericks), I had to findle a little more than usual to get Homebrew working again.

Here are the steps I took to fix it:

  1. Delete the old Homebrew stuff:
    • Run rm -rf /usr/local/Cellar from terminal
    • It goes without saying, if you any custom stuff in this directory (which you shouldn’t). Back it up before performing this action.
  2. Re-install latest Homebrew goodness:
    • Run ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" from terminal.
  3. Fix any Homebrew issues:
    • Run brew doctor from terminal and make the changes it suggests.
  4. Profit from your newly installed brew.