|
2015-11-09
, 07:00
|
Posts: 285 |
Thanked: 1,900 times |
Joined on Feb 2010
|
#1672
|
IC. Thanks for the clarification, now I see where you are coming from. To clarify my stance, I was completely and consciously ignoring that bit because to the best of my knowledge, Sailfish comes from the same people as Harmattan. Not the same company, but the same people.
Jolla does not have to implement all the bells and whistles anew, only remember how they were implemented the first time and do it again, in those few cases where for copyright reasons they cannot use an already existing code.
|
2015-11-09
, 08:40
|
Posts: 592 |
Thanked: 1,167 times |
Joined on Jul 2012
|
#1673
|
- You don't need to have everything 100% ready at day 1 or even day 2. You need a viable platform to build upon.
- Added features increase overall complexity. Complexity increases the cost and time needed to implement and test it all.
- If you try to do too much in one step, you will end up with budget overruns, delays and boatload of bad PR, no matter how good the end product may be in the future. People just love to see bad things happening (to others).
- Adding features in incremental steps has proved to be effective strategy
|
2015-11-09
, 09:59
|
Posts: 285 |
Thanked: 1,900 times |
Joined on Feb 2010
|
#1674
|
I believe this to hold true only if your platform is actually viable, that is, created to be adaptable.
Now, the question is, is SFOS such a platform? It appears to me that this "let's keep it flexible and simple" (very common in UNIX systems overall and definitely not a bad idea) is kind of the opposite of what Mr Jobs has done with iPhone; who knew what they wanted (and needed) and focussed on it by providing for example high-level, easy to use API's for developers for basically everything.
|
2015-11-09
, 12:47
|
|
Posts: 1,389 |
Thanked: 1,857 times |
Joined on Feb 2010
@ Israel
|
#1675
|
Apple had some serious restrictions what you could do with their API:s. There's no reason why Sailfish per se couldn't be adaptable, but Jolla does has some restrictions in their store, which IMO is something that should be addressed with high priority (as should proper support for paid-for apps in store and general support for more APIs). We don't know why, but my guess is that they need to develop better tools to check and QA apps that are to be delivered there.
|
2015-11-09
, 13:19
|
Posts: 285 |
Thanked: 1,900 times |
Joined on Feb 2010
|
#1676
|
Actually iOS is based on unix and you can get access to system with jailbreak and do a lot of interesting stuff. For example one of the really popular TMO users added support for android wearables for iPhone before it was released officially by Google :P
And if you say that he publish app to Stroe, you should remember that there are a lot of API limitations for Sailfish store even with available APIs :P
You can call me troll or that I'm bashing, but there are more than enough reasons for that....
|
2015-11-09
, 13:27
|
Posts: 71 |
Thanked: 621 times |
Joined on Sep 2010
@ UK
|
#1677
|
|
2015-11-09
, 13:33
|
|
Posts: 7,075 |
Thanked: 9,073 times |
Joined on Oct 2009
@ Moon! It's not the East or the West side... it's the Dark Side
|
#1678
|
I just wanted to say thank you, to all who have posted in this thread, I agree with some things people post, I disagree with a lot more, but either way they are mostly quality, well thought out, informative,intelligent posts, and well worth reading (not including mine of course)
Its keeping me interested until my Tablet does finally arrive - im sure it will, just not sure when. This year, next year?
The "water" posts had me in stitches.
|
2015-11-09
, 13:42
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#1679
|
As of paid apps, there is huge thread on TJC that is few years old and was started by Jolla about paid apps, but as it get activity Jolla ignored it and any questions(again they started this thread, which is ironical). And after a huge noise from community on TJC/IRC/here/twitter they finally answered with "more info soon (c)" reply, as always
|
2015-11-09
, 14:17
|
|
Posts: 1,196 |
Thanked: 2,708 times |
Joined on Jan 2010
@ Hanoi
|
#1680
|
Um.... no. You missed the point, which was not comparison between Harmattan and Sailfish.
Mobile OS's and devices have very long history of development, along with it comes burden of history. Now, if newcomer is to support all the bells and whistles invented in that time frame, it will take huge amount of time and resources even if those technologies are considered to be "already existing." So the choice is either to release something that doesn't have it all, or try to reassure investors to fund closed development for 5+ years to have "everything" in place. And after you launch it, there are those cheeky guys saying it's half baked because there is no support for X or Y, if needed it can be some non-relevant legacy bit from six years after the great potato war....
Also, it's worth mentioning that F-16 was to be cheap, maneuverable fighter without all the bells and whistles instead of super expensive, all-new super-fighter like F-15 or F-14 (which actually was also released half baked, it's development was done in three major parts because it was known that it would never enter the service if everything was to be ready at launch...). Most of F-16's capabilities have been added on later, so it kind of launched half baked. But it was extremely successful. F-35 was not made from scratch either, every invention has roots somewhere and F-35 draws from previous generations of multi-role fighters and iterations of stealth-fighter/bombers. Most of weapons for it already exist and have been in active service for years. How come it takes so much effort to integrate them all? One of the reasons is actually software and kind of UI for all of them, as F-35 is not designed to just bolt on different weapons and use them as it has been done before but to integrate multiple systems into much improved combination of sensor data and situational awareness. Among other fancy things. It's very ambitious plan - which unfortunately has resulted in budget overruns, delays and PR-catastrophe even before entering service. Still, there is a good chance it will turn up to be very competitive in the future.
How does it compare to Sailfish? If there are lessons to be learned, IMO they would be these:
- You don't need to have everything 100% ready at day 1 or even day 2. You need a viable platform to build upon.
- Added features increase overall complexity. Complexity increases the cost and time needed to implement and test it all.
- If you try to do too much in one step, you will end up with budget overruns, delays and boatload of bad PR, no matter how good the end product may be in the future. People just love to see bad things happening (to others).
- Adding features in incremental steps has proved to be effective strategy
Tags |
moral hazard, paypal refund |
|
The problem is the 'not invented here' mentality that seems to be prevalent these days. Inventing your own wheel means it's easier to control it.
'Men of high position are allowed, by a special act of grace, to accomodate their reasoning to the answer they need. Logic is only required in those of lesser rank.' - J K Galbraith
My website
GitHub