4 ms·
Word and Excel. For non technical users, you need at least these two. If Open Source is serious about the desktop, interoperability with these two application
by stcredzero 16y ago
Word and Excel. For non technical users, you need at least these two. If Open Source is serious about the desktop, interoperability with these two applications is job one.
EDIT: Some company should create a bounty for developing and implementing a process for achieving and maintaining 100% Microsoft Word compatibility for year. You'd have to put up a million dollars for something like that, but it would be worth it.
- stuaxo 16y ago100% ? There's a lot of weird stuff in those, I don't see it happening in a year - there could a lot of improvement probably. I guess some sort of automated testing that loads documents with tests in both and compares the rendering would a great step forward.
- rbanffy 16y agoInteresting idea. It should be relatively easy to make various versions of Word and Open/LibreOffice load documents and print them and then compare the bitmaps for meaningful discrepancies.
- foljs 16y agoBut they are not (serious about the Desktop). Or, to be more precise, it doesn't matter if they are or not, because OO don't have the resources needed to pull of such a thing. OpenOffice only exists ―and has semi-decent Office compatibility because it originated from thanks to corporate backing. KOffice never amounted to much, Gnumeric and Evolution withered, etc etc... The Open Source process as practiced by most projects gives very good server and programming tools, but at most nice desktop stuff.
- motters 16y agoNote that they're not complaining about Word and Excel. They're complaining about printer and scanner drivers.
- goodside 16y ago"Users have, it claims, also complained of missing functionality, a lack of usability and poor interoperability." Not mentioned by name, but it's hard to imagine anything else being the number one complaint.
- deleted 16y ago[deleted]
- ekidd 16y agoInteresting. 10 years ago, printing and scanning from Linux was just agonizing. But today, I actually find Ubuntu 10.10 almost as easy as the MacOS: I ask it to look for new printers, it gives me list of printers on the network, and I choose the one I want. Everything just works. Similarly, the Gnome scanning application is a lovely way to make PDFs. This usually surprises the Windows users, who were telling me, "Oh, you're going to have figure out where the CD is, and install some software, and you may have problems with <X>..." Now, I'm sure that there are other printers and network configurations where Ubuntu will fail. But for the most part, they've done a great job. On the other hand, I do need to keep MS Office around for marking up contracts. Open Office doesn't support Microsoft's Track Changes feature, which is a dealbreaker.
- ams6110 16y agoThe Foreign Office started migrating its servers to Linux in 2001 and since 2005 has also used open source software such as Firefox, Thunderbird and OpenOffice on its desktop systems. Even in 2005, configuring printers in Linux was painful. And a big government bureaucracy cannot be deploying every distro-du-jour to keep up with improvements... most comparable Windows shops are still running XP. One thing that I think a lot of tech folks don't appreciate is how much business generally craves reports and printing. Its just reality, utopian dreams of a "paperless office" notwithstanding. I worked at a company that built a web-based system for a government agency. One thing we did, with EVERY release and EVERY new feature was include new or updated reporting (Crystal Reports) that paralleled the new features. Developers hated working with Crystal and hated doing report work in general. But the customer LOVED it.
- Vivtek 16y agoIt'd be very difficult indeed to find and duplicate all the bugs.
- neutronicus 16y agoDon't forget Outlook/Exchange - the scheduling capabilities are awesome. I could figure out when the people I wanted to meet with were free, find out what rooms were free, invite the people I wanted to meet with (and then see whether they RSVP'd), and reserve the meeting room for a desired time slot, all through Outlook. I don't really know of an open source solution that does this quite so well.
- slashdot 16y agoWhile not open source, there are free(mium) solutions like Tungle (or doodle, etc) do this quite well. Tungle even allows you to do this with people that aren't on the same exchange server Disclosure: I work at Tungle
- rchowe 16y agoOpen source no, but Google Apps does this very well, including sending email invitations to people not also using Google Calendar.
- RockyMcNuts 16y agoAnd spend days trying to explain to people how to not screw invites up on their Blackberries and then have fits that their meeting vanished. People don't understand that they have to manage their calendars and that meeting requests are a convenience feature. They think there's a central calendar and everything gets updated automatically. Have fun when the CEO misses an important call or meeting from his calendar. This stuff is like crack, it makes people think it's easy and magical, but it's a support nightmare. http://blogs.technet.com/b/outlooking/archive/2010/03/29/some-best-practices-when-working-with-outlook-calendar.aspx http://blogs.technet.com/b/outlooking/archive/2010/03/29/som...
- neutronicus 16y agoAll I can say is that, where I worked, it was easy and magical and I never had a problem. Obviously your mileage varied.
- Zak 16y ago
- davidw 16y agoYou have to wonder, though, in a big bureaucracy, how much of the pain is due to "not 100%" compatibility, and how much is due to "this Linux thing is not what I'm used to".
- SimonPStevens 16y agoHaving worked with people trying to encourage adoption of open office I can say the main problem is compatibility. Pretty much everyone can adjust to the slightly different interface. The issue is that if you save a doc in open office and email to a customer who uses word if you've used anything beyond the basic text features there is a good chance when they open it there will be something wrong. The reverse applies too. Almost everyone I've tried open office with has eventually given up and migrated back to word primarily because they couldn't open files other people were sending them.
- _delirium 16y agoWe're on Word here and still have that problem. If you have a newer version of Word that does .docx files, you have to save as the older .doc files, because some recipients will complain that they can't open the newer ones. And if you're on the older one yourself, you have trouble opening stuff people send you. Whenever Word files go out to a distribution of more than two or so people including some external collaborators, I've always had problems. Afaict, Word on the Mac also behaves differently from Word on Windows, at least in terms of who reports back to me that they can't open a file I sent, and god help you if you try to embed media or use the reference manager. Honestly OpenOffice users give me the fewest problems, because they seem to be able to at least open anything I send them, even if the formatting is a bit mangled, while a significant percentage of Word users report back with "I couldn't open your file" or "your file seemed corrupt" or something.
- stcredzero 16y agoWe're on Word here and still have that problem. If you have a newer version of Word that does .docx files, you have to save as the older .doc files, because some recipients will complain that they can't open the newer ones. This tells me that Microsoft is actually in a vulnerable position here. If they start ramping up their rate of change to maintain lock-in they're going to inconvenience their customers even more. OpenOffice will start looking like the better alternative. Honestly OpenOffice users give me the fewest problems, because they seem to be able to at least open anything I send them, even if the formatting is a bit mangled, while a significant percentage of Word users report back with "I couldn't open your file" or "your file seemed corrupt" or something. It's not good to get egg on your face because the formatting is messed up. That looks like your fault. A corrupt file is seen as something like traffic. "Computers are tricky and stuff happens" is the usual reaction I see.
- benwerd 16y agoPart of the problem is the open source movement's increasing antipathy towards Microsoft. This is an understandable attitude to have, of course, but it doesn't win you fans when you try and acquire users outside the movement itself. For most people, computing isn't a political stance or a way of life; it's just another thing they need to use to do their job. Integrating with Active Directory to some extent, for example, shouldn't be incredibly difficult - and you would have thought that full integration with the new Office XML-based formats should be possible. But I suspect there isn't much appetite to actually do the work without substantial commercial incentive. I agree that a million dollar bounty would do the job, but then you'd have to do it again the next time a version of Office came out, and again and again. When it's so difficult to actually make money through an open source project (see LibreOffice's recent plea for 50,000 euros), that's difficult to justify. Despite what many people who run projects say, the open source business model problem is anything but solved. I know from experience that running an open source project as a business can occasionally be a soul-destroying experience (although, particularly if you're socially orientated, the good times far outweigh that). When there's a reliable way to make payroll and grow companies through producing open sourcing software, as opposed to packaging it or selling customization services, all of these problems will go away. Until then, we're - as ever - reliant on developers and teams within companies scratching an itch.
- Starmonkey 16y ago"Integrating with Active Directory to some extent, for example, shouldn't be incredibly difficult " I get confused on this one. I am trying to implement some simple software at work, and the software (not Open Source) is supposed to be LDAP compliant. The Unix admin in charge of the LDAP Directory insists that Active Directory itself isn't LDAP compliant, and that when people gear their software towards Active Directory they "break LDAP." So far, his comment is correct. The product keeps trying to pull in windows AD objects just because the server is running Windows. Frustrating. Sorry, I guess my point is, that for some of us, it gets really difficult to figure out who is breaking what in terms of compatibility. "For most people, computing isn't a political stance or a way of life; it's just another thing they need to use to do their job." 100% agreed.
- drdaeman 16y agoSorry, but even Microsoft software itself cannot provide 100% backwards-compatibility between versions. And forward-compatibility is almost non-existent.