Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

Well, this was already posted several times. Still it was ignored by some people.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

Does Jolla intend that the Sailfish platform should be OpenGL ES 3.0 compliant, in order that app developers can have surety that in targetting new API's they don't disqualify a large proportion of the potential audience?

Even if OpenGL ES 3.0 support doesn't arrive in v1.0 of Sailfish, at least ensure the hardware is compliant:

http://talk.maemo.org/showthread.php...20#post1360320

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

IMHO people who never touched the Sailfish Alpha SDK shouldn't be complaining at all about technical issues/shortcomings/incompatibilities.
The others should wait for the new SDK with Wayland and Qt5 and will then realize how easy it is to port code from Qt4 to Qt5 usually.
And you'll probably not even realize that there's Wayland instead of X11, except for having better performance.

With PySide code the situation will look differently, but it was never advertised for Sailfish development in the first place. It's a dead Nokia project. It's opensource and you can try port it to Qt5 if it's worth, or wait and see what PyOtherSide will be capable of. Probably PyOtherSide will be the cleaner and faster approach to bring QML and Python together.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

Are you a developer yourself? If yes, you should now already that developing is moving forward not backward. Stuff changes all the time. Also developers inside Jolla knows that.

Python3 not backward compatible with 2
Qt4 not backward compatible with Qt3
Gnome2 not compatible with Gnome1

X11 not backward compatible with itself.

And in case of computer languages: New languages comes and others dies.

and so on...

If you are a developer and dont like movement you will get into trouble thats for sure.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

OK do we have a conclusion here?
What is the bottom line - is Sailfish burning or cool platform? :p :D

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

http://www.jollausers.com/2013/07/wh...-a-comparison/

:cool:

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

The conclusion? Sailfish is a cool new OS. But it's till unknown and we can't if it good for the enduser or not.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

What i meant... its their job to make sure its possible and easy for developers to port apps rather than pointing developers to do efforts for them. "The way forward" and "contributing" is BS if a company fails to do that.
Btw, since i never said anything about changes your answer was irrelevant.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

...that's that certain

"do it yourself (or at least don't complain to someone), you can do it yourself because "everythings' open", if you won't / can't "contribute", you are against us and should just f*ckoff."

FOSS mentality you'll never get away from their minds. You cannot "win" (arguments).

Not even when we are talking about a commercial provider here, that wants to get traction with an unproven platform even before any shipments and of course also wants (your) money by selling you devices.

Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 

They're already doing A LOT that'll benefit others moving into the same area*, with very limited resources mind you.
It's unreasonable to expect that they alone must drive the entire XWayland & Python bindings initiatives.
They've already made a solid start on the latter, it remains to be seen if they'll do the same for the former.
But if they eventually do, then the whining really needs to be dialled down, dramatically...

*Hello Canonical -Who's already taken code from Jolla/Others "internally" a few times
They've typically released it later, but only after being pressed, & it's not been released in a friendly manner