maemo.org - Talk - Maemo & Closed source

maemo.org - Talk (https://talk.maemo.org/index.php)

- General (https://talk.maemo.org/forumdisplay.php?f=7)

- - Maemo & Closed source (https://talk.maemo.org/showthread.php?t=31131)

Re: Maemo & Closed source

Quote:

Originally Posted by SD69 (Post 318913)

Entitled but not obligated. Maybe there is something we don't know, but from what I know so far, it seems to me that people should be scrutinizing the manufacturers who are locking down their devices rather than the party who provided the FOSS in the first place.

Exactly...

Re: Maemo & Closed source

Why ? The manufacturers didn't force Google to choose the license and are perfectly in line with what the license allows them to do. Or are we mixing Open with Free with regard to governance again ?

Re: Maemo & Closed source

Quote:

Originally Posted by attila77 (Post 318929)

Why ? The manufacturers didn't force Google to choose the license and are perfectly in line with what the license allows them to do. Or are we mixing Open with Free with regard to governance again ?

And Google didn't force manufacturers to lock down their devices.

I'm not mixing up anything.

Re: Maemo & Closed source

Quote:

Originally Posted by attila77 (Post 318929)

The manufacturers didn't force Google to choose the license and are perfectly in line with what the license allows them to do.

They are and i like this model of full choice.
However after all the consumers decide by buying those products.
It wil be interestig to see how open Android implementations will perform against closed ones.

Personally i think it won't matter to the average user and design/usability will win.

Re: Maemo & Closed source

I did some research about those topics and this is what i found out.

Quote:

Originally Posted by allnameswereout (Post 318869)

IMO its more important to understand why (for Maemo reference see Andre Klapper's post above).

The SDK contains proprietary elements like integration with Google Maps but those are not essential to Android as an operating system.
In fact you can build the whole SDK from scratch. (Excluding those proprietary extras).

Quote:

Originally Posted by allnameswereout (Post 318869)

Which is why its as problematic as iPhoneOS to me. Sometimes, using open or defacto standards is more important than open source. Sometimes, a proprietary yet compatible product is better than an open source product which does not use open or defacto standards. Case in point: X11. TCP/IP stack. No X11 or TCP/IP stack sucks for me.

From what i found out this was a design decision.
Using a combination of QT/Gtk/X11 was considered too CPU intensive and not suited for mobile devices.
Of course it's another topic if this decision was correct but IMO it's a valid excuse for not using those defacto standards.