Office for Mac and the larger interoperability divide between proprietary and open source communities
140916
Blog: As an industry we are terrible at working on interoperability.  The open source world should be the one to fix this.
510882
Societa' disposta a favorire l'accesso agli 'open source'
22092
Redmond makes a foray into the design-suite space with this bundle of four applications. How do they stack up, individually and together -- and should Adobe be worried?
160332
Warm, fuzzy and free, the open-source operating system is winning over both Windows and Mac users. Ready to try it? Here's what you need to know. By SeÃ¡n Captain.
458368
Despite opinions from some of the PHP community, interoperability between PHP applications isn't is such a bad state - at least According to Aaron Wormus:    The fact of the matter is that it's not such a big deal. Porting a plugin from Wordpress to Serendipity is usually trivial, and as we see more web-services based plugins (stuff like the awesome askimet) the task becomes simpler and simpler.   Interoperability is overrated, the more you think of it the more complex it gets. As you start throwing in new factors into the equation (how will this interoperate with a java/c# application) you start to develop monsters like JSR 170 which solve a lot of problems on paper, but in reality are too unwieldy to be truly useful.    He even lists out some of his "steps to interoperability" to help speed things along (like "use as much abstract code as possible" and "use services").
415412
This scenario is all too familiar to office workers who collaborate electronically on projects: E-mails get passed around with differing versions of documents-in-progress attached. Instant messages whizz by. Web sites are cited, then lost. It's often a jumbled mess, with no central online location for shared data. There must be a better way.
553129
A Win/Mac developer recently asked me what I thought about his plan to create a binary of his application and sell it to interested Linux sound and music people. He asked with some trepidation, having already received a rather critical chorus of objection from some overly enthusiastic Linux users. This man's work is excellent and his software already runs nicely under Wine.read more
126665
Bigger and brawnier isn't necessarily better for everyone. FileMaker's new desktop database adheres to the Apple division's credo that ease of installation and use is more important to its user community than whizzy new features that add bulk and complexity.
431571
Can computers get along fine without writers? Word is they just might. [Missing Link]
239311
As the proprietary world continues to devour the open-source world, one has to wonder if anyone will be left to shake up the old world.
583590
The trials and tribulations of application dependency in a virtualized, hosted world.
481653
I'm back, with a very interesting topic too!  Joel Spolsky, ex-Microsoft Manager and software engineering guru has a new essay, How Microsoft Lost the API War that is creating quite a big storm in the blogging communitiy.  Joel posits that the priests in the holy Temple of Microsoft have lost their way, because it has split into two factions, and the wrong faction is winning. One faction worships on the alter of backward compatibility, while the other is led by fervent priests who are proselytizing to raise up the new gods of .NET and Longhorn. Joel suggests that the new gods will cause the destruction of the holy Temple because Microsoft's great victories were built on the altar of keeping customers happy with backward compatibility. Furthermore the old gods of the Windows API continue to grow more grotesque and cruel with the passing of time, driving former worshipers into the arms of the friendlier gods of World Wide Web.  This story sounds extremely plausible. I must admit that i fit the profile of the developer who used to develop on the Window's API, is familiar with COM and Win32 who now develops mostly using PHP and Python. However I continue to develop and maintain Windows apps that keep our customers happy, and we still plan to develop new Windows apps. Some points:  Temple of the Blind? Firstly, Microsoft is still a compelling place to work for to people who feel that they can make a difference. The Temple continues to attract talented people with a Unix background. For example we have the recent hiring of Ward Cunningham, author of the Wiki.  Microsoft is still able to keep talented people like Raymond Chen, and others like him who continue to look after the Windows API, and Longhorn apparently will still give high priority to backward compatibility. Open sourcerers like Miguel Icaza are sufficiently attracted to the .NET vision to stake their careers on Mono. Longhorn and .NET are compelling technologies, so even if Win32 is not so cute anymore, M'soft is providing something that remains very attractive.  What i do see M'soft doing wrong is that they aren't disseminating the .NET runtime fast enough. It remains an optional install in XP Service Pack 2 for example. Also their IE dev team appears to be hog-tied due to political reasons; nevertheless IE remains good enough, particularly when I can embed IE as an activeX control, something I cannot do with Mozilla (AFAIK) - Update: I'm wrong.  Temple of the Spider?  Secondly, people don't merely use a web browser. They run the web browser in the OS.  So let me ask you, if you are using DreamWeaver or HomeSite or Photoshop or vi or emacs or Gimp, how many of you are willing to give it up for a java applet (or whatever your favorite technology is) running in your web-browser? Precisely.  Temple of the Abandoned?  Third, Joel makes the claim that developers are not developing to the Windows API. Well he could be right. But I bet a lot of them are still calling Win32.  If you are using a framework or IDE like Delphi or wxWindows (or .NET or VB) then you certainly are insulated from the Windows API, but that doesn't mean that you're not calling the Windows API all the time. I don't see Borland dropping their Windows version of Delphi at any point in time.   In fact, the fact that many developers are using some form of framework is a compelling argument for Microsoft to enhance the .NET framework to attract developers who are using other frameworks.  Today, not that many students learn x86 assembler, but that doesn't mean that Intel lost the CPU wars. Just because fewer people are learning Win32 doesn't mean Microsoft has lost the API wars, if the frameworks run predominantly on Win32.  Temple of the Lost  Joel even warns you in the beginning that "because I'm talking about big trends, I need to exaggerate and generalize". But you still get sucked in because Joel Spolsky is a first-class writer, in the same order as Philip Greenspun or Eric Raymond. That makes him so persuasive and plausible. But this is not Indiana Jones and doomed temples, but Steve Jobs and reality distortion fields.  Other opinions:  Harry Fuecks (PHP is ASP's upgrade path),  Dennis Hamilton (M'soft is just covering all bases), Robert McLaws (Joel is wrong in 7 points), Oliver Travers (the web is not good enough), One Run-time to Rule them all....
386513
A team of researchers is evaluating how Linux and Mac OS X stack up against Windows for internal use.
349743
Interoperability is the great challenge facing the open-source movement.
123174
The Open Solutions Alliance, a nonprofit group backed by a number of commercial open source vendors, released a survey on Wednesday that found interoperability is a foremost concern among open source software customers.The group, which includes CollabNet, EnterpriseDB, and others, contended in a statement that if its members overcome interoperability challenges, they stand to &quot;out-Microsoft Microsoft by offering a fully interoperable suite of business tools.&quot;&quot;We think interoperability has to be a core feature [of open source software] from the very beginning,&quot; OSA&#39;s president, Dominic Sartorio, said in an interview. &quot;Most commercial open source companies are finding a good amount of success. But how many opportunities are they leaving on the table because they&#39;re not interoperable?&quot;The OSA singled out Microsoft, as opposed to Oracle or SAP, because its member companies mostly target midmarket customers, according to Sartorio. &quot;We have one common competitor: Microsoft.&quot;OSA derived the study&#39;s findings from a series of forums it held this year in Europe and the United States. It said some 100 people attended the events.Participants cited a variety of interoperability scenarios and concerns, including single sign-on for identity management.Another involved user interface interoperability. &quot;A lot of people try to plug open source projects into an enterprise portal, and they want a unified look and feel,&quot; Sartorio said.Customers also cited cross-platform portability and data integration challenges.In addition, the study found that:-- Lower up-front cost was the most important driver for adoption of open source products, but this was tempered by concerns that spending on support and services would be greater. That feeling in turn was mitigated by a belief among respondents that open source products will become more mature over time and easier to support.-- Few customers cited the ability to customize source code as a selling point for open source applications, preferring instead that it handle their needs out of the box.Sartorio said OSA&#39;s work will continue in 2008. &quot;This is going to be an ongoing effort. We&#39;re scratching the surface here with issues customers brought up in these forums,&quot; he said.
2910
Blog: Programmers release an early but incomplete and crash-prone version of the open-source office suite for Mac OS X's native Aqua interface.
569498
New dual-core processors will make conventional software licensing models obsolete. What's next?