Be more specific...

Cool games.

Come on, you can dream up some of that yourself. And often you see that new technology sparks new inventions. I've seen multiple new wireless things, which thanks to the extreme low power requirements of bluetooth 4 are finally capable of directly communicating with smartphones.

lol, and you haven't grasped that i am not talking about a game or app today, i am talking about the speed at which development in general will adopt those new standards tomorrow.

what he said was irrelevant, i was was quoting you.

I guess a nice comparison of the new and changed features of OpenGL 3.0 vs 2.0 might break this stalemate.

my pleasure:

http://www.anandtech.com/show/6134/k...ression-clu/2/

It's a must be for me. Unless we want to be stuck with an obsolete base which has problems supporting newer stuff, like Maemo has an obsolete x11 (but this is software related so opengl is worse) or thumb2-incompatible soc

Not commenting any details about the actual hw. Your feedback has been read. Some people will be pleased and some people will never be pleased to anything short of a 200fps space rocket.

Just saying that even if hw would support fancy new things like BT4.0, ES X.0, its more about the fact what android adaptations are available through libhybris and when, and what core version open source components like bluez support. If you want to wait for months for some adaptation to stabilise or Android 4.3 to appear for specific SoC, then your not going to get the device this year. And I think that we all want to have the device this year, don't we?

Of course its nice if HW supports new things, and you can participate on Mer/Nemo projects to update middleware to support software features even if some of your 'must have, cannot live without vibrating earpiece' are missing from PR1.0.

i do indeed want a sailfish phone this year, and "waiting" until OpenGL ES 3.0 drivers were available via libhybis for the chosen SoC would be silly.

but i only propose that a compliant SoC is chosen, and then adopt the driver once that arrives, in order that the whole jolla platform is openGL ES 3.0 compliant eventually.

i realise at this point the hardware i probably fixed, and the choices at the time may have made the rational choice impossible, i only ask that they consider it.

And maybe (might be stupid idea) we could get a SoC supporting ES 3.0, but still use libhybris providing 2.0 only? ES 3.0 compat would be provided later

The problem seems to be a difference in viewpoint.

Some are arguing: invest in the software first, and push it out when hardware/conditions are ready.
Others are arguing: push out the hardware first, then make a software update.

I think Linux needs a fresh re-boot.
It needs the best software available, with the best UX available. That means cutting out 95% of everything else, breaking compatibility to pave a new way for the ecosystem to thrive.

However, we tried this before quite a few times and failed.

Pushing out the dedicated hardware has been hard, neigh impossible.
So its better to push out half-assed hardware with half-assed software and advance.
Is it though?
No. We've also tried this method.

The best method is Android.
Say what you want but Google is twelve steps ahead of Linux.

Open Source philosophy is what drags Linux down.
Android is not open source.
Its closed source dictated by one company.
But the company has good direction, and later opens up the source.
Its a hybrid approach, and one much suited for this world.

We need the same muscle and philosophy Google uses on Android, except one for true Linux systems.
Nokia was meant to be it.
The N900 successor was meant to be a qwerty-tilt device with competitive hardware and superior software.
Yet the N9 we dreamt was trashed, and we got a bastardized iPhone competitor.

At this point, I'm just giving up hope.
Maybe Linux could catch a break. Maybe. Who knows.
I'm simply not holding my breath anymore, my phones will no longer be mobile computers but "fun gadgets" instead.