I must be unique then. Fine with me.

Iff a project is populated with developers sharing a common network (even via ssh) I would not use a DVCS; not if it include all the *pain* git introduces. I would just stick with, for example, svn. Iff the developers do *not* share a common network I would pick git and live with its bloatness. In that case all the git pain at least has an upside.

@spongessuck the problem is that the regression tests themselves can be "broken", i.e. only testing a small subset of what should have been tested or being plain broken. In the end things will broken all over the place and the need for reverted commits will not go away.

Continous integration is no silver bullet to ensure that "broken" code isn't merged into a release branch. Test coverge will never be 100%.

Still. Git hurts certain projects as much as it helps. I have been in projects which spent as much as 25% of its time on git related issues and gotchas. For them git was the wrong choice.

Git is too versatile. Too complex. It hurts as much as it helps. I think we can do better if we keep things simple.

Maybe special frontends on top of git implementing different workflows. A few and limited set of commands for each.

Got it at EUC 2013 if I remember correctly.

http://erlang-factory.com/conferenc...

Ctrl-z, kill %1

Less is more

I prefer languages with as *few* concepts as possible. I vote for Erlang and Scheme.

Devrant takes lossy image compression to new levels of fuzziness.

Note to self: remember that

It is just a DAG of objects they say. A can of worms? I see a lot of wasted git activity in my vicinity. Waste of bloody time.

Poll. Always.

Instead of http://www.workmanlayout.com/blog/ or http://kaufmann.no/roland/dvorak/

6p is a tad too large IMHO. The 5X is cheap and you have no need of the extra punch the 6p provides anyway. My 5 cents.

Nexus. No vendor bloat. Less fluff. No wait for Nougat.

It is obviously a crime to use tabs in code. Untabify Me.