![]() |
Re: Closed Source Packages in Maemo
Quote:
|
Re: Closed Source Packages in Maemo
Quote:
Quote:
|
Re: Closed Source Packages in Maemo
@tag writer:
I notice the tag "try to correct an error" on this thread. Would the writer care to explain more? |
Re: Closed Source Packages in Maemo
Quote:
I would happily donate to any project that is going to deliver a feature I want or even that already has. The trouble is, if you donate to an open source project there is a chance the developer will get bored or real work will get in the way. Commercial on the other hand, it IS their real work so you pay them to implement a feature, they better do it. They also generally have more resources to throw at it and will not just do "the fun/interesting" bits, which any developer doing it as a hobby is likely to do. Quote:
|
Re: Closed Source Packages in Maemo
Quote:
I mean, with millions at stake, I'm sure they can afford a few IDA Pro hackers... Binary is source code after all, no matter how obfuscated you make it... If a few kid can crack games, I'm sure dedicated people can reverse engineer anything! So, what is the real advantage in locking down your hardware through some proprietary gate-keeping software when you benefit from it being used as widely as possible and you don't sell any software at all ? Quote:
|
Re: Closed Source Packages in Maemo
|
Re: Closed Source Packages in Maemo
You lock it down you gain a competitive advantage. You buy yourself a few months leeway while they are hacking away trying to clone your device.
As was said earlier, if you don't do that they may even release a clone product before the official product itself launches. I do not necessarily agree with the Release Early, Release Often for all software though. For one I wish KDE 4 had not come out until it was up to standard with KDE 3. Too many distros have adopted KDE 4 and practically dropped KDE 3, when 4 is just not ready yet. Had it not been "released early" they would have stuck with 3 that bit longer and avoided the ton of teething problems people have with 4. I get it, you need people to test it. But surely there are plenty enough people willing to risk early software rather than forcing it onto an unwilling public. But this is getting off topic. |
Re: Closed Source Packages in Maemo
Quote:
Quote:
It's all about giving access to the software early so to get as many eyes as possible on the code and fix things. It's definitely not branding alpha version as final 4.0.0 product ready to be shipped! If KDE ****ed up, it's totally unrelated! :/ |
Re: Closed Source Packages in Maemo
Quote:
In any case, feel free discussing the topic with them. :) Free software in the hardware adaptation layer is something that companies like Nokia would be also interested about. Well, there are a few browser available and a lot of media players on maemo's repository... :)[/QUOTE] As starters, the serious browser alternatives would imply Webkit, which is not supported in Maemo and is not a trivial task to productize. Moving away from the Mozilla family is a deeper strategic move aniway, not worth if the only "problem" is the UI layer being not open source. And still, I haven't said the browser UI will be closed, or open. For Media Players let's not forget that Python is not officially supported and productizing it is not trivial. MPlayer is a beast on it's own and there are many reasons not to ship it pre-installed. Probably the maintainers of MPlayer and the Maemo port would agree on this. And still I believer the Maemo 5 browser and media player would beat these options in many aspects that are essential even if not so evident: performance, footprint, stability, etc. But we shouldn't start discussing browser, media player or other specific app here. Looking forward to your Brainstorm proposals for browser and media player, listing the serious candidates for solutions and having their own threads for discussion. :) |
Re: Closed Source Packages in Maemo
Quote:
|
All times are GMT. The time now is 15:25. |
vBulletin® Version 3.8.8