Comment Re:Welcome to hell (Score 1) 244
TFS is a a corporate beast. Good for managers only. You know, give a try to Git, or Mercurial, or Plastic.
Comment Re:slightly one sided... (Score 1) 244
Yes, should have done that: highlight their tool instead telling so many good things about Git, don't you think?
Comment Re:Advertising disguised as history lesson. (Score 1) 244
Hey, wasn't Linus Torvalds himself who said "you must be brain dead to use CVS"?? Don't shoot the messenger!
Small companies need to be creative, share information, tell stories... I guess that's the goal of the post. If the Plastic SCM guys were Microsoft they would be on slashdot everyday, don't you think?
Submission + - An illustrated version control timeline (blogspot.com)
rocket22 writes: Most software developers are supposed to be using the latest in tech and see themselves as living on the edge of software innovation. But, are they aware of how old some of the tools they use on a daily basis are? There are teams out there developing iPad software and checking in code inside arcane CVS repositories. Aren't we in the 21th century, the age of distributed version control? The blog post goes through some of the most important version control systems on the last three decades and while it doesn't try to come up with an extremely detailed thesis, it does a good job creating a catalog of some of the most widely spread or technologically relevant SCMs.
The timeline on the post highlights the kind of cellular phones used by the time the SCMs were released, giving a good picture of how old some of them are already...
From Visual Source Safe to Git, from Clearcase to Mercurial, the post covers the weaknesses and strengths of a good number of version control systems out there.
The timeline on the post highlights the kind of cellular phones used by the time the SCMs were released, giving a good picture of how old some of them are already...
From Visual Source Safe to Git, from Clearcase to Mercurial, the post covers the weaknesses and strengths of a good number of version control systems out there.
Submission + - 15% of the internet routed through China in April (washingtontimes.com)
olsmeister writes: For 18 minutes this past April, 15% of the world's internet traffic was routed through servers in China. This includes traffic from both .gov and .mil US TLD's. Is this related to the recent hacking of gmail accounts that appear to have originated in China? Probably not ... but the moral of the story is, if you're sending sensitive information across the net, make sure it is encrypted.
Submission + - Plastic SCM joins the DVCS battle (blogspot.com)
rocket22 writes: With Git becoming the de-facto standard for Open Source projects and Mercurial user number rising while Subversion sinks, a new player enters the scene: Plastic SCM. While Git, Mercurial, Bazaar, DARCS and even Veracity (Eric Sink's attempt to renew the outdated Vault version control) are all open source, Plastic is not although it heavily relies on the Mono project. The DVCS battle broke the existing status quo on the version control world, well major products like Perforce, Subversion, Clearcase and others stayed on the top for too long.
Plastic will probably have hard times getting users since it has to fight Linus' creation but it comes fully loaded with some of the features the open source ones miss: polished graphics including an interactive branch visualization diagram and even a 3D version tree (flashy but effective). The "backend" is based on relational databases instead of binary files which is also closer to the commercial strategy. It also provides its own merge and diff tools, which add the ability to track refactored code (code moved and modified on the same file).
The product has been around for several years but a new Community Edition has been announced this week.
Plastic will probably have hard times getting users since it has to fight Linus' creation but it comes fully loaded with some of the features the open source ones miss: polished graphics including an interactive branch visualization diagram and even a 3D version tree (flashy but effective). The "backend" is based on relational databases instead of binary files which is also closer to the commercial strategy. It also provides its own merge and diff tools, which add the ability to track refactored code (code moved and modified on the same file).
The product has been around for several years but a new Community Edition has been announced this week.
Submission + - Mercurial 1.7 has been released (selenic.com)
rocket22 writes: Mercurial (Hg) the open source DVCS has just reached version 1.7. A good amount of new features available on this new release
Submission + - PlasticSCM, Windows DVCS, now free for 15 (blogspot.com)
rocket22 writes: PlasticSCM is a distributed version control system (DVCS) especially designed for Windows developers working on commercial projects. It's like a Git or Mercurial but focused mainly on Visual Studio developers, with many graphics like the "branch explorer" to track merges between different codelines. Now a new Community Edition has just been released which goal is to provide a Windows-ready DVCS for most small companies worldwide (up to 15 developers in size).
Although the primary goal is Windows, there are versions for Linux and MacOS X too.
Although the primary goal is Windows, there are versions for Linux and MacOS X too.
Submission + - Subversion scalability compared (blogspot.com)
rocket22 writes: Subversion is still the most used version control among developers worldwide. Many big teams use it and put SVN under heavy load. How does a single server handle 100 automated concurrent developers? The post unveils some of SVN weaknesses.
Submission + - 3-way merge tool to detect moved code (blogspot.com)
rocket22 writes: Merging code can be painful especially when the same piece of code has been refactored (extracted to a different method, for instance) and modified on different revisions. Something like that ends up being a manual and error prone task. But there's some movement on the "merging industry" and together with new tools to detect similarities during diff the people at Codice Software, a European start-up, just released Xmerge as the first tool able to handle moved and modified code during merge.
Submission + - Hardcore DVCS branching patterns (blogspot.com)
rocket22 writes: Distributed version control is mainstream since Git made the cut thanks to Torvalds, the community and the GitHub folks. And developers have gravitated from mainline development towards more sophisticated branching pattern that were previously considered evil. The post describes in detail the most common branching pattern used nowadays: branch per task. Welcome to the dark side, Luke.
Comment And for software engineers? (Score 1) 204
Any company doing the same for developers? Something like IDEs, build tools, profilers, version controls?
Comment Re:Mono just miss one thing (Score 1, Interesting) 570
Mono is one thing, MonoDevelop something different.
I mean, I can't understand why this guys are loosing their time building another sad IDE instead of getting mono integrated with Eclipse. I'd drop all MonoDevelop efforts tomorrow morning and put the team to work on the debugger, and then get it integrated with Eclipse or SlickEdit.
You can actually build everything from SlickEdit but you can't debug.
Mono, as a platform, is great but:
They must forget MonoDevelop
They must have a proper debugger *everywhere*
They must go *truly* multi-platform: I mean, official releases for all the linux distros plus MacOS X, and the BSDs, Solaris, HP-UX, AIX and so on. While they *stick* to Linux... they're dead.
Everything else will come...
Comment Re:Why not develop on the JVM instead? (Score 1) 570
That would be great!! But, is anyone doing that?
Comment Re:The thing is... (Score 4, Interesting) 570
Unfortunately (or maybe not) the truth is 20 years later, to write multi-platform products, the best option is still C/C++...
