This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new Linux.com!

Linux.com

Re: Seriously wrong approach

Posted by: Anonymous [ip: 127.0.0.1] on December 16, 2007 06:45 PM
"The approach you are using can never work. Microsoft will make sure that nothing will ever integrate with Windows seamlessly. What you are asking the Linux community to do is to forever play catch-up with the latest obfuscated, proprietary protocol to come out of Redmond. Not only is it impossible to achieve 100% integration if you're always playing catch-up to a moving target, but also, trying to do so would mean we'd have no time to innovate."

AMEN!

"First: printers should be connected to a Linux or Unix server. Run Samba so that Windows machines can use them seamlessly. Print serving is much more advanced on Linux and Unix than on Windows - it's never necessary for every machine on the network to install a special printer driver for every different model of printer being used (though you can let them do that if they want)."

Alternatively, if you have the power to do so, you can make it mandatory that the Windows clients have the Bonjour client installed. Easy cheesy, can connect to Cups, and also works with any modern networked printer.

'If you want to "work with" Microsoft Office documents then use Microsoft Office on Microsoft Windows. Microsoft's file formats are designed, and regularly changed, so that nothing else will ever work 100%. The import facilities in OpenOffice are good enough if you want to convert a document once, and thereafter maintain it in the standardized, well-specified, OpenOffice format.'

Again, amen. Plus, I don't buy that argument that people NEED 100% compatibility with Office. Do some minor conversion on your end, save it as ODF once, and if you need to do document interchange, 99.9% of the time you'll be better off sending a PDF anyway. PDF is an interchange format. A .DOC is not. And the final reason I don't buy that argument about needing 100% compatibility is that, back when WordPerfect was king, MS obviously didn't need 100% perfect WPD support to steal the market, and ditto for Lotus 1-2-3.

"The fact that Evolution does not track every proprietary incompatibility with standards devised by Microsoft does not constitute a bug. There may be some way to get Exchange/Outlook to use standard URLs; investigate that; if there isn't, accept the fact that Microsoft spends a huge amount of money and effort designing incompatibility into its products. It really does take two to tango."

The thing I find astounding is that a KDE PR person isn't pressuring the powers-that-be to switch from proprietary Exchange to something free like Kolab ( http://www.kolab.org/ ), or isn't looking at installing Kubuntu and using the Kontact Exchange plugin, which will support Exchange 2000. Kubuntu is my distro of choice, and for KDE users, it's as wonderful as Ubuntu is for GNOME users.

And I agree with several others and add that this seemed like far too shallow an analysis and more of a bitchfest about how GNOME isn't chasing Microsoft's tail fast enough. We get enough of those from ZDNet; let's hear some real analysis.

#

Return to Integrating Ubuntu with a Windows-based network is harder than it should be