I used work for a company that wrote frameworks and drivers for 3rd party apps. BC breaks were not tolerated at all unless supported by the appropriate paperwork. If they happened managers were called and fixes were rushed through as your team would not be allowed submit anything else until it was fixed. This break should have been caught.
I tried out Rigid Gas Permeable lenses a few days ago and could only tolerate them for about 20 minutes. I've been wearing soft lenses for over 15 years.
I can't see anyone tolerating that level of discomfort without a really really good reason.
InstantiationException.IllegalAccessException cannot be resolved to a type Maze.java/Maze/src line 76 Java Problem
Syntax error on token "|", . expected Maze.java/Maze/src line 76 Java Problem
The method lineSeparator() is undefined for the type System Maze.java/Maze/src line 139 Java Problem
They struggled greatly with it in fact. It was one of the reasons they dropped Sybmian, the 'ecosystem' never took off. Symbian C++ and frameworks were complicated, and the signing program was a disaster. Maemo had a couple of apps sure but nothing like what Apple have.
Elop considered the 'ecosystem' to be the most important thing for the survival of the company.
The problem with this is that in urban areas you'll encounter lots and lots of picocell towers, and these may vary over time. In short, with GSM/3G you're never really sure who you're connected to. Apparently the Chinese embassy in London has its own tower and uses it to gather info on any protestors outside.
The 'bad code written in India' mainly came from the SoC manufacturers who'd write the baseports and drivers, in my time they were Broadcom and ST-Ericsson. (The Raspberry Pi uses the same graphics hardware as the N8). They were so flaky you couldn't believe. And on top of that Nokia management expected the entire stack to be developed in parallel. It was unworkable, they'd release new Symbian environments a few times a day and if it worked you got lucky, if it didn't you just wasted 4 hours downloading Gigs of rubbish only to have to delete it and see if anyone else had a working env. There were other Nokia-proper teams in India but the code they wrote shouldn't have brought down a board and if it did there was usually a workaround. However due to the *appalling communication* within Nokia it was nigh-on impossible to find out what the workaround was, or even who to ask.
We'd have to do test runs everyday yet the phones in development crashed constantly and unpredictably so you couldn't tell if it was your code causing the problem or something else. Managers demanded answers and ignored the truth. To be fair the whole system was so fucked there really was nothing that could have been done.
The subcontractors that I knew of were Sasken and another I can't think of right now.
The Symbian Ltd employees who were bought by Nokia could not believe how fucked up Nokia was at software. To be honest, I'm wasn't aware of any competition between teams but I wasn't in Finland.
Here's the reason given in the archive for the theft/release:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This archive contains 18,592 scientific publications totaling
33GiB, all from Philosophical Transactions of the Royal Society
and which should be available to everyone at no cost, but most
have previously only been made available at high prices through
paywall gatekeepers like JSTOR.
Limited access to the documents here is typically sold for $19
USD per article, though some of the older ones are available as
cheaply as $8. Purchasing access to this collection one article
at a time would cost hundreds of thousands of dollars.
Also included is the basic factual metadata allowing you to
locate works by title, author, or publication date, and a
checksum file to allow you to check for corruption.
ef8c02959e947d7f4e4699f399ade838431692d972661f145b782c2fa3ebcc6a sha256sum.txt
I've had these files for a long time, but I've been afraid that if I
published them I would be subject to unjust legal harassment by those who
profit from controlling access to these works.
I now feel that I've been making the wrong decision.
On July 19th 2011, Aaron Swartz was criminally charged by the US Attorney
General's office for, effectively, downloading too many academic papers
from JSTOR.
Academic publishing is an odd system—the authors are not paid for their
writing, nor are the peer reviewers (they're just more unpaid academics),
and in some fields even the journal editors are unpaid. Sometimes the
authors must even pay the publishers.
And yet scientific publications are some of the most outrageously
expensive pieces of literature you can buy. In the past, the high access
fees supported the costly mechanical reproduction of niche paper journals,
but online distribution has mostly made this function obsolete.
As far as I can tell, the money paid for access today serves little
significant purpose except to perpetuate dead business models. The
"publish or perish" pressure in academia gives the authors an impossibly
weak negotiating position, and the existing system has enormous inertia.
Those with the most power to change the system--the long-tenured luminary
scholars whose works give legitimacy and prestige to the journals, rather
than the other way around--are the least impacted by its failures. They
are supported by institutions who invisibly provide access to all of the
resources they need. And as the journals depend on them, they may ask
for alterations to the standard contract without risking their career on
the loss of a publication offer. Many don't even realize the extent to
which academic work is inaccessible to the general public, nor do they
realize what sort of work is being done outside universities that would
benefit by it.
Large publishers are now able to purchase the political clout needed
to abuse the narrow commercial scope of copyright protection, extending
it to completely inapplicable areas: slavish reproductions of historic
documents and art, for example, and exploiting the labors of unpaid
scientists. They're even able to make the taxpayers pay for their
attacks on free society by pursuing criminal prosecution (copyright has
classically been a civil matter) and by burdening public institutions
with outrageous subscription fees.
Copyright is a legal fiction representing a narrow compromise: we give
up some of our natural right to exchange information in exchange for
creating an economic incentive to author, so that we may all enjoy more
works. When publishers abuse the system to prop up their existence,
when they misrepresent the extent of copyright coverage, when they use
threats of frivolous litigation to suppress the dissemination of publicly
owned works, they are stealing from everyone else.
Several years ago I came into possession, through rather boring and
lawful means, of a large collection of JSTOR documents.
These particular documents are the historic back archives of the
Philosophical Transactions of the Royal Society—a prestigious scien
Symbian was designed by several phone manufacturers, there was no 'one-designer'. It's not unmaintainable at all, but it was difficult to write for as developers had to know about things uch as asynchronicity (you'd be surprised by how many can't get this right... every API in Symbian was asynchronous - it saved battery).
As for S40, when I left Nokia they were considering a rewrite because expanding the platform became so difficult. What saved it was that it seemed to have a long-term group of developers who knew it inside out and they were mostly all in Denmark and Finland. Symbian OS was developed in London and then it spread out to India and China. Quality dropped.
IIRC, you have to encode the key, encode the parameter, append them with '&' and encode again, and then sort them, generate the signature, encode the signature key and the signature itself. Or something. Oh and the encoding routine is urlencode plus some extra characters so that has to be written from scratch too.
Hi Mark, thanks for replying.
Do you not think it was a flaw to target a spec towards a specific language/architecture?
Another thing that really pissed me off was the complete lack of help testing my implementation. I'd have given up far sooner if it hadn't been for this site: http://term.ie/oauth/example/client.php
I tried to implement OAuth v1 on a mobile device. What a pain in the hole. And it all fell down once you had to get the user to fire up the browser to accept the request. There was no way (I could figure out) to handle the callback so instead it seems to have been implemented via a corporate server thereby defeating the whole purpose of it. The easiest to work with was DropBox.
I never got what extra level of security sorting the parameters provided the signature would show up any tampering, it just means you gobble up memory unnecessarily.
I don't see what Symbian had to do with Meego. They were totally independent projects with Meego having a far higher level of secrecy. Symbian had its own developers and Meego had theirs. The problems with Symbian were several-fold:
- High learning curve: chipset manufacturers didn't like it as they couldn't get decent developers. India didn't churn out Symbian developers. Their code was typically very buggy and due to low level nature of it buggy code in a driver could prevent any development in the higher levels from happening at the required pace due to development boards (early phone prototypes) freezing up with no way of diagnosing the problem easily; the baseports and higher level development were expected to be done simultaneously. Project deadlines constantly slipped (the N8 was late by about a year). A QEmu simulator was under development but ultimately abandoned for reasons I'm not too sure about. Code would be committed that wouldn't compile... basic shit. This would affect *every* developer as they'd waste several hours downloading the latest environment only to find it didn't work.
- Underpowered hardware: It just wasn't up to the job, RAM was never enough. Use-case tear-down and reconstruction rarely worked (related to the point above)
- Politics: Symbian was a cash-cow for years and every ladder-climbing manager wanted in. It soon became impossible to get a 'Yes' decision on anything, and if you weren't in Finland your opinion counted for little. It was unclear who was really in charge.
- Symbian Signed: 3rd party developers were really shat on. Sure tools like Carbide were free (and fairly decent) but getting an app signed was a joke.
I'm not sure how much of this applied to Meego development, I was under the impression they were given a free hand to do as they liked, but Politics definitely became an issue there too when it became clear the project had a future.
I can't see it happening this way. Nokia wouldn't have developed the graphics drivers itself but received them from the GPU manufacturer (due to the presence of HD protection keys these would have been delivered in binary form only), the baseband code is likely to be full of Nokia's IP and thus would have to be done by someone else (Nokia sold its modem team to Renesas before Symbian got axed) and will probably be of iffy quality. I'm not sure these Meego guys will have access to the radio testing rooms as they did under Nokia.
Best of luck to them though
Slashdot Mirror
Asha phones are intended for developing countries where bandwidth can be limited and expensive They talk about it here http://www.developer.nokia.com/Develop/Series_40/Nokia_Browser_for_Series_40/
I used work for a company that wrote frameworks and drivers for 3rd party apps. BC breaks were not tolerated at all unless supported by the appropriate paperwork. If they happened managers were called and fixes were rushed through as your team would not be allowed submit anything else until it was fixed. This break should have been caught.
I tried out Rigid Gas Permeable lenses a few days ago and could only tolerate them for about 20 minutes. I've been wearing soft lenses for over 15 years. I can't see anyone tolerating that level of discomfort without a really really good reason.
You get a free book.
InstantiationException.IllegalAccessException cannot be resolved to a type Maze.java /Maze/src line 76 Java Problem
Syntax error on token "|", . expected Maze.java /Maze/src line 76 Java Problem
The method lineSeparator() is undefined for the type System Maze.java /Maze/src line 139 Java Problem
Bing's maps are provided by Nokia
They struggled greatly with it in fact. It was one of the reasons they dropped Sybmian, the 'ecosystem' never took off. Symbian C++ and frameworks were complicated, and the signing program was a disaster. Maemo had a couple of apps sure but nothing like what Apple have. Elop considered the 'ecosystem' to be the most important thing for the survival of the company.
The problem with this is that in urban areas you'll encounter lots and lots of picocell towers, and these may vary over time. In short, with GSM/3G you're never really sure who you're connected to. Apparently the Chinese embassy in London has its own tower and uses it to gather info on any protestors outside.
The 'bad code written in India' mainly came from the SoC manufacturers who'd write the baseports and drivers, in my time they were Broadcom and ST-Ericsson. (The Raspberry Pi uses the same graphics hardware as the N8). They were so flaky you couldn't believe. And on top of that Nokia management expected the entire stack to be developed in parallel. It was unworkable, they'd release new Symbian environments a few times a day and if it worked you got lucky, if it didn't you just wasted 4 hours downloading Gigs of rubbish only to have to delete it and see if anyone else had a working env. There were other Nokia-proper teams in India but the code they wrote shouldn't have brought down a board and if it did there was usually a workaround. However due to the *appalling communication* within Nokia it was nigh-on impossible to find out what the workaround was, or even who to ask. We'd have to do test runs everyday yet the phones in development crashed constantly and unpredictably so you couldn't tell if it was your code causing the problem or something else. Managers demanded answers and ignored the truth. To be fair the whole system was so fucked there really was nothing that could have been done. The subcontractors that I knew of were Sasken and another I can't think of right now.
You'd soon blow your beer budget if you were working with Finns and had to pay Finnish prices for booze.
The Symbian Ltd employees who were bought by Nokia could not believe how fucked up Nokia was at software. To be honest, I'm wasn't aware of any competition between teams but I wasn't in Finland.
Why not get coding instead of whining that someone else won't do something you want for free?
Here's the reason given in the archive for the theft/release: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This archive contains 18,592 scientific publications totaling 33GiB, all from Philosophical Transactions of the Royal Society and which should be available to everyone at no cost, but most have previously only been made available at high prices through paywall gatekeepers like JSTOR. Limited access to the documents here is typically sold for $19 USD per article, though some of the older ones are available as cheaply as $8. Purchasing access to this collection one article at a time would cost hundreds of thousands of dollars. Also included is the basic factual metadata allowing you to locate works by title, author, or publication date, and a checksum file to allow you to check for corruption. ef8c02959e947d7f4e4699f399ade838431692d972661f145b782c2fa3ebcc6a sha256sum.txt I've had these files for a long time, but I've been afraid that if I published them I would be subject to unjust legal harassment by those who profit from controlling access to these works.
I now feel that I've been making the wrong decision.
On July 19th 2011, Aaron Swartz was criminally charged by the US Attorney General's office for, effectively, downloading too many academic papers from JSTOR.
Academic publishing is an odd system—the authors are not paid for their writing, nor are the peer reviewers (they're just more unpaid academics), and in some fields even the journal editors are unpaid. Sometimes the authors must even pay the publishers.
And yet scientific publications are some of the most outrageously expensive pieces of literature you can buy. In the past, the high access fees supported the costly mechanical reproduction of niche paper journals, but online distribution has mostly made this function obsolete.
As far as I can tell, the money paid for access today serves little significant purpose except to perpetuate dead business models. The "publish or perish" pressure in academia gives the authors an impossibly weak negotiating position, and the existing system has enormous inertia.
Those with the most power to change the system--the long-tenured luminary scholars whose works give legitimacy and prestige to the journals, rather than the other way around--are the least impacted by its failures. They are supported by institutions who invisibly provide access to all of the resources they need. And as the journals depend on them, they may ask for alterations to the standard contract without risking their career on the loss of a publication offer. Many don't even realize the extent to which academic work is inaccessible to the general public, nor do they realize what sort of work is being done outside universities that would benefit by it.
Large publishers are now able to purchase the political clout needed to abuse the narrow commercial scope of copyright protection, extending it to completely inapplicable areas: slavish reproductions of historic documents and art, for example, and exploiting the labors of unpaid scientists. They're even able to make the taxpayers pay for their attacks on free society by pursuing criminal prosecution (copyright has classically been a civil matter) and by burdening public institutions with outrageous subscription fees.
Copyright is a legal fiction representing a narrow compromise: we give up some of our natural right to exchange information in exchange for creating an economic incentive to author, so that we may all enjoy more works. When publishers abuse the system to prop up their existence, when they misrepresent the extent of copyright coverage, when they use threats of frivolous litigation to suppress the dissemination of publicly owned works, they are stealing from everyone else.
Several years ago I came into possession, through rather boring and lawful means, of a large collection of JSTOR documents.
These particular documents are the historic back archives of the Philosophical Transactions of the Royal Society—a prestigious scien
Symbian was designed by several phone manufacturers, there was no 'one-designer'. It's not unmaintainable at all, but it was difficult to write for as developers had to know about things uch as asynchronicity (you'd be surprised by how many can't get this right... every API in Symbian was asynchronous - it saved battery). As for S40, when I left Nokia they were considering a rewrite because expanding the platform became so difficult. What saved it was that it seemed to have a long-term group of developers who knew it inside out and they were mostly all in Denmark and Finland. Symbian OS was developed in London and then it spread out to India and China. Quality dropped.
Sheeit. Sorry for getting all y'all hopes up.
Get over to tvcatchup.com to watch practically all UK channels, live.
IIRC, you have to encode the key, encode the parameter, append them with '&' and encode again, and then sort them, generate the signature, encode the signature key and the signature itself. Or something. Oh and the encoding routine is urlencode plus some extra characters so that has to be written from scratch too.
Hi Mark, thanks for replying. Do you not think it was a flaw to target a spec towards a specific language/architecture? Another thing that really pissed me off was the complete lack of help testing my implementation. I'd have given up far sooner if it hadn't been for this site: http://term.ie/oauth/example/client.php
I tried to implement OAuth v1 on a mobile device. What a pain in the hole. And it all fell down once you had to get the user to fire up the browser to accept the request. There was no way (I could figure out) to handle the callback so instead it seems to have been implemented via a corporate server thereby defeating the whole purpose of it. The easiest to work with was DropBox. I never got what extra level of security sorting the parameters provided the signature would show up any tampering, it just means you gobble up memory unnecessarily.
I don't see what Symbian had to do with Meego. They were totally independent projects with Meego having a far higher level of secrecy. Symbian had its own developers and Meego had theirs. The problems with Symbian were several-fold: - High learning curve: chipset manufacturers didn't like it as they couldn't get decent developers. India didn't churn out Symbian developers. Their code was typically very buggy and due to low level nature of it buggy code in a driver could prevent any development in the higher levels from happening at the required pace due to development boards (early phone prototypes) freezing up with no way of diagnosing the problem easily; the baseports and higher level development were expected to be done simultaneously. Project deadlines constantly slipped (the N8 was late by about a year). A QEmu simulator was under development but ultimately abandoned for reasons I'm not too sure about. Code would be committed that wouldn't compile... basic shit. This would affect *every* developer as they'd waste several hours downloading the latest environment only to find it didn't work. - Underpowered hardware: It just wasn't up to the job, RAM was never enough. Use-case tear-down and reconstruction rarely worked (related to the point above) - Politics: Symbian was a cash-cow for years and every ladder-climbing manager wanted in. It soon became impossible to get a 'Yes' decision on anything, and if you weren't in Finland your opinion counted for little. It was unclear who was really in charge. - Symbian Signed: 3rd party developers were really shat on. Sure tools like Carbide were free (and fairly decent) but getting an app signed was a joke. I'm not sure how much of this applied to Meego development, I was under the impression they were given a free hand to do as they liked, but Politics definitely became an issue there too when it became clear the project had a future.
How's the parent a Troll? Mod up.
I can't see it happening this way. Nokia wouldn't have developed the graphics drivers itself but received them from the GPU manufacturer (due to the presence of HD protection keys these would have been delivered in binary form only), the baseband code is likely to be full of Nokia's IP and thus would have to be done by someone else (Nokia sold its modem team to Renesas before Symbian got axed) and will probably be of iffy quality. I'm not sure these Meego guys will have access to the radio testing rooms as they did under Nokia. Best of luck to them though
You're the lucky one. Most people are on a waiting list for several months now
Power and syntax of C, safety of C++, useful compiler errors like Java. NO HEADER FILES!!!
You mean someone actually got their Pi delivered?