An anonymous reader writes "I've been working on a financial application which I've decided to release to the public. I want to make some money from the application, though I certainly don't expect to become a millionaire. The problem is that I'd like nothing better than to open-source it. There are many aspects of the application that I don't have time to refine, and other developers could definitely improve upon my work. However, I don't know how I earn money from something once I've made it open source. How have you dealt with trying to turn a reasonable profit on your work while remaining open-sourced?"

MarcoF brings us his take on how to cultivate interest in open-source software to casual users who aren't interested in or necessarily aware of its existence. Many people simply have trouble leaving their comfort zone of older proprietary software; what's the best way to get them to look at an open-source alternative? "Since most people would rather die than write or study software source code, it is actually counterproductive to promote software 'because you can modify it yourself and be part of its community'. Look for really practical advantages which can be enjoyed every day by the person you want to convince. Start from the actual deep passions, beliefs, interests and practical needs of the people in front of you and go backwards from there, delaying the apparition of terms like 'source code', 'the four software freedoms', GPL, Gnu, Linux, etc."

mudimba writes "Apple and Twentieth Century Fox are about to announce a deal that will allow users to rent Fox movies over iTunes. The deal will allow people to download movies that will only play for a limited amount of time. 'Pali Research analyst Stacey Widlitz said the deal follows a trend of Hollywood studios selling directly to consumers and cutting out the middleman. "It's just a sign the studios feel ... that another distribution channel is where they are choosing to go, and incrementally it hurts Blockbuster and Netflix," Widlitz said.'"

nil0lab writes "In a case of 20/20 hindsight, Princeton DARPA Grand Challenge team member Bryan Cattle reflects on how their code failed to forget obstacles it had passed. It was written in Microsoft's C#, which isn't supposed to let you have memory leaks. 'We kept noticing that the computer would begin to bog down after extended periods of driving. This problem was pernicious because it only showed up after 40 minutes to an hour of driving around and collecting obstacles. The computer performance would just gradually slow down until the car just simply stopped responding, usually with the gas pedal down, and would just drive off into the bush until we pulled the plug. We looked through the code on paper, literally line by line, and just couldn't for the life of us imagine what the problem was.'"

nowhere.elysium writes "Symbian has suggested that Google is not experienced enough or capable of fully developing a workable mobile platform. Symbian's vice president, John Forsyth inferred that Google's interest in the field will also wane due to it being 'deeply unsexy', and that development is not likely for such a platform because "You have [...] a lot of zeroes in your sales figures before a developer gets out of bed." In the same series of statements, Linux is likened to the common cold: "About every three months this year there has been a mobile Linux initiative of some sort launched. It's a bit like the common cold. It keeps coming round and then we go back to business.""

jg21 writes "It is probably coincidental, but two responses to OpenSocial from well-respected members of the Microsoft blogging community have each in their own way come out against Google's OpenSocial initiative, Dare Osabanjo because in his view OpenSocial while billed as a standardized widget platform for the Web, actually isn't. And Don Dodge because his claim is that fifty million Facebook developers "don't know what OpenSocial APIs are...and don't care.""

Ponca City, We Love You writes "The NYTimes reports that Gene Munster, an analyst at Piper Jaffray, has studied Apple's financial statements and come to the conclusion that AT&T is paying Apple $18 a month, on average, for each iPhone sold by Apple and activated on AT&T's network — up to $432 over a two-year contract. This shows how much incentive Apple has to maintain its exclusive deal with AT&T rather than to sell unlocked phones or cut deals with multiple carriers. Last week Apple disclosed that 250,000 iPhones had been purchased but not registered with ATT that Apple thinks are being unlocked so Apple has now taken action to curb unauthorized resellers by limiting sales of the iPhone to two per customer and requiring that purchases must now be made with a credit or debit card — cash will not be accepted." The latter article links to a US Treasury page explaining the incorrectness of the widely-held belief that cash cannot be refused for any transaction.

Bongo Bob writes "CNET.co.uk has up a review of the Asus Eee PC 701 that runs Linux. According to the reviewer. 'It's hard to fault the Eee PC, mainly because of its price. It can be difficult to use because of the cramped keyboard, but it's better than similar-sized laptops like the Toshiba Libretto. If you're in the market for a second PC, or looking for something you can take with you almost anywhere, the Eee PC is definitely worth buying.'"

Gibbs-Duhem writes with news that MIT has dropped its subscription to the Society of Automotive Engineers' web-based database of technical papers over the issue of DRM. The SAE refuses to allow any online access except through an Adobe DRM plugin that limits use and does not run on Linux or Unix. Also, the SAE refuses to let its papers even be indexed on any site but their own. SAE's use of DRM is peculiar to say the least, as they get their content for free from the researchers who actually do the work. And those researchers have choices as to where they send their work, and some of the MIT faculty are pretty vocal about it. From the MIT Library News: "'It's a step backwards,' says Professor Wai Cheng, SAE fellow and Professor of Mechanical Engineering at MIT, who feels strongly enough about the implications of DRM that he has asked to be added to the agenda of the upcoming SAE Publication Board meeting in April, when he will address this topic."