Need good source control [closed] - version-control

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I am working on my C programming skills. I decided to run Ubunutu Linux and use code::blocks as my IDE. Now, I need a good source control.
Something that's easy for a beginner to administer (I want to concentrate on coding not managing a server)
Free
Hopefully has a plugin that integrates well with code::blocks
I plan to use source control for my own use. I want to be able to undo my changes if I make too many mistakes. I also want to be able to revert back to an old version and do side-by-side comparisons.
Maybe one day, my buddy and I could work on some code together (from different locations), but this is not a major concern at this time.
What works for me?

You want Mercurial or Git. I personally prefer Mercurial.

Subversion is still very popular and stable. It's centralized though, which these days is considered "the old way." (I've heard people say "Git is to SVN what BitTorrent is to FTP.")
Git is pretty much the in thing right now. In my opinion it has a higher learning curve, but its adoption by the open-source community is widespread.
Mercurial is a great DVCS and, in my opinion, doesn't get enough attention. Great commercial products are built on top of it, though, so growing your project to a commercial system is pretty smooth.
There are others.

Related

Which one is used more by IT companies, NetBeans Or Eclipse? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm new to Java. I took an introductory course where I was using NetBeans, but I noticed that some of my classmates were using Eclipse. From what I've understood, Eclipse is the popular IDE among IT companies.
My question is, as a new programmer, should I stay with NetBeans or switch to Eclipse?
You forgot one more: IntelliJ.
They are all different and there is no single "best one", for example each has a feature that another doesn't.
My personal remarks:
Eclipse is probably the most open. It's very actively developed. It was the de facto standard at all 4 companies I worked for so far. Eclipse is completely free.
IntelliJ is kind of intelligent. It's really interesting to use, but not all features are available in the community edition. I evaluated it because somebody claimed that a study shows that it makes you about 10% more productive but I haven't seen the study itself. I think IntelliJ is awesome but I'm so used to Eclipse it's really hard to switch.
Unfortunately I've never even seen NetBeans.
Considering these points, Eclipse seems the safest choice, due to its popularity at my past workplaces and open and free nature. But your mileage may vary.
Just keep in mind that Eclipse/NetBeans/IntelliJ whatever are just tools. It doesn't matter whichever you choose, the most important thing is that you get coding, and code well. Use whichever makes you the most productive.
Honestly, I think both are equally prevalent. Once you learn one, it is not a huge deal to switch to the other. Those with whom I work have their own preferences, and the company does not have a preference - nor do the contracting companies that we work with. To each his own seems to be pretty standard policy. That being said, in my experience the IDE choice has sometimes been defined by the problem at hand (ease of use, different plugins for particular purposes, etc.).
Bottom line - learn both. It isn't that hard to do and you will probably use both eventually anyway.

What is your best experience for Emacs source code navigation? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have a big project with many .c and .h files to navigate. What tool do you have the best experience?
I searched online and found users recommend etags, global, and ECB. I just wonder which one is best for my case so that I can stick with it. Thanks.
I think etags or ctags are easy to use. Many open source projects come with make rules to generate the databases for these type. For C++, ebrowse is better. Personally, I like to use a project bundled with emacs. If you download a 3rd party app, you will have to re-compile whenever you upgrade, and often there is more integration work. At least if you start with etags and ctags, you can find they don't have the needed features and then investigate some of the 3rd party eLISP packages.
I have made some assumptions.
You use *nix.
You use Gnu emacs.
Something else may be better with XEmacs and/or on Windows and OSx.
Apparently, global fits my criteria; but I have never used it personally. I have tried to get CEDET working and it is very difficult. It might be easier if your distro comes with a package (.deb, .rpm, etc) for something like CEDET.

Is there any reason to use Dev-C++? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Dev-C++ was one of the first IDEs that I got my hand on long ago. To me, Dev-C++ was a small software that can be downloaded and I could quickly do academic assignments with it.
In my college, people have been suggesting Dev-C++ for a quick download and just do the homework, for a few generations now. I recalled I used to have some problems with Dev-C++, mainly not understanding what exactly are mingw, different dependencies, different compilers, and all the complicated stuff.
When I tried to go for bigger projects, I always have the trouble of getting help. Other online helps seem to favor Visual Studio a lot more. For veteran developers who understand compilers and how things go around in software development, this may not be so difficult. But for people who are new to learning programming, is Dev-C++ a reasonable choice? Or should they not use Dev-C++ at all? Will the end justify the mean in the long run?
It's my understanding that Dev-C++ hasn't been supported for a long time and accepts a lot of bad code which it should reject, and it's not recommended simply because it's low quality compared to Visual Studio. Dev-C++ was my first C++ development environment too, and I wouldn't recommend it. VS also has one hell of a debugger, and some strong online reference material, not to mention all the other fun features of having a proper IDE. Visual Studio Express is free for everyone, even the current version, and whilst it's not quite as powerful as the commercial versions, it's still far superior in quality to Dev-C++.
All you have to do is look at the supported versions of Windows. Their latest non-beta version doesn't even list XP as supported.

best distributed version control for a small group project on windows? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
whats the best distributed version control for a group project of 2 people coding on windows?
Probably Mercurial. It is known to support Windows well.
Git would be my personal preference, simply because it is somewhat more powerful than Mercurial, and its recent Windows support is good, but it will probably never be a 1st class Windows "citizen".
+1 for Mercurial, with TortoiseHg as GUI: http://tortoisehg.bitbucket.io/
If you are going with git, check out TortoiseGit here: https://tortoisegit.org/
You can also use Mercurial for distributed development. It has a per-project repository structure and fits good to your needs.
Git, mercurial and bazaar are the new boys on the distributed version control scene, but all of them are mainly used in a *nix environment. Git is particurlarly popular - it has big backing since Linus Torvalds invented it.
For a team of two working on Windows I see: small budget, limited specialization. So you may wantr to consider one of the standard workhorses: CVS or SVN.
Although I personally would choose mercurial, I would recommend SVN to you: many companies offer free hosted SVN for your team size.
Cheers!
I am particularly fond of SVN as it scales nicely from one person to large teams. You can also check out Git which is becoming quite popular.
Believe it or not VSS is still around and used for many projects (especially if its internal to a network) but I would not recommend it, unless you want to use Microsoft TFS (Team Foundation Server), but that will cost you some money to setup.
I'm voting for Git. I'm absolutely in love with it. Its GUI support is meh, but I find myself not missing one ever. I do use GITK often to graphically view branches.
Git has a very clean directory structure with all source control meta data in one folder. Merging and Branching is very nice, as is the "cherry-pick" option.

Is there any cushycms alternative? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I need a free very simple CMS which i can host on my own server just like Cushy CMS www.cushycms.com. is there any ?
I recently wrote an alternative to CushyCMS because I wanted the open source community to have a free alternative.
Mechedit is an open source CushyCMS like applciation. Runs on PHP5 only though.
Orbis CMS is another open source alternative to CushyCMS. It's built on the same pricinples (simplicity, ease-of-use) and features a stylish interface, but is self-hosted and free.
SnappySnippets is a free and simple alternative; it is highly customizable and has a desktop interface that your clients will find easy to use. It is hosted so that you don't have to install anything
There are many questions like this on Stackover flow
for example:
link text
Just search for CMS
Good question which I was asking myself recently. This is a neglected corner of the CMS landscape. However, I did find:
this rather detailed and intelligent summary list:
http://www.matthijskamstra.nl/blog/index.php/2011/02/16/lightweight-cms-for-simple-projects/
a briefer but recently updated list of 40 lightweight CMSs http://www.abcphp.com/out/top-40-free-simple-lightweight-cms-|-vivalogo-resources/
Two other lists, both from 2012 and neither suggesting much examination of the products:
http://webdesignledger.com/tools/10-simple-and-light-weight-cms-solutions
http://speckyboy.com/2010/07/19/14-light-and-east-to-use-open-source-content-management-systems/
In case you're wondering, the project I was looking at using one of these for got a little more complicated and I ended up going to a more heavyweight system, with a simplified interface on top of it.
There's a lesson there. Many systems that will cope with complex needs (Drupal, MODX etc) can still be installed pretty quickly, and your users' needs are only going to grow more complex over time.
That said, I'd still like to think lightweight systems have their place. Let us know what you chose.