Here’s why your farmed salmon has color added to it

Here’s why your farmed salmon has color added to it:

The fact that consumers will shell out more for salmon that looks wild—even if it got that way by eating pellets in its pen—hints that people want to be eating wild salmon, but not quite badly enough to buy the real deal. If it’s price that’s keeping consumers from buying wild-caught salmon, they might want to consider saving a few bucks more and start demanding farmers cut out those expensive pigments—and sell them salmon that’s gray.

[Interesting. But I’d be surprised if it happened. Maybe if a company wanted to take on the marketing of a “new” fish and not call it salmon… and still charge nearly as much. What a mess. (I should add that assuming that none of the folks involved are lying to us, we buy wild salmon, we’re not fans of food coloring.)]

Rivers Run Free… Nation’s Biggest Dam Removal Is Done

Rivers Run Free… Nation’s Biggest Dam Removal Is Done | Gear Junkie:

Last year, 72 dams were removed across the country, including the final portion of the Glines Canyon Dam along the Elwha River in Washington, the largest dam ever removed.

American Rivers keeps track of all the dams removed across the country. In 2014, those 72 removed dams were found in 19 states.

[According to American Rivers, 15O,618 acres of riverside land was protected and 4.2 million pounds of trash were removed through their National River Cleanup program. Progress!]

Open source license usage on

Open source license usage on

Open source simply isn’t open source without a proper license. Unless you’ve explicitly told others that they can modify and reuse your work, you’ve only showed others your code; you haven’t shared it. Here at GitHub, we’re big fans of open source, so we set out to better understand how our users approached licensing their code by looking at license usage across public, non-forked repositories, in hopes of encouraging more users to share their work with others.

[snip -ed]

Share your code

If you haven’t already, we encourage you to add a LICENSE file to your project. To make things a bit easier, if you begin to create a file named LICENSE via the web interface, we’ll even provide you with a list of common license templates to choose from.

This is just the start. Look forward to a more in depth analysis over the coming weeks as to how license usage affects project success, as we delve deeper into the numbers. Of course, in the mean time, we encourage you to explore license usage on GitHub using the Licenses API.

Happy open source licensing!

[One of the many parts of software development that I truly enjoy is making easy things easier. It’s not hard to include a license in a project, but time is always at a premium and discipline is as well. When something requires even a little bit of both the chances that a large community will consistently perform those actions diminishes. Of course, even better, is when someone does it for you. Sadly, the vast majority of the code I’ve written will never see the light of day. But that’s the way it goes. We (at work) open source what we can, when we can.]