I don't know about the rest of your post, but this is nonsense:
There are also concerns about prematurely wearing out flash. The problem is that flash rewrite life estimates are based upon general use of the entire block of memory... but a swap partition gets created in a specific chunk of flash, and that one tiny chunk gets relentlessly hammered.
Flash does not work like a hard disk. Flash has wear leveling, and it works at the block level. Ever time a block is written to, it uses a different physical block in the flash. Regardless of wether the block happens to be part of a swap file or any other kind of file. "One tiny chunk" never gets "hammered".
Slow phones are slow, fast ones are fast, and occasionally things stick on Android, but no more than on comparably priced hardware using "the other" platform.
A statement for which you have no evidence. But you say it hoping it's true.
With multiple cash registers then of course you get a receipt. If your sale is rung up on register A then you get a receipt and it's reported for the taxman. If your sale is rung up on register B then you get a receipt but it's never reported to the taxman.
And there's nothing wrong with having multiple registers. Plenty of shops do. Any shop that has several cashiers for example.
The only tax rate that is so low people won't bother cheating is 0%. A bit like software piracy - we see that people will still hack and pirate apps even when the price is as low as 99c.
Spending reductions are the first and best measure - tax revenues go UP when rates go down.
Right after you mention the Laffer curve. Of course the Laffer curve doesn't say that. Only above a certain rate is that true. Below that rate tax revenues go down when rates go down.
What's that rate? Nobody knows, because the Laffer curve is only a concept. No one can draw a chart of it. Economics are far too complex to be encapsulated by it.
and they will do so beyond any point where you would have made your case to someone with an open mind.
Where are these people with an open mind? They certainly don't frequent internet comment areas. Heck, look at Slashdot - It's cause for celebration once every 6 months or so when someone actually says: "Yes, good point, you've changed my opinion." Other than that, it's just contradiction.
More manufacturers wanting to differenciate themselves from the rest means also more diversity on the software front. Thats from where Sailfish, Tizen, Firefox OS, and even Open Web OS phones will come.
So far it just seems to mean an ever more fragmented Android.
It's caused by a combination of several factors. Including all the ones in TFS. Several of which affect wealthy people too.
Mostly it comes down to this: American corporation prioritise profit over health. Because of lobbying and campaign contributions (bribes), the US government represents the interests of corporations more than people. And much of the American population has been brainwashed by the media corporations to believe that's a good thing. Everything else follows from that.
Conclusion 2: limited availability of contraception for teenagers causes it. WTF? This may indirectly contribute to more people in the world, but how does it affect the life expectancy of those teenager's babies or anybody else?
You seem to be unaware that condoms don't just protect against babies, they also protect against STDs, including AIDS. Perhaps you're Catholic...?
Doing fix it now on type (c) Seems like a recipe for chaos. A distraction. I'm working on one particular feature or bug, and I've got my SCM state set up so I can encapsulate just that one thing in a branch or a specific commit. You're suggesting I switch my mind and SCM state to this newly spotted thing, fix it, submit it and then come back? But then the weekend intervenes and I'm... where am I exactly?
And even if it goes perfectly, have I been spending my time wisely? Was that newly spotted bug a high priority, urgent job, or a low priority, non time-critical job?
Far better just to submit a bug report, and deal with it when it comes to the top of the list as the most important thing to do.
Further, I'd suggest that that is sometimes what to do with issues of type (b) too. Simply make the error you're not yet handling into an abort, or a a log message, and file a bug report on it.
It goes far wider than coding. I'm basically suggesting that a prioritised to-do list is far better than the fire-fighting approach of trying to deal with things when you see them.
a) I write some code and it doesn't work. So I fix it now? b) I write some code and it works, but there's an error state I haven't covered, so I fix it now? c) I write some code and notice a defect in some other code, so I fix it now?
Meanwhile, I notice that both Samsung and Google filed more patents than Apple. Funny how the Slashdot hive-mind would have you believe that Apple is the one that's claiming too many patents.
Almost as funny as finding out a couple of weeks ago that Samsung spends 10 times as much as Apple on marketing.
True enough, but I know a LOT of iphone users -- one of the companies I work with is a cell phone dealer
You're still overestimating the people that are similar to you. Because the people surrounding you, in your circles of work and socialising, will tend to be a bit like you. But you're not accounting for the people in entirely different kinds of work, of radically different ages, working in countries other than your own, with different wealth and different values.
People do, always, think there are more people with similar views to themselves than is actually the case.
When a statistic comes along, it's OK to be sceptical. To go and research other stats for comparison. But disbelieving a stat because it doesn't match your own experience is wrong-headed. It's mistaking anecdote for data.
Is this more true of apps than of, for example, movies? I was under the impression that several critically acclaimed movies still didn't make a profit.
I'm way ahead of you. As I said there are many ways to define good/bad, and so I defined what I meant by it. And it was apps that people tend to want to use for a long time. Not that reviewers said it was good.
(OT: You want to take claimed lack of profit on movies with a pinch of salt. Very often that's an accountancy trick to lower costs such as royalties. For example the studio tried to claim that none of the LOTR movies made a profit. Of course they did. Why the hell else would they have moved on to making The Hobbit.)
But how does an app get in front of a widely followed reviewer in the first place?
You send it to them. A proportion will pick it up. Meanwhile user reviews on the App Store count for a lot.
It's not random. It's not a game of chance. It's a game of skill - primarily in developing a good app. Secondarily in doing competent marketing.
And that's great. For people who want to tinker about creating or adapting programs for a hobby, the RPi seems like a great, simpl(ish) and cheap way.
Personally I got a lot of enjoyment from programming the Propeller based Hydra board a few years ago. I'm sure a lot more fun than I'd have with the RPi, but that's a taste based thing. And the Hydra costs about 6 times the price.
Why do people that don't like Apple bitch when Apple doesn't serve a particular market?
Maybe one day Apple TV will have apps. But it's still not the same market. Such apps will be commercial apps available from the App Store. It'd compete with consoles and set top boxes. It won't ever be a device intended for hobby coders.
That might be the contention, but it's wrong. GIven the same decent marketing, a bad app will still not be successful, whilst a good app will be. That's a game of skill.
Of course there can be many ways of defining bad and good apps. Most of them subjective. So for the purposes of this I'll say a bad app is one which people typically use for long enough to see what it is, then abandon it. And a good app is one that people keep on using for a long time.
Good apps predominantly get good reviews, bad ones get bad reviews. Both on store and off store. People see other people running good apps, and get personal recommendations for them. Not bad apps.
You left "targetting" out of the quote and replaced it with your own word "opinion".
Lets be clear, this game is no editorial. It's simply a game with the objective of freedom fighters/terrorists beating Assad. No discussion; no alternative ways of making a decent country. No, the simple objective is to beat Assad.
That's an item of propaganda, not editorial content. It implies that it's a good thing to depose the Assad government without any discussion or evidence of why.
It comes far closer than "targetting" than giving an "opinion".
Slashdot Mirror
I don't know about the rest of your post, but this is nonsense:
There are also concerns about prematurely wearing out flash. The problem is that flash rewrite life estimates are based upon general use of the entire block of memory... but a swap partition gets created in a specific chunk of flash, and that one tiny chunk gets relentlessly hammered.
Flash does not work like a hard disk. Flash has wear leveling, and it works at the block level. Ever time a block is written to, it uses a different physical block in the flash. Regardless of wether the block happens to be part of a swap file or any other kind of file. "One tiny chunk" never gets "hammered".
Slow phones are slow, fast ones are fast, and occasionally things stick on Android, but no more than on comparably priced hardware using "the other" platform.
A statement for which you have no evidence. But you say it hoping it's true.
And when the taxman comes back 3 days later and asks the shop owner for the matching receipt from their register what happens then?
They supply it. and then know that that particular days sales of register B will need to be included in their tax return.
then you don't get a receipt.
With multiple cash registers then of course you get a receipt. If your sale is rung up on register A then you get a receipt and it's reported for the taxman. If your sale is rung up on register B then you get a receipt but it's never reported to the taxman.
And there's nothing wrong with having multiple registers. Plenty of shops do. Any shop that has several cashiers for example.
The only tax rate that is so low people won't bother cheating is 0%. A bit like software piracy - we see that people will still hack and pirate apps even when the price is as low as 99c.
Spending reductions are the first and best measure - tax revenues go UP when rates go down.
Right after you mention the Laffer curve. Of course the Laffer curve doesn't say that. Only above a certain rate is that true. Below that rate tax revenues go down when rates go down.
What's that rate? Nobody knows, because the Laffer curve is only a concept. No one can draw a chart of it. Economics are far too complex to be encapsulated by it.
and they will do so beyond any point where you would have made your case to someone with an open mind.
Where are these people with an open mind? They certainly don't frequent internet comment areas. Heck, look at Slashdot - It's cause for celebration once every 6 months or so when someone actually says: "Yes, good point, you've changed my opinion." Other than that, it's just contradiction.
(The full half hour).
Well then you have to define reasonable.
How about "Either fix it or report it now".
More manufacturers wanting to differenciate themselves from the rest means also more diversity on the software front. Thats from where Sailfish, Tizen, Firefox OS, and even Open Web OS phones will come.
So far it just seems to mean an ever more fragmented Android.
vanilla Android
That must be Ice Cream Sandwich. Typical Android phone, ships with an old OS version.
Samsung is not successful because they have high quality phones. They are successful because they spend so much on marketing.
Fair enough. So probably better to say "report it now" rather than "fix it now".
It's caused by a combination of several factors. Including all the ones in TFS. Several of which affect wealthy people too.
Mostly it comes down to this:
American corporation prioritise profit over health. Because of lobbying and campaign contributions (bribes), the US government represents the interests of corporations more than people. And much of the American population has been brainwashed by the media corporations to believe that's a good thing. Everything else follows from that.
Conclusion 2: limited availability of contraception for teenagers causes it. WTF? This may indirectly contribute to more people in the world, but how does it affect the life expectancy of those teenager's babies or anybody else?
You seem to be unaware that condoms don't just protect against babies, they also protect against STDs, including AIDS. Perhaps you're Catholic...?
Doing fix it now on type (c) Seems like a recipe for chaos. A distraction. I'm working on one particular feature or bug, and I've got my SCM state set up so I can encapsulate just that one thing in a branch or a specific commit. You're suggesting I switch my mind and SCM state to this newly spotted thing, fix it, submit it and then come back? But then the weekend intervenes and I'm... where am I exactly?
And even if it goes perfectly, have I been spending my time wisely? Was that newly spotted bug a high priority, urgent job, or a low priority, non time-critical job?
Far better just to submit a bug report, and deal with it when it comes to the top of the list as the most important thing to do.
Further, I'd suggest that that is sometimes what to do with issues of type (b) too. Simply make the error you're not yet handling into an abort, or a a log message, and file a bug report on it.
It goes far wider than coding. I'm basically suggesting that a prioritised to-do list is far better than the fire-fighting approach of trying to deal with things when you see them.
What is meant by "fix it now"?
a) I write some code and it doesn't work. So I fix it now?
b) I write some code and it works, but there's an error state I haven't covered, so I fix it now?
c) I write some code and notice a defect in some other code, so I fix it now?
Tell whoever is still running those versions that they are no longer supported.
They all claim it's for a defensive position.
Meanwhile, I notice that both Samsung and Google filed more patents than Apple. Funny how the Slashdot hive-mind would have you believe that Apple is the one that's claiming too many patents.
Almost as funny as finding out a couple of weeks ago that Samsung spends 10 times as much as Apple on marketing.
True enough, but I know a LOT of iphone users -- one of the companies I work with is a cell phone dealer
You're still overestimating the people that are similar to you. Because the people surrounding you, in your circles of work and socialising, will tend to be a bit like you. But you're not accounting for the people in entirely different kinds of work, of radically different ages, working in countries other than your own, with different wealth and different values.
People do, always, think there are more people with similar views to themselves than is actually the case.
When a statistic comes along, it's OK to be sceptical. To go and research other stats for comparison. But disbelieving a stat because it doesn't match your own experience is wrong-headed. It's mistaking anecdote for data.
Those engineers and architects are employers or contractors of the bridge's developer. Yes they only get paid once.
Just like computer programmers who are employees or contractors of software developers only get paid once.
But the developer of a bridge, who creates it for himself and owns it, keeps on getting paid tolls.
Just like the software developer. Be it the boss of a company, or an indy working on his own.
The two industries are indeed similar.
Actually cheating on paying tolls is not a bad analogy for software piracy.
MANY linux users and developers are gun enthusiasts.
It's the perfect combination: gun nuts and freetards.
Is this more true of apps than of, for example, movies? I was under the impression that several critically acclaimed movies still didn't make a profit.
I'm way ahead of you. As I said there are many ways to define good/bad, and so I defined what I meant by it. And it was apps that people tend to want to use for a long time. Not that reviewers said it was good.
(OT: You want to take claimed lack of profit on movies with a pinch of salt. Very often that's an accountancy trick to lower costs such as royalties. For example the studio tried to claim that none of the LOTR movies made a profit. Of course they did. Why the hell else would they have moved on to making The Hobbit.)
But how does an app get in front of a widely followed reviewer in the first place?
You send it to them. A proportion will pick it up. Meanwhile user reviews on the App Store count for a lot.
It's not random. It's not a game of chance. It's a game of skill - primarily in developing a good app. Secondarily in doing competent marketing.
Downside: The McDonalds Raspberry Pi would run too hot.
Upside: You could sue them!
And that's great. For people who want to tinker about creating or adapting programs for a hobby, the RPi seems like a great, simpl(ish) and cheap way.
Personally I got a lot of enjoyment from programming the Propeller based Hydra board a few years ago. I'm sure a lot more fun than I'd have with the RPi, but that's a taste based thing. And the Hydra costs about 6 times the price.
Why do people that don't like Apple bitch when Apple doesn't serve a particular market?
Maybe one day Apple TV will have apps. But it's still not the same market. Such apps will be commercial apps available from the App Store. It'd compete with consoles and set top boxes. It won't ever be a device intended for hobby coders.
That might be the contention, but it's wrong. GIven the same decent marketing, a bad app will still not be successful, whilst a good app will be. That's a game of skill.
Of course there can be many ways of defining bad and good apps. Most of them subjective. So for the purposes of this I'll say a bad app is one which people typically use for long enough to see what it is, then abandon it. And a good app is one that people keep on using for a long time.
Good apps predominantly get good reviews, bad ones get bad reviews. Both on store and off store. People see other people running good apps, and get personal recommendations for them. Not bad apps.
None of these things happen in a game of chance.
You left "targetting" out of the quote and replaced it with your own word "opinion".
Lets be clear, this game is no editorial. It's simply a game with the objective of freedom fighters/terrorists beating Assad. No discussion; no alternative ways of making a decent country. No, the simple objective is to beat Assad.
That's an item of propaganda, not editorial content. It implies that it's a good thing to depose the Assad government without any discussion or evidence of why.
It comes far closer than "targetting" than giving an "opinion".