Follow Slashdot stories on Twitter


Forgot your password?

Comment Re:what about git? (Score 1) 85

Why can't git be updated to just use another algorithm?

First off, Linus on the topic of SHA1 safety: (SO link, as the git mailing list links are flaky on me today)

The Linus' comment is somewhat outdated.

For the first type of collision - the inadvertent kind - a check was added to the git very long time ago. It will not let you commit, if there is a hash collision. The time-stamp is also part of the commit, and as such, the workaround is to simply wait one second and try to commit again.

Comment Re:CVS or Subversion (Score 1) 316

SVN has been working just fine for my group for a number of years. We have a total of about 35 people across 7 or 8 teams using the same set of repos and build server. We've discussed moving to git because our dev organisation use it, but if and when we do, we'll probably continue to use SVN as our front end, because git introduces complexities that most of us simply do not need in our day-to-day work. We sometimes branch but very seldom merge. (*My* job unfortunately includes the major exception to the latter case, but due to the nature of things, I'm *always* going to be stuck with doing this manually no matter what CVS we use. BTW, SVN rocks when it comes to performing reverse merges when you've committed something stupid and just need it to go away ASAP.)

We use SVN in maintaining both the huge set of docs for which we're responsible (XML plus pulls from software sources plus various other text and binary assets) plus the backend for processing them (Perl, Python, PHP, ruby, shell, XSLT, FOP, javadoc, Doxygen, heaps of Makefiles, etc.) and it does just great.

Comment Re:I've got to disagree. (Score 1) 132

For individual projects and small teams--yeah, sure. We even use some for those things.

The biggest problem with wikis is that they're flat and amorphous. The *two* biggest problems with wikis are that they're flat, amorphous, and they don't scale. The *three* biggest problems problems with wikis are that they're flat, they're amorphous, they don't scale, and they possess no intrinsic semantics. The *four* biggest problems, then--*Amongst* the biggest problems with wikis are issues such as... Wait, I'll come in again.

Amongst the greatest problems with wikis are such diverse issues as being flat, being amorphous, non-scalability, lack of intrinsic semantics, and nice red uniforms--oh, damn!

Comment Re:Empathy is for loosers (Score 1) 764

Equality is not achieved : look at salary graphs... You can come back with more SJW bashing now.

The last time I saw my salary in relation to others, I left the company considering I felt I was pulling the weight of those peers who were paid better. I did not feel wage equality between genders was an issue, equality between work produced was.

Comment Re:Dear SJW morons (Score 5, Funny) 764

There is a small software tool that developers use, and a 32-bit hexadecimal value that shows up in one dialog box defaults to the hex value "DEADBEEF". Clever, right? Also harmless and not at all intended to be offensive. But someone got offended and they made them change it.

My name is a trigger word.

Comment A timeline... (Score 4, Insightful) 764

Frat boys call each other bro, such that it becomes part of a stereotype.

Feminists start using the word as a slur to evoke the stereotype in order to ridicule anyone they perceive as too masculine.

People start using bro ironically in a totally different context.

Feminists lose their shit and call *that* "offensive".

I'm guessing what they're really upset about is their insult losing its negative connotation.

1: No code table for op: ++post