if the perception of the Marketplace is that it's full of malware
Perceptions of non-geek do not involve words like malware. So it is only geeks' perception.
to most users, Android is the phone and what it comes with - the Marketplace will simply be a "never touch" zone
For more than a decade, downloading apps from the internet for Microsoft Windows OSes should have been a "never touch" zone. But actually it was very far from a never touch zone for "most users". No one could even beat the dancing bunny.
You are yet to come up with any arguments supporting this claim. Unless you believe in proof by repetitive assertion.
Your claim is possible, but far from "clear" as you want everyone to believe. I have an extremely good Samsung LCD monitor, but heaven forbid that turns my interest towards Samsung laptops.
There is nothing so misleading as an obvious fact - Sherlock Holmes
FYI, Fedora doesn't support jfs. First, you have to pass a kernel argument "jfs" to make fedora even run a JFS / or/boot. Even then, jfs is not presented as option for/,/home or any other mount point.
I've been using jfs on Fedora by 1. installing with ext4 2. boot into it 3. install jfsutils 4. backup the files 5. create a jfs file system 6. copy files on jfs file system 7. edit grub.conf and add jfs kernel argument.
That's Fedora for you. Or rather, I should say, Fedora is not for you, given your expectations from "production" ready.
"Reasonably" safe cutting edge features have always been part of Fedora - be it kernel level mode setting, pulse audio, ext4 in its early days. You are encouraged to file bugs if it makes your system crash. No guarantees that the bug will be fixed, of course.
So this could have been the response you should have given, rather than starting to sensationalize the "consequences". Your failing to mention this in your original post suggested that you don't mind that the evidence is anecdotal given the "consequences".
Your "proven conclusively its unsafe" approach would only be appropriate if we were discussing a benefit of substantial value, which we are not.
The post you replied to objected to the evidence being anecdotal. Your reply didn't argue about non-anecdotal evidence there, but you started to harp on the "consequences". My reply was not to "all the arguments you made in your life" but to that single post of yours.
The approach "proven conclusively its unsafe" is not mine, but it is of that post of yours to which I replied. I just used it to reach absurd conclusions to demonstrate the absurdity of the approach.
How is eating an apple weighing between 75.45 and 75.46 grams of substantial value? There are many other apples to choose from, not to mention other food materials.
Has it been proven conclusively that a passenger boarding an aircraft after eating an apple weighing between 75.45 and 75.46 grams does not increase significantly the chance of the aircraft crashing within 46 minutes and 34 seconds of taking off? By your argument, and considering the magnitude of consequences, lets ban apples of the said description.
How about apples weighing between 83.51 grams and 83.52 grams? Pizzas of total carbohydrate content between 31.94 grams and 31.95 grams?
As you say, any actual risk does not have to be demonstrated, just an irrational fear needs to be invoked with sufficient sensationalism.
In fairness, every ad supported app requires network access for downloading apps
Actually, not exactly. App doesn't need to access the network itself, it just calls google's API. Google's API implementation then needs network access. So disabling network access works just fine even if they have to show Android ad framework supported ads.
Only to implement their own ad framework, each app needs its own network access. I don't think that is a good idea anyway.
Your first paragraph seems a re-iteration of your earlier points, second one seems to be trying to give a reason for it. Correct me if I am wrong in this.
1. Nokia never made Symbian. 2. It can be argued that as long as Symbian was relatively independent (48% owned by Nokia, rest by Samsung, SonyEricsson etc), Symbian was doing well. Once under Nokia, not so well. That is when Symbian marketshare started decelerating and then plummeting. 3. "Microsoft has said that they will share the internal details" is completely different from them actually sharing. If a company bases its business model on good faith in Microsoft, God help it. 4. The good coders may not be in Nokia any more after the huge layoffs. Note that blanket layoffs shows enormous disrespect to employees, so even high-performance employees are likely to quit. 5. Nokia has never yet demonstrated their expertise in customizing closed blobs of OS like MS win phone 7 is likely to be. 6. Even if Nokia had demonstrated any such expertise, this is a completely new Nokia from top to bottom. So a repetition of similar success is far from guaranteed. 7. Competitive landscape is a lot different now from "back in the day". Nokia has never demonstrated an ability to survive in a marketplace like today's. 8. Creating a stunning mobile OS is no guarantee of (at least immediate) success as demonstrated by Maemo, HP WebOS, RIM QNX etc. All these OSes got excellent expert reviews, today having negligible market share. Android and iOS, with all their defects, are ruling.
After all these, Nokia's success from "customizing" Win Phone 7 is at best suspect. Far from the certainty you make it out to be.
In 2005, Nokia released (and open-sourced) python for S60. All that Android gains by Dalvik and iOS gains by virtualized objective-C could be gained by python. Software of some respectability could be written in python, and it was trivial to write trivial software right on the phone itself - so much can't be said for Android.
if Nokia gets a special customise WinPho7 card to play, where does that leave all the other manufacturers? It'll probably leave Nokia as the *only* Windows phone manufacturer
Why is that? HTC (and everyone else) can customize Android, but still there is a market for un-customized Android, as shown by appreciation of Nexus series (though lack of sales channels caused it to not have many users).
Why do you think Nokia customization of Microsoft's OS, without many internal details shared by Microsoft (as MS does to all its desktop/laptop software partners) will undoubtedly be better than stock Windows phone 7? When has Nokia, let alone a Nokia minus thousands of employees, ever shown great expertise to customize a closed OS blob?
You might find Made in Japan instructive and enjoyable. It is written by a founder of Sony.
He explains how, even in its early days, Sony refused to get into price wars with competing electronics manufacturers. Note that price-war, while reducing corporate profits, are extremely beneficial for customers.
During early days, there was not much demand for Sony items at high prices because those days, Japanese manufacturing was considered inferior to American and European. But Sony refused to let their retailers sell Sony branded items cheap, even if no one was buying them. Logic was that a high price suggests a "premium" product to customers, regardless of quality.
Yeah, but I guess you have changed the argument. Your original statement was to someone comparing iPhone's openness and Android'd openness. Your statement could only be taken as denying Android's openness. Now you change tack and allege something illegal is going on (which is true in a way, but besides the point here).
iPhone's openness, whatever it is, is by virtue of one unfair advantage (of Apple over AT&T and other carriers) winning over another unfair advantage (of US carriers over US customers). So the openness itself is not open. It could be a temporary victory of one tyrant over another. Android's openness is inherent in product design and license terms. US law enforcement being screwed up, this openness comes at a cost. But in any sensible market environment, it is clearly superior. Even for the US, you would not deny that a sensible market environment is the right way forward rather than a battle of tyrants providing occasional comfort to customers?
So, back on topic, there definitely are Android open phones. Due to carrier prejudice, this openness is expensive, but that is besides the point. Why then, do you say
"When all three carriers lock down the phones designed for their respective networks in undesirable ways, I have the Hobson's choice of doing without." ?
You can "buy" openness if it is worth any money to you. You can buy cheap locked down phones, if that is worth openness to you. Why is it a Hobson's choice? That is like saying you have a Hobson's choice between buying food and staying hungry.
But half of Nokia models are buggy (other half are excellent). You need to research which ones randomly reboot while in a call, or explode while charging, or their UI freezes when camera is started.
Not only Nokia, but most manufacturers which have a big variety, have this issue. Only Blackberry, HTC, Apple have limited number of models so a simple feature comparison suffices.
Re:What the XBox 360 is doing for Microsoft
on
Why Nokia Is Toast
·
· Score: 1
Nokia need to stick to their simple 12 keys and a monochrome screen for all the parents out there
Nokia failed in that too. 2 reasons 1. Nokia's "release 20 handsets per month in one segment" policy made sure that parents have to research the latest good "parent phone". Research is what parents are worst at. While general handset quality of Nokia is quite good, they often have big duds (some in battery life, some in exploding, keypad quality etc.). So buying Nokia without research never made sense. One dud buy, and the parent swore away from Nokia.
2. Large fonts - Most entry level Nokia phones did / do not have large fonts.
Slashdot Mirror
what open source filesystems do you actually find in the datacenter ? I look at our unix infrastructure and I see : VxFS, JFS2 and Zfs, in that order
2 of these 3 filesystems are open source, so you yourself actually find open source filesystems in the datacenter.
if the perception of the Marketplace is that it's full of malware
Perceptions of non-geek do not involve words like malware. So it is only geeks' perception.
to most users, Android is the phone and what it comes with - the Marketplace will simply be a "never touch" zone
For more than a decade, downloading apps from the internet for Microsoft Windows OSes should have been a "never touch" zone. But actually it was very far from a never touch zone for "most users". No one could even beat the dancing bunny.
This was many people observing the halo effect
Which many people?
The causation is quite clear
You are yet to come up with any arguments supporting this claim. Unless you believe in proof by repetitive assertion.
Your claim is possible, but far from "clear" as you want everyone to believe. I have an extremely good Samsung LCD monitor, but heaven forbid that turns my interest towards Samsung laptops.
There is nothing so misleading as an obvious fact - Sherlock Holmes
Well, RAID-Z can almost emulate RAID-5 and RAID-6.
Also, BTRFS does have RAID and LVM capabilities as mentioned in the summary. It can also span multiple storage devices.
FYI, Fedora doesn't support jfs. First, you have to pass a kernel argument "jfs" to make fedora even run a JFS / or /boot. Even then, jfs is not presented as option for /, /home or any other mount point.
I've been using jfs on Fedora by
1. installing with ext4
2. boot into it
3. install jfsutils
4. backup the files
5. create a jfs file system
6. copy files on jfs file system
7. edit grub.conf and add jfs kernel argument.
jfs bugs are rejected by bugzilla.
That's Fedora for you. Or rather, I should say, Fedora is not for you, given your expectations from "production" ready.
"Reasonably" safe cutting edge features have always been part of Fedora - be it kernel level mode setting, pulse audio, ext4 in its early days. You are encouraged to file bugs if it makes your system crash. No guarantees that the bug will be fixed, of course.
You had an electromagnetism teacher? That's seriously specific (I was taught that by my adjective teacher).
.
You had an adjective teacher? That is seriously specific. I was taught adjectives by my English teacher, under the "grammar" heading.
Actually a risk has been demonstrated by Boeing
So this could have been the response you should have given, rather than starting to sensationalize the "consequences". Your failing to mention this in your original post suggested that you don't mind that the evidence is anecdotal given the "consequences".
Your "proven conclusively its unsafe" approach would only be appropriate if we were discussing a benefit of substantial value, which we are not.
The post you replied to objected to the evidence being anecdotal. Your reply didn't argue about non-anecdotal evidence there, but you started to harp on the "consequences". My reply was not to "all the arguments you made in your life" but to that single post of yours.
The approach "proven conclusively its unsafe" is not mine, but it is of that post of yours to which I replied. I just used it to reach absurd conclusions to demonstrate the absurdity of the approach.
How is eating an apple weighing between 75.45 and 75.46 grams of substantial value? There are many other apples to choose from, not to mention other food materials.
Has it been proven conclusively that a passenger boarding an aircraft after eating an apple weighing between 75.45 and 75.46 grams does not increase significantly the chance of the aircraft crashing within 46 minutes and 34 seconds of taking off? By your argument, and considering the magnitude of consequences, lets ban apples of the said description.
How about apples weighing between 83.51 grams and 83.52 grams? Pizzas of total carbohydrate content between 31.94 grams and 31.95 grams?
As you say, any actual risk does not have to be demonstrated, just an irrational fear needs to be invoked with sufficient sensationalism.
In fairness, every ad supported app requires network access for downloading apps
Actually, not exactly. App doesn't need to access the network itself, it just calls google's API. Google's API implementation then needs network access. So disabling network access works just fine even if they have to show Android ad framework supported ads.
Only to implement their own ad framework, each app needs its own network access. I don't think that is a good idea anyway.
Your first paragraph seems a re-iteration of your earlier points, second one seems to be trying to give a reason for it. Correct me if I am wrong in this.
1. Nokia never made Symbian.
2. It can be argued that as long as Symbian was relatively independent (48% owned by Nokia, rest by Samsung, SonyEricsson etc), Symbian was doing well. Once under Nokia, not so well. That is when Symbian marketshare started decelerating and then plummeting.
3. "Microsoft has said that they will share the internal details" is completely different from them actually sharing. If a company bases its business model on good faith in Microsoft, God help it.
4. The good coders may not be in Nokia any more after the huge layoffs. Note that blanket layoffs shows enormous disrespect to employees, so even high-performance employees are likely to quit.
5. Nokia has never yet demonstrated their expertise in customizing closed blobs of OS like MS win phone 7 is likely to be.
6. Even if Nokia had demonstrated any such expertise, this is a completely new Nokia from top to bottom. So a repetition of similar success is far from guaranteed.
7. Competitive landscape is a lot different now from "back in the day". Nokia has never demonstrated an ability to survive in a marketplace like today's.
8. Creating a stunning mobile OS is no guarantee of (at least immediate) success as demonstrated by Maemo, HP WebOS, RIM QNX etc. All these OSes got excellent expert reviews, today having negligible market share. Android and iOS, with all their defects, are ruling.
After all these, Nokia's success from "customizing" Win Phone 7 is at best suspect. Far from the certainty you make it out to be.
In 2005, Nokia released (and open-sourced) python for S60. All that Android gains by Dalvik and iOS gains by virtualized objective-C could be gained by python. Software of some respectability could be written in python, and it was trivial to write trivial software right on the phone itself - so much can't be said for Android.
Nokia failed to make it work, that is all.
if Nokia gets a special customise WinPho7 card to play, where does that leave all the other manufacturers? It'll probably leave Nokia as the *only* Windows phone manufacturer
Why is that? HTC (and everyone else) can customize Android, but still there is a market for un-customized Android, as shown by appreciation of Nexus series (though lack of sales channels caused it to not have many users).
Why do you think Nokia customization of Microsoft's OS, without many internal details shared by Microsoft (as MS does to all its desktop/laptop software partners) will undoubtedly be better than stock Windows phone 7? When has Nokia, let alone a Nokia minus thousands of employees, ever shown great expertise to customize a closed OS blob?
Anti-customer is in the very DNA of Sony.
You might find Made in Japan instructive and enjoyable. It is written by a founder of Sony.
He explains how, even in its early days, Sony refused to get into price wars with competing electronics manufacturers. Note that price-war, while reducing corporate profits, are extremely beneficial for customers.
During early days, there was not much demand for Sony items at high prices because those days, Japanese manufacturing was considered inferior to American and European. But Sony refused to let their retailers sell Sony branded items cheap, even if no one was buying them. Logic was that a high price suggests a "premium" product to customers, regardless of quality.
Hey, it used to be $1 wrench in this comic. Inflation finally getting to XKCD?
Yeah, and they call you Creepy!
Yeah, but I guess you have changed the argument. Your original statement was to someone comparing iPhone's openness and Android'd openness. Your statement could only be taken as denying Android's openness. Now you change tack and allege something illegal is going on (which is true in a way, but besides the point here).
iPhone's openness, whatever it is, is by virtue of one unfair advantage (of Apple over AT&T and other carriers) winning over another unfair advantage (of US carriers over US customers). So the openness itself is not open. It could be a temporary victory of one tyrant over another. Android's openness is inherent in product design and license terms. US law enforcement being screwed up, this openness comes at a cost. But in any sensible market environment, it is clearly superior. Even for the US, you would not deny that a sensible market environment is the right way forward rather than a battle of tyrants providing occasional comfort to customers?
So, back on topic, there definitely are Android open phones. Due to carrier prejudice, this openness is expensive, but that is besides the point. Why then, do you say
"When all three carriers lock down the phones designed for their respective networks in undesirable ways, I have the Hobson's choice of doing without." ?
You can "buy" openness if it is worth any money to you. You can buy cheap locked down phones, if that is worth openness to you. Why is it a Hobson's choice? That is like saying you have a Hobson's choice between buying food and staying hungry.
If not committing murder was better than committing murder, they would not need to outlaw murder.
Else you would not need an explicit license for it. Is there no concept of driving license in your country? I am sure it is there in the US.
Another example - running a pharmacy is not a right but a privilege (in my country, at least). For similar reasons.
Irrelevant. GP talking about crime, you talking about evil. These are two different things.
Crime and evil are not antonyms, but very far from synonyms too. Just an example where crime is extremely moral.
The bullocks or horses you call are unlikely to do research for you. Let me try
http://www.askageek.com/2009/08/04/nokia-n79-cellphone-reboots-randomly/
http://discussions.europe.nokia.com/t5/Nseries-and-S60-Smartphones/Reboot-problem-with-N8/td-p/925737
http://discussions.europe.nokia.com/t5/Eseries-and-Communicators/Nokia-E71-Shutdown-and-restarts-automatically/td-p/325797
I have personally seen this on my friend's 5230 : http://discussions.europe.nokia.com/t5/Nseries-and-S60-Smartphones/Nokia-5230-RESTARTING-DEFECT/td-p/635260
HTC - yeah, they have problems. But they release relatively few models so it is easier to figure out.
But half of Nokia models are buggy (other half are excellent). You need to research which ones randomly reboot while in a call, or explode while charging, or their UI freezes when camera is started.
Not only Nokia, but most manufacturers which have a big variety, have this issue. Only Blackberry, HTC, Apple have limited number of models so a simple feature comparison suffices.
After losing about 8 billion dollars over about 10 years?
Nokia need to stick to their simple 12 keys and a monochrome screen for all the parents out there
Nokia failed in that too. 2 reasons
1. Nokia's "release 20 handsets per month in one segment" policy made sure that parents have to research the latest good "parent phone". Research is what parents are worst at. While general handset quality of Nokia is quite good, they often have big duds (some in battery life, some in exploding, keypad quality etc.). So buying Nokia without research never made sense. One dud buy, and the parent swore away from Nokia.
2. Large fonts - Most entry level Nokia phones did / do not have large fonts.