On: Bzr is dying; Emacs needs to move

[mickeyp]

Ten (edit: even five!) years ago I'd agree with you. Back then a source control system was a piece of software you used for keeping a versioned history of your work and to enable you to collaborate with coworkers or friends. It was a tool.

Now? It's A Big Deal to a lot of younger developers. It is almost totemic. If it's not Git and (ideally) Github then.. it isn't worth hacking on?

[joelthelion → mickeyp]

>Now? It's A Big Deal to a lot of younger developers. It is almost totemic. If it's not Git and (ideally) Github then.. it isn't worth hacking on?

Do you really want those guys on your project?

[sparkie → joelthelion]

I wonder if any of those guys would ever contribute to emacs anyway, unless we rewrite it in javascript.

[reddit_clone → sparkie]

You made me spill my coffee on the keyboard. It does seem Javascript people have taken over the obnoxious hipsterism from Ruby folks.

[aaronem → sparkie]

SNARK: No need to rewrite it in Javascript. Just call it "Sublime Text 5" and charge them seventy bucks a copy.

[Crito → sparkie]

If the Emacs/Guile thing ever gets off the ground properly, ECMAScript/Emacs may become a possibility.

[rbanffy → Crito]

But remember: it's not because it's possible that it's a good idea. ;-)

[Goosey → joelthelion]

Absolutely. Stigma over a (d)vcs !== (in)ability to contribute to a project.

[rodgerd → joelthelion]

Well, since they're constantly told on HN that unless they're visible on Github they aren't getting a job, why are you blaming them?

[ecspike → joelthelion]

Long answer yes with a but. They will eventually take up the mantle from devs who age out or die. We might have something totally different than Git at that point but it's not good to dismiss them either. That is how projects die.