Mozilla introduces Rec Room

Not a bad looking toolchain for spinning up your web development projects. Definitely something to keep in mind or keep an eye on.

Rec Room is a Node.js utility belt you can wear to build client side web apps. It includes:

Brick to add components like appbars and buttons to your UI.
Ember for your app’s controllers, models, and views.
Handlebars to write your app’s templates.
Grunt to run the tasks for your app, including building for production.
I18n.js to localize your app.
Mocha to test your app.
Stylus to write your CSS.
Yeoman to scaffold new code for your app’s models and templates.

CloudFlare bringing SSL to Free Accounts

Should be rolling out in the fall. Can’t wait! It’s also interesting to hear that Google will be rewarding HTTPS in search rankings.

First, Google just announced that they will begin taking into account whether a site supports HTTPS connections in their ranking algorithm. This means that if you care about SEO then ensuring your site supports HTTPS should be a top priority. Kudos to Google to giving webmasters a big incentive to add SSL to their sites.

@aol.com is one pricey email account

I wonder how many of those subscribers continue paying just keep their email address and how many still use dial-up.

But as always, the most amazing thing about AOL’s business is the thing that drives AOL’s business: Millions of people, who started paying the company a monthly fee for Internet access more than a decade ago, who continue to pay the company a monthly fee for Internet access, even though they likely aren’t getting Internet access from AOL anymore.

Swift Benchmarks

Jesse Squires:

When Apple introduced Swift, we were assured safety, clarity, modernity, and speed. It is clear to me that they have delivered and are continuing to deliver on these promises. The refinements and enhancements made over the past few months have been absolutely great. I think Swift is coming along quite nicely and I am more excited than ever for the next beta.

An in-depth look at that Netflix-Comcast deal

Dan Rayburn breaks it down with some context and history and gets right to the point.

The reason for the poor quality streaming is that Cogent refuses to pay Comcast to add more capacity, even though Cogent is taking Netflix’s money for the service. Cogent is charging Netflix for a service it can’t deliver.

So, the deal with Comcast may not be as bad as it seems at first glance.

Comcast conquers Netflix

From the Wall Street Journal:

Netflix Inc. has agreed to pay Comcast Corp. to ensure Netflix movies and TV shows stream smoothly to Comcast customers, a landmark agreement that could set a precedent for Netflix’s dealings with other broadband providers, people familiar with the situation said.

This sets a dangerous precedent, but I doubt Netflix had any alternatives based on this:

Netflix Chief Executive Reed Hastings decided to strike the deal after Netflix saw a deterioration in streaming speeds for Comcast subscribers. According to Netflix data published in January, the average speeds of Netflix’s prime-time streams to Comcast subscribers had dropped 27% since October. Mr. Hastings didn’t want streaming speeds to deteriorate further and become a bigger issue for customers, the people said.