Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re:Netbeans ( or others ) (Score 1) 193

I love vim, but, the ability to highlight individual lines and give me specific errors,

i am not sure if i understand you, but do you know the vim command line option "-q" that allows to follow up a compilation error list, also featuring navigation? if you knew or if i misunderstood you, my apologies.

Comment Re:Sorry but ... (Score 1) 1359

Hey guy, I suggest to exchange my passport with yours (UK). I live in a country in the EU (Spain), where freedom is everywhere. I am actually tired of this freedom for everybody : freedom for thieves, freedom for inept politicians, and an absolute opposition to any kind of privacy control. Well, in fact, privacy is not a right for policemen, where I live (Barcelona - Catalonia) even videos where they fairly smash violent individuals have been leaked and broadcast once and again on TV and people has had the idea that policemen are evil!
In short : I am tired of all this whining supporting privacy at all costs. Privacy it's fine, but I prefer security and non-impunity to privacy. It's below on the scale of priorities, like preferring not starving to freedom of speech. Be realist. I don't plan doing any criminal things, so it's ok for me if police wants to spy me a little in exchange for more safety.

Comment Re:strategy (Score 1) 346

i can concede that in *concept*, D-VCS is better than C-VCS (as you put it, C-VCS is a subset of D-VCS). but when it comes to getting things to work, have non-geek developers use it, have multiplatform tools, interoperability, etc, or simply, that the company does not *need* or *want* to use a D-VCS (i.e. does not want the source code to leave *easily* the office), a popular C-VCS like svn may be the choice. also, the learning curve. i have read recently that git's has been flattened in the last year (last time i tried to learn to use it), but if it is already difficult for some developers to use svn, let alone try git (or bzr). fyi, i am using bzr as my D-VCS of choice (was much easier to use than git). i won't of course say that C-VCSs are suitable for all the projects / companies.

Comment strategy (Score 4, Informative) 346

I have migrated to svn many repos from older stuff, like SCCS and VSS. Migration strategies are important, and to decide about them you need to answer a few questions. First of all, ask yourself if git or DVCS is the best option for you, your project and your company. Just don't be led by hype. It may be that a centralized VCS like svn may be a better option. There are tools to make them perform as DVCS, like the plugins git-svn and bzr-svn. Second, ask yourself how much of the project history is needed, if any is needed at all. That may save you lots of time, disk, chaos and entropy. When migrating, it is very important to tidy up the repo. Purge unnecessary files, binaries, archives, branches, etc. I have seen people who use VCSs like a trashcan. Bad practices may sink the repository performance. After migrating, make sure users know how to use the repo and that understand the basic VCS concepts, either generic or specific for the VCS of choice. Try to remove practices and concepts from the older VCS. As you mentioned it, best practices are very important, and they are not easily found on literature. There is more I could say, but I guess by now it's ok.

Slashdot Top Deals

If God had not given us sticky tape, it would have been necessary to invent it.

Working...