Git!
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
Personally I have little issue with Git. But I just knew that someone would come along and tell everybody the difficulty was their own fault. How nauseatingly immature that is, and how self-destructive. Trying to defend, blindly, a piece of software against a chorus of criticism, developer criticism at that, shows total disregard for the end user and I for one would never show any interest in adopting products created by people like that. Did I already mention I have no problem with Git?
-
Never tried it. No plans to try it. Using TFS at work and at least it's a step up from Subversion.
You'll never get very far if all you do is follow instructions.
I cannot agree with that. I've been using TFS for the past 6 mths, and while I found it to be great Application Development Lifecycle tool, when it comes to the source control, SVN is far superior IMHO. Initially I thought it is just a matter of getting used to the tool and I should give it a chance. After months of experience, I still reckon that common things like branching, merging, blaming, comparing revisions (changesets) or even committing is simpler and more intuitive in SVN.
-
MarkTJohnson wrote:
I could lock the file I was working on and know my changes would go in. If someone had a file I needed locked
Ew. I hated locking files. I thought it was a huge improvement to work with something like SVN that didn't require file locking, and was one of the reasons I never adopted TFS because in its early days, it required file locking. Inevitably, someone would leave a file locked at the end of the day and was nowhere to be found. Marc
Not to mention locking a whole bunch of files, and then leaving the company! I really disliked PVCS... almost as much as CMS on the VAX.
Cheers, Mike Fidler
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
We are moving to Git where I work and this thread is not giving me any warm fuzzies.
-
I totally agree. I REALLY don't understand how it has become so darn popular. It's unintuitive, user-unfriendly and even buggy... :mad: Note: If you pronounce it in French, the name couldn't be more appropriate! :doh: But because it's the hottest thing since Salma Hayek, management insists that we used it. No thanks, give me back SVN - it was easy and nice to work with, and no bugs (that I know of)
Anything that is unrelated to elephants is irrelephant
Anonymous
-----
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-----
I'd just like a chance to prove that money can't make me happy.
Me, all the timeIt is popular because the database follows you around so you can work from home, and on site without connecting back to base. You can check in stuff whenever and wherever. At the end of the day, you still have to merge it with the "master" even though there is no official "master". Yes - I like SVN and I'm sticking to it. I just get a mini-repository when I go off site.
-
It is popular because the database follows you around so you can work from home, and on site without connecting back to base. You can check in stuff whenever and wherever. At the end of the day, you still have to merge it with the "master" even though there is no official "master". Yes - I like SVN and I'm sticking to it. I just get a mini-repository when I go off site.
-
Trust me, if I didn't have to use it I wouldn't. PVCS was wonderful. I could lock the file I was working on and know my changes would go in. If someone had a file I needed locked then I knew I could work on some other item in my queue but we wouldn't be stepping on each other's code.
MarkTJohnson wrote:
I could lock the file I was working on and know my changes would go in. If someone had a file I needed locked then I knew I could work on some other item in my queue but we wouldn't be stepping on each other's code.
If you have that problem except very rarely then it isn't a problem with the source control system. It is a problem with the design, implementation and/or the way tasks are allocated.
-
Branching is evil and should be avoided. It's a sign of a flawed process.
You'll never get very far if all you do is follow instructions.
PIEBALDconsult wrote:
Branching is evil and should be avoided. It's a sign of a flawed process.
The fact that you don't like it and that you claim that you deliver perfect code into production doesn't mean that the rest of the world doesn't need it nor that they shouldn't have it.
-
PIEBALDconsult wrote:
Branching is evil and should be avoided. It's a sign of a flawed process.
Why? I'm on the fence (having seen the usefulness of it in Git), but want to know your reasons. Marc
-
Well, they want back to the first feature of source control : backup ! I definitely need to write that article about it...
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
-
No, but if you do, you'd better understand how it works... Decentralised configuration management systems are not trivial (centralised neither, but state-of-the-art now). Plus if you do not need the decentralized way, you may use it as a plain normal centralized version as well.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
Rage wrote:
Decentralised configuration management systems...
Presumably that was a misstatement.
Rage wrote:
Plus if you do not need the decentralized way, you may use it as a plain normal centralized version as well.
Doesn't alter the fact that is missing a primary feature for anything above a small company - that of management of multiple products where there are non-trivial code dependencies between them.
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
The only time I used Git I had to type like 10 commands to be sure that I got the right branch, this coupled with the lack of a fully functioning GUI made me switch to TFS.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
GIT is a great tool… in the same way that an advanced CNC milling machine is a great tool. If you’re working in a very specialized environment, with highly skilled craftspeople that are well-trained and understand how to properly use – and what the dangers are – of such a tool, then it is the appropriate tool for that environment. That environment is most likely producing specialized items; prototypes, one-off’s, uniquely difficult items to fabricate, or have other special needs (the machine shop at NASA’s Jet Propulsion Laboratory comes to mind). I’ll admit, a CNC milling machine is pretty cool… I’ve used (and accidently abused) them. But when my task was to quickly drill a hole, I didn’t want to waste time trying to set up that complex machine when a simple drill press – or even hand drill – would do the job more quickly and safely. In fact, if you need to quickly and safely attach part A to part B, you don’t want a CNC milling machine, you want a power screwdriver; maybe one with torque settings, speed control, and a few other simple, self-obvious features. It’s going to let you focus on your job of attaching the parts together and moving on to the next task. Something like Subversion or the myriad of other source control systems that aren’t so cool but do their job of managing source, and allow me, as a developer, to intuitively check out, update, merge, diff, and check in source code. So if you’re developing something specialized, like the Linux kernel, or have a relatively small team of highly distributed people whom you can afford to train (and pay accordingly), then by all means you should consider GIT. That is the environment and skill level the tool was developed for. But if your focus on writing software, with teams of developers at a various skill levels, and you want them to focus their time and effort on developing the software business solutions that make your company money, then GIT is most likely not the appropriate solution, no matter how “cool” folks say it is. BTW, we are a small, start-up, who hastily chose GIT because “everyone is going to it”. After a year, no one in the organization is comfortable with it, most of the developers don’t trust it because we have all managed to destroy work by doing “what seemed intuitive”, and it's a decision we all regret.
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
I'm using Git with git flow (http://danielkummer.github.io/git-flow-cheatsheet/[^]) and i love it ...
gzo
-
Oh Jeez, how do I hate thee? Let me count the ways. 93. There are 93 different ways in which I hate GIT! I have to use the bloody thing and I'm not sure if I'm pointing to the right repo or not. Elephants! :confused: :sigh: :mad: :wtf: :beer:
Making git easy... http://gitblit.com/[^] http://code.google.com/p/tortoisegit/[^]
-
I'm working with git as an extension to VS's Team Explorer (VS 2012/2013) and had no problem so far (4 months)...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
As far as I knew, VS Team Server Explorer shipped with version control (Last version I had success with was 2010, 2012 didn't play nice with the rest of the team's setup so I threw it out.) From what I've read about GIT, it seemed really unfriendly. The interfaces in VSTS were UI, web link, and command, I thought GIT was console command only.
-
-
Rage wrote:
Decentralised configuration management systems...
Presumably that was a misstatement.
Rage wrote:
Plus if you do not need the decentralized way, you may use it as a plain normal centralized version as well.
Doesn't alter the fact that is missing a primary feature for anything above a small company - that of management of multiple products where there are non-trivial code dependencies between them.
jschell wrote:
Presumably that was a misstatement.
How that ? No, dfinitely Distributed/Decentralised Configuration Management System.
jschell wrote:
here there are non-trivial code dependencies between them
Define "non trivial" ? DCMS can do everything what a normal CMS can do, so either what you are trying to achieve is not feasible with centralised configuration management, or your code structure was not made up properly.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
-
I'm using Git with git flow (http://danielkummer.github.io/git-flow-cheatsheet/[^]) and i love it ...
gzo
-
jschell wrote:
Presumably that was a misstatement.
How that ? No, dfinitely Distributed/Decentralised Configuration Management System.
jschell wrote:
here there are non-trivial code dependencies between them
Define "non trivial" ? DCMS can do everything what a normal CMS can do, so either what you are trying to achieve is not feasible with centralised configuration management, or your code structure was not made up properly.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
Rage wrote:
No, dfinitely Distributed/Decentralised Configuration Management System.
Because that isn't what Git is. http://en.wikipedia.org/wiki/Configuration_management#Overview[^]
Rage wrote:
Define "non trivial" ? DCMS can do everything what a normal CMS...
If we are talking about Git then it does not have a mechanism for dealing with independent deliverables which share code (not other deliverables) because each repository is optimized for dealing with a single deliverable. This works well for open source internet projects. It doesn't work for a company with different product lines because the end up kludging solutions either with multiple repositories or a single repository. Other source control systems do.
