Thread: The Original And Classic Off Topic Jolla T-Shirt Shipment Thread[Closed]
View Single Post
jalyst is offline jalyst
2013-07-16 , 14:55
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#201
What's with the antagonistic response....

Originally Posted by don_falcone View Post
Uh oh... may i point you do the fact that for at least one of those firms (it starts with an 'X', i'm not too familiar with the others), there in fact is a whole cloud service infrastructure (including synchronization, backup, and payment processing) that's _not_ hogging onto Google's service hosting train? That they have enough employees to provide updates _every Friday_?
That's hardly unique in the Android world, you seem to have missed the point being made, perhaps that's my fault for not being clear enough initially.

Giving that most of Jolla's homework is done by other groups too (so-called 'communities') that care for the actual development of base OS, frameworks, and SW components, i can't see that they realistically have to care for building much from scratch, besides their (closed-source by the way) UI components and related integration.
You mean Mer & Nemo, the upstream projects for Sailfish? The overwhelming majority of that work is in-fact done by Jolla, it's not mostly pulled from elsewhere, not even close.
You're mistaken about the "UI component", Silica is open, they have said some core apps/components will be closed for the licensed version of Sailfish.

Further, it was mentioned most of their guys came with an Maemo and N9 projects background; so it's even more moot thaey have to start from scratch. They are definitely able to leverage their expertise here and shorten their cycles.
Are you seriously trying to compare those completely distinct code-bases (i.e. they're not building on them at all) with Android's?
A project which has had far more commercial momentum/backing, & way less speed-bumps, for 3yrs+ now...
The only advantage they take from Freemantle/Harmattan, is the experience of having done similar work, that's NOT the same (or even close) as the code advantage that Android OEM's start with.
And much of the work was NOT done by Nokia when it comes to MeeGo-proper, MeeGoCE was little more than a proof-of-concept when most resources were dropped in Q1 2011.
For all intents & purposes they have started from scratch, & in a properly organised fashion since only about Jan/Feb 2012.

And unless someone close to them can prove that they designed all of their hardware in-house, i bet there's a huge re-use of COTS board-level components going way farther that basic SoC reference designs.
I doubt very much there'll be a huge level of customisation beyond reference, way more resources already goes into the sw/infra side compared to the typical Android ODM.
Plus, if the "Other Half" is as innovative as they've alluded to, that in itself would suck-up a relatively large amt of resources for such a tiny co.
A fair bit may have gone into design/aesthetics/build-quality, perhaps not much more than your typical mid-tier Android ODM, time will tell.

And how many people are Jolla now, like 50? I bet they are steering towards 80. (sorry, can't be arsed to grep their Twitter musings for that...)
That's not a startup; size-wise.
It most certainly is, it's minuscule compared to the top 10 players in the Android sphere, heck most probably even the top 20.
For Android ODM's far less resources go into sw, much more of the legwork is done compared to Nemo/Sailfish ODM's, because it's shared so far/wide.
The biggest players are the ones that shift it forward most, there's some niche players doing some unique things, but they're by no means driving the bulk of it.
Jolla is handling the lion's share of work for Mer/Nemo/Sailfish, a tiny start-up compared to the biggest players (or even the middlings) in Android.