Ware, Ryan R a écrit :
On 8/13/10 2:53 PM, "Robin Burchell" <[email protected]> wrote:
Hi,
Excerpts from Jean-Christian de Rivaz's message of Fri Aug 13 21:33:18
+0100 2010:
Agreed, it didn't have much to do about SSE3, but when the accelerated
graphics portion takes over, _that_ is the part it shows up.
Again, you failed to list a single Meego package that will not support
a
non SSSE3 machine by design. Others kind of accelerated graphics
optimization exists aside of the SSSE3 set.
I think all of this is on a bit of a tangent. Nobody in this discussion
(as
far as I know?) has advocated that doing away with an ssse3-optimised
build
would be a step forward.
Going around in circles over what benefits ssse3 does and doesn't provide
isn't
helping this debate I think, because at the end of the day, if Intel want
this,
then they're more than capable of making it happen.
As I understood it, The argument is that an additional, non-optimised
build
should be introduced, so that those using AMD processors (and yes,
slightly
older Intel processors) can also benefit and use/test/develop MeeGo.
<reasoning>
This is especially important in an application developer context: if an
application developer can't use MeeGo, and the competition Just
Works(tm), then
they aren't going to shell out £300 or whatever other "insignificant"
amounts
might be required to get new hardware: they'll use the competition.
Given that MeeGo is arriving a bit late to this game, I think this is
something that can be ill-afforded, personally: issues like this aren't
going to help us gain developer mindshare. At all.
</reasoning>
There's nothing wrong with the reasoning, but the question comes (as Greg
KH brought up) is who supports this. Adding a new build for older
hardware is far from free. Who's infrastructure does the release build?
Who's infrastructure does daily builds? (Building QT alone right now
takes 4+ hours in OBS.) Who is going to put forth the validation
resources for that build? Who is going to triage the bugs that come in
for that build? Who is going to fix the bugs that come in for that build?
Those are only the questions that came to mind before I had to pause and
think my next sentence. There are many issues with adding another build;
the vast majority of which are currently un-scoped and only the least
significant (changing the build configuration) has been spoken for.
Getting an additional build out in the field is far from a small effort.
This is _really_ disappointing. When all those extremely critical
questions has been raised at the Meego creation time, there all have
been pushed out by the argument that Meego and his OBS will be
incredible compared to others possible upstream distributions and that
we have to wait before judging too hard at them.
Now what ? Should I cancel my Dublin registration and buy an Androïd
device ? Because if there is not a really clear official response to all
this mess, I don't see any future to Meego. I expected to see a open
distribution able to find a major place into the future market of
devices that converge the desktop and the mobile of a vast range of
hardware. Now this end up to be a Intel only way. So not with me. Sorry.
Regards,
Jean-Christian de Rivaz
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
