thedaniel

Running `atom --safe` will start the editor with only bundled packages activated.

Do you provide an export function as well, to prevent lock in?

It says "See how they are listening to their users" on the home page. Does this imply that not using this tool or not desiring feature voting is the same as ignoring your users? That's some pretty unpleasant positioning IMO.

I dunno, we're doing OK on Google with "Atom".

yes: https://github.com/github/git-lfs/blob/master/docs/api.md

atom-shell absolutely has made the switch to io.js, that's where Atom's node comes from.

I think you're being overly literal. "The text" is obviously "the meaning" or "the object" to a baby, but it's the same idea.

And folks are apparently already hacking their in-cabin sounds to sound like higher-performance models! (cf. http://jalopnik.com/someone-hacked-their-bmw-m135i-to-sound-... )

We moved to Ruby 1.9+ quite a while ago with our patched-up Rails 2.3.

We had already backported a whole bunch of of stuff to 2.3 so hopefully the 3->3.2 transition won't be so terrible.

We don't. http://readwrite.com/2014/08/14/github-government-ben-balter...

I want to agree with the sentiment about the human side of versioning being unreliable, but when the author "pins" the argument on the fact that pinning all versions is "annoying" s/he loses me. Pinning (and vendoring) everything is the only way to know that exactly what you expect to be deployed will be deployed when you deploy it. Anything less is inappropriate for production environments.

> First, that is a low blow linking to others doing it.

I thought the same thing at first, but the users that are linked to are all big, big names that get millions of plays on Soundcloud that will never get takedowns, whether they have clearances or not. It's more like saying "why are you hassling me for my $10 unpaid fine when you don't care about these corporations' $100,000 unpaid fines" than it is about narcing on the competition.

How fundamental are we talking here? Is npm still going to be a couchapp?

It is pre-1.0, and only official builds are provided for OSX so far. That said people are having a lot of luck getting things working on disparate configurations so I am feeling optimistic about the progress of lin/win!

Yeah, no conspiracy here. Sometimes when people say they're going to have a beta to gather information and make an informed decision, they actually do it.

licecap

The download is only available for Mac today, but we are working on the Linux and Windows builds.

> an automatic language detection model that the developer has zero control over

Pull requests welcome :)

https://github.com/github/linguist

If you use the "fixes #7" syntax in a branch commit, the issues will be closed only when that branch is merged to your default branch (usually master). I realize that this is only part of what you desire, but it's a useful recent addition: https://github.com/blog/1386-closing-issues-via-commit-messa...

"But I read an outsourced rebranding that came in nicely wrapped up, even with legalese in appendix A."

I can assure you, your read is wrong. This work was done by GitHubbers collaboratively and painstakingly.

The maintenance commitment cannot be understated. If you add some kind of processing to a file format, people are going to expect it to always be there, and always work, so you're taking on an eternal renderer maintenance workload. That said, we'd love to cleverly render all sorts of formats. The limitation is the time and developer energy to do it right and keep it updated.

What browser/os? This is how it looks for me on mac chrome: http://cl.ly/image/271T2o3w1v0V

This is great - I can't wait to dig in and think about it in the context of software development.

I have a developer unit and can confirm: it's legit. I don't want to go into too much detail because of the developer agreement, but think it is best characterized as like a "useful, portable, affordable, easy to integrate kinect". I'm having a lot of fun messing around with it, though I don't have much to share yet as other work has taken precedence. SOON.

Well, that's what the post-receive URLs (https://help.github.com/articles/post-receive-hooks) are intended for, though you're right that you won't appear in the services list.

Doesn't this cover shifting the onus onto service providers?

"As of today, all new services must accept an unmodified payload over HTTP. Any service that does not will be rejected."

Or, Rails was well-marketed, had lots of 3rd party plugin components, and actually had database migrations (oh the pain of databases and models in early Django)

As I assume you're referring to the 3rd Reich, let me add that you don't even have to go back to the 30s for this - the DDR had a surveillance state courtesy of the Stasi until the wall came down.

The JS interpreter shares your preference of writing all var declarations at the top - in fact, at interpretation time they will be "hoisted" to the top of the scope. In other words:

  foo()
  var bar = 1;

is actually run as

  var bar;
  foo();
  bar = 1;