Feeds

New style reviews

Making product reviews more useful and interactive

  • alert
  • submit to reddit

Secure remote control for conventional and virtual desktops

We’re experimenting with various new review styles. One is to compare two products, both good of their type, and look at the different purposes each is fit for – there’s an example (for Perforce and Subversion) here.

We think this makes it easier to get a feel for the products in context and moves away from the “this product is great, if you like this sort of thing” style, rather forced on you if you are looking at a single product. But, no – we won’t be doing “group reviews” with a vaguely favourable few lines on each product….

We’re also accepting vendor feedback via the blog, which gives readers a chance to comment too. For instance, Perforce takes exception to a couple of points in Tim Anderson’s review, although I don’t think they make a material difference to his overall (generally favourable) conclusions.

The comments come from Dave Robertson, director of European Operations Perforce Software: “The review says, ‘It's also true that Perforce fully supports parallel working, though unlike Subversion it does not positively encourage it.’ This isn’t correct. From day one, Perforce's inter-file branching architecture was built to encourage branching and parallel edits on files and codelines in contrast to how other contemporary SCM systems handled this. Ten years on, Subversion has come along with its own version of this idea.

“The review also stated that ‘Perforce falls in between old-style locking and Subversion's liberalism. Perforce marks working files read-only unless you check them out for edit. Multiple users can check-out the same file, but will be warned.’ This describes the default mode of working within Perforce, which is easily changed by changing one option in the product.”

Dave goes on to praise the flexibility and power of Perforce’s approach to Branching and Merging, something of which he is obviously particularly proud: “Perforce maintains all integration history, so users can easily identify pending changes to be merged between files, or select previously applied changes to be removed,” he says, “and Perforce also has the ability to merge code automatically based on user selected parameters… developers can rely on Perforce to ensure that correct changes are identified and moved between branches automatically”.

It’s an interesting area, but Tim Anderson tells me: “I didn't do a deep comparative study of the branching and merging [in both products] as that would have taken up the entire review and more”; and there are limits. If you want to know more about how Perforce works, in considerable detail, I’d suggest taking a look at Laura Wingerd’s excellent Practical Perforce - but that’s about 300 pages, a bit long for a single review.

The essential guide to IT transformation

More from The Register

next story
The Return of BSOD: Does ANYONE trust Microsoft patches?
Sysadmins, you're either fighting fires or seen as incompetents now
Munich considers dumping Linux for ... GULP ... Windows!
Give a penguinista a hug, the Outlook's not good for open source's poster child
Intel's Raspberry Pi rival Galileo can now run Windows
Behold the Internet of Things. Wintel Things
Linux Foundation says many Linux admins and engineers are certifiable
Floats exam program to help IT employers lock up talent
Microsoft cries UNINSTALL in the wake of Blue Screens of Death™
Cache crash causes contained choloric calamity
Eat up Martha! Microsoft slings handwriting recog into OneNote on Android
Freehand input on non-Windows kit for the first time
Linux kernel devs made to finger their dongles before contributing code
Two-factor auth enabled for Kernel.org repositories
prev story

Whitepapers

Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Top 10 endpoint backup mistakes
Avoid the ten endpoint backup mistakes to ensure that your critical corporate data is protected and end user productivity is improved.
Top 8 considerations to enable and simplify mobility
In this whitepaper learn how to successfully add mobile capabilities simply and cost effectively.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.