Apple has a history of going off-the-rails when Jobs wasn't involved. Say what you want about him as a person, he was pretty good at figuring out what people wanted and giving it to them just in time for them to figure it out themselves. He also worked with something of a minimalist approach, at times to a fault, but with a great degree of success. Without that restraint this could become a problem.
You mean in the great sample-size of ONE period-of-time that Jobs wasn't in charge?
macOS hardware choice sucks! you can hack it but after each update you may have to re hack it
Mac hardware is much more carefully-spec'ed than you realize.
For about 85-90% of applications, what they offer does just fine. The other 10% usually hack. Apple has obviously accepted that tacit arrangement. They could lock macOS to Apple hardware with ease; but they don't.
"No reasonable person would believe our advertising"
If you think they're actually telling the truth with this $70B figure, I have to say LOL.
If this figure is accurate, then I'll bet this includes the $100/year/dev and whatever cost corporations need to pay for MDM, and the 30% that gets skimmed off... Wouldn't be surprised if it included the hardware (the desktop and phone) that devs have bought. Throw in the cell companies that need to pay APL multimillion dollars to just have their phone on the network.
Of course, this could be just a fake number...
This is royalty payments to App Developers. Nothing more, nothing less.
I'm glad you asked. It's easy to calculate what the average is for those who aren't in the top 1,000.
$70 billion 2.2 million current apps gives 31k per app per 9 years. say 3.5 k per year. Now you have to deduct for apps that used to be in the store but are no more, so let's be generous and say the rate of attrition is 50% over the last 9 years (it's probably much higher). That means the average app makes $1.75 k per year.
So let's be nice again, and say that the top 1,000 apps take 90% of the revenue (it's probably much more). That leaves the 4.4 million apps (we have to include those that are no longer there, remember?) to split $7 billion over 9 years, or $1,509 each over 9 years, which works out to $176 a year.
So, how many apps does the average app developer have to crank out to make $10 an hour ($20,800 per year) for a 40 hour week (260 days, no 2 weeks holiday for YOU!) You would need to crank out 118 apps in 260 working 8-hour days in a year..That's more than 2 apps a day. With no money left for overhead, income tax, etc., and no time or budget for promoting your app or support.
Most app devs are either suckers or they've got a customer who is a sucker.
And remember, this is an average. Half will be making less than $10 an hour pumping out 118 apps a year.
Are you saying you aren't good enough to to write an App that can attain that hypothetical Top 1,000?
Says a bunch of people who never owned one and obviously jealous...
As a multiple Surface Pro owner, they are fantastic machines if you can afford them... Really hoping to get the new Pro before the year is out if I can score a deal similarly to what I paid for my SP3...
ROFL !!!!
Nice try at shamevertising. This isn't Reddit, many here (myself included) can afford as many tech widgets as they desire to have, but choose to spend money on better gear than Surface. Nobody is at all jealous of those. Please try again.
Microsoft Q1-'17 sales for the ENTIRE "Surface"-brand: $831 Million
Apple Q1-'17 sales for the iPad product line: $5.3 BEELION
Apple Q1-'17 sales for the Mac product line: $7.42 BEELION
Believe me, at least some of those people could have bought Surface products instead; but they didn't.
- I already have plenty of expensive and inexpensive headphones - I was in several situations where ability to connect the my phone to the AV system saved the day - Adaptors suck, get lost and may contain a low quality DAC. - Others make phones with a headphone jack, why should I go for the inconvenience of buying one without?
If you are used to working with A/V systems, then you know that Adapters are a way of life.
If your profession is working with A/V systems, you should already be used to keeping track of your adapters.
If you are consistently, or even fairly occasionally, losing adapters, then the problem is not the adapters; but rather it is you. I still have audio adapters I purchased in the mid-1970s, and video adapters from the mid 1980s.
Bottom line: You either keep track of your shit, or you don't. Don't blame the adapters for your lack of discipline.
You're assuming there isn't a good reason. (...) The headphone jack has been causing problems with the placement of components, especially antennas, for years now because the thing is enormous, cutting deep into the device, and has to be on the edge and at one end.
You know what else is enormous and so on? Wheels on cars. We still have them, even though they, together with the wheel wells, ruin the aerodynamics of the car. Levitating cars somehow are less useful. Just because you have good reasons to remove something, it doesn't necessarily make it a good idea.
When Apple dropped the headphone jack, there was nothing to replace it, but other companies inexplicably followed suit.
That's bullshit and you very well know it.
1. Just like the Android "Essential", Apple (wisely) included a Lightning to 3.5 mm analog Headset adapter. So, if you liked your current headphones/earbuds/headset, you could seamlessly continue to use them.
2. Apple also included a Lightning-based headset with the phone. No adapter needed. So, if you disliked using the adapter, you were all set.
So, it sounds like Apple provided not one, but rather TWO replacements for the 3.5 mm headset jack's functional purpose.
As I predicted, more and more mobile devices will be following Apple, Motorola, HTC and others in eschewing the outdated, problematic and technologically-inferior 3.5 mm headphone jack in favor of a digital replacement.
Guess Apple was courageous after all, eh?
Or are people going to fill Slashdot and other online forums with literally thousands of posts crapping on this new "Essential" Android phone for shipping a "dongle" for analog headphone compatibility, too?
Given Apples track record with other OSS projects its more likeley Apple just could not interact well with the upstream project. Im thinking in particular of the KHTML/WebKit fiasco
The "fiasco" that resulted in nearly every single browser switching to WebKit? That one, right?
Tells me that the real problem was with the KHTML Projext, not WebKit.
You can still side load... That's the huge difference...
Banning dropbox and all apps that depend on it because it opens their own website vs closing a security hole while leaving an out (hosting apk any where else)?
Yeah...
This again?!?
You've been able to Sideload, "legally", on iOS devices since iOS 8.
The carriers take stock android and customise it to their requirements. It is then the carriers responsibility to get that sorted out update-wise.
Cheap. Remember cheap. With android's biggest draw being cheap, once that phone is out of most companies hands and into yours, they are done with you. Since cheap rules for Many-most android users, there isn't anyone on the company staff to do the required testing and rollout.
So like so many of my friends who laugh about my "Overpriced Apple shit", and their economical Android Phones, they get a new one every year because the old one is all screwed up. Meanwhile I'm on only my second iPhone.
Same here.
First iPhone was a 4s. Still works, but is "retired." Just stopped getting updates last September, at iOS 9.3.5.
Current phone is a 6 Plus. Will be 3 years old in a few months. Works fine. Gets current OS updates.
"It is then the carriers responsibility to get that sorted out..."
The problem for Google is that abuse by the carriers damages Google's reputation. Most people don't understand all the issues.
Companies should have enough control over their products that they can prevent their products from being used as an instrument of abuse by other companies.
Yup.
Apple did it, why can't others?
Perhaps because they don't give a shit about their customers?
I'm 61 and consistently crank out code around 50-60 hours per week.
Most weekdays, I work a regular workday, sleep for around four hours (bladder won't allow longer), then get up and work another 3 to 5 hours, then crash for another 2 hours before getting back up for work. Then I usually turn in another 4 hours or sometime over the weekend.
Not to be self-aggrandizing; but I have about a 95% "works first time" rate, in case you think I just stumble around for 60 hours a week. And I'm the guy that tends to get all the "I don't even know how you could do that" Projects.
People can try to push those old jokes all they want, but the fact is that Apple did remove the standard 3.5mm headphone jack and they did call it "courage". If the technology to replace something is of lower quality than what it replaces, I don't call it "courage" I call it "stupidity".
How would a digital interface with the chance to use a better DAC than the iPhone has internally be better than an analog interface with a nasty reputation for intermittent behavior?
Slashdot Mirror
Random, possibly with the options weighted by market share.
Oh, great!
So when I say to Alexa, "Order me a laptop", I'm guaranteed to get the shittiest Windows laptop (and ONLY a Windows laptop) there is, right?
Afterall, Windows has be highest Marketshare, right?
Apple has a history of going off-the-rails when Jobs wasn't involved. Say what you want about him as a person, he was pretty good at figuring out what people wanted and giving it to them just in time for them to figure it out themselves. He also worked with something of a minimalist approach, at times to a fault, but with a great degree of success. Without that restraint this could become a problem.
You mean in the great sample-size of ONE period-of-time that Jobs wasn't in charge?
Yeah, some "history".
Lick my balls, pal. If I wanted to be blasted by slang all day, I'd be reading FARK.
Parent is the type that would use curse words in a masters thesis for "flavor."
Apparently, you don't know the difference between slang and a contraction.
macOS hardware choice sucks! you can hack it but after each update you may have to re hack it
Mac hardware is much more carefully-spec'ed than you realize.
For about 85-90% of applications, what they offer does just fine. The other 10% usually hack. Apple has obviously accepted that tacit arrangement. They could lock macOS to Apple hardware with ease; but they don't.
I believe that is exactly why.
Well, how can I make a decent snarky reply, when you have already obviously outclassed me?
Good on you, seriously.
Everyone I know in the game is likewise evaluating alternatives.
I think this is a really exciting time for Linux and BSD.
Or for the only reasonable alternative, macOS.
"No reasonable person would believe our advertising"
If you think they're actually telling the truth with this $70B figure, I have to say LOL.
If this figure is accurate, then I'll bet this includes the $100/year/dev and whatever cost corporations need to pay for MDM, and the 30% that gets skimmed off... Wouldn't be surprised if it included the hardware (the desktop and phone) that devs have bought. Throw in the cell companies that need to pay APL multimillion dollars to just have their phone on the network.
Of course, this could be just a fake number...
This is royalty payments to App Developers. Nothing more, nothing less.
I'm glad you asked. It's easy to calculate what the average is for those who aren't in the top 1,000.
$70 billion 2.2 million current apps gives 31k per app per 9 years. say 3.5 k per year. Now you have to deduct for apps that used to be in the store but are no more, so let's be generous and say the rate of attrition is 50% over the last 9 years (it's probably much higher). That means the average app makes $1.75 k per year.
So let's be nice again, and say that the top 1,000 apps take 90% of the revenue (it's probably much more). That leaves the 4.4 million apps (we have to include those that are no longer there, remember?) to split $7 billion over 9 years, or $1,509 each over 9 years, which works out to $176 a year.
So, how many apps does the average app developer have to crank out to make $10 an hour ($20,800 per year) for a 40 hour week (260 days, no 2 weeks holiday for YOU!) You would need to crank out 118 apps in 260 working 8-hour days in a year..That's more than 2 apps a day. With no money left for overhead, income tax, etc., and no time or budget for promoting your app or support.
Most app devs are either suckers or they've got a customer who is a sucker.
And remember, this is an average. Half will be making less than $10 an hour pumping out 118 apps a year.
Are you saying you aren't good enough to to write an App that can attain that hypothetical Top 1,000?
Oh fuck off, you "you're holding it wrong" cuck.
That's why I keep reading Slashdot: intelligent, erudite Intercourse.
Says a bunch of people who never owned one and obviously jealous...
As a multiple Surface Pro owner, they are fantastic machines if you can afford them... Really hoping to get the new Pro before the year is out if I can score a deal similarly to what I paid for my SP3...
ROFL !!!!
Nice try at shamevertising. This isn't Reddit, many here (myself included) can afford as many tech widgets as they desire to have, but choose to spend money on better gear than Surface. Nobody is at all jealous of those. Please try again.
Microsoft Q1-'17 sales for the ENTIRE "Surface"-brand: $831 Million
Apple Q1-'17 sales for the iPad product line: $5.3 BEELION
Apple Q1-'17 sales for the Mac product line: $7.42 BEELION
Believe me, at least some of those people could have bought Surface products instead; but they didn't.
- I already have plenty of expensive and inexpensive headphones
- I was in several situations where ability to connect the my phone to the AV system saved the day
- Adaptors suck, get lost and may contain a low quality DAC.
- Others make phones with a headphone jack, why should I go for the inconvenience of buying one without?
If you are used to working with A/V systems, then you know that Adapters are a way of life.
If your profession is working with A/V systems, you should already be used to keeping track of your adapters.
If you are consistently, or even fairly occasionally, losing adapters, then the problem is not the adapters; but rather it is you. I still have audio adapters I purchased in the mid-1970s, and video adapters from the mid 1980s.
Bottom line: You either keep track of your shit, or you don't. Don't blame the adapters for your lack of discipline.
You're assuming there isn't a good reason. (...) The headphone jack has been causing problems with the placement of components, especially antennas, for years now because the thing is enormous, cutting deep into the device, and has to be on the edge and at one end.
You know what else is enormous and so on? Wheels on cars. We still have them, even though they, together with the wheel wells, ruin the aerodynamics of the car. Levitating cars somehow are less useful. Just because you have good reasons to remove something, it doesn't necessarily make it a good idea.
What a moronic argument.
When Apple dropped the headphone jack, there was nothing to replace it, but other companies inexplicably followed suit.
That's bullshit and you very well know it.
1. Just like the Android "Essential", Apple (wisely) included a Lightning to 3.5 mm analog Headset adapter. So, if you liked your current headphones/earbuds/headset, you could seamlessly continue to use them.
2. Apple also included a Lightning-based headset with the phone. No adapter needed. So, if you disliked using the adapter, you were all set.
So, it sounds like Apple provided not one, but rather TWO replacements for the 3.5 mm headset jack's functional purpose.
As I predicted, more and more mobile devices will be following Apple, Motorola, HTC and others in eschewing the outdated, problematic and technologically-inferior 3.5 mm headphone jack in favor of a digital replacement.
Guess Apple was courageous after all, eh?
Or are people going to fill Slashdot and other online forums with literally thousands of posts crapping on this new "Essential" Android phone for shipping a "dongle" for analog headphone compatibility, too?
A long time ago, a friend I respected told me, "Love the Mac, hate Apple." Apple had its own methods of abuse.
Name Three.
Wrong. Apple switched because Samba changed its license to GPLv3.
So, if that's the real reason, that means that most Slashdotters would agree with Apple's decision to go their own way, right?
Given Apples track record with other OSS projects its more likeley Apple just could not interact well with the upstream project. Im thinking in particular of the KHTML/WebKit fiasco
The "fiasco" that resulted in nearly every single browser switching to WebKit? That one, right?
Tells me that the real problem was with the KHTML Projext, not WebKit.
You can still side load... That's the huge difference...
Banning dropbox and all apps that depend on it because it opens their own website vs closing a security hole while leaving an out (hosting apk any where else)?
Yeah...
This again?!?
You've been able to Sideload, "legally", on iOS devices since iOS 8.
You don't even need a Mac to do it.
The carriers take stock android and customise it to their requirements. It is then the carriers responsibility to get that sorted out update-wise.
Cheap. Remember cheap. With android's biggest draw being cheap, once that phone is out of most companies hands and into yours, they are done with you. Since cheap rules for Many-most android users, there isn't anyone on the company staff to do the required testing and rollout.
So like so many of my friends who laugh about my "Overpriced Apple shit", and their economical Android Phones, they get a new one every year because the old one is all screwed up. Meanwhile I'm on only my second iPhone.
Same here.
First iPhone was a 4s. Still works, but is "retired." Just stopped getting updates last September, at iOS 9.3.5.
Current phone is a 6 Plus. Will be 3 years old in a few months. Works fine. Gets current OS updates.
"It is then the carriers responsibility to get that sorted out..."
The problem for Google is that abuse by the carriers damages Google's reputation. Most people don't understand all the issues.
Companies should have enough control over their products that they can prevent their products from being used as an instrument of abuse by other companies.
Yup.
Apple did it, why can't others?
Perhaps because they don't give a shit about their customers?
I'm 61 and consistently crank out code around 50-60 hours per week.
Most weekdays, I work a regular workday, sleep for around four hours (bladder won't allow longer), then get up and work another 3 to 5 hours, then crash for another 2 hours before getting back up for work. Then I usually turn in another 4 hours or sometime over the weekend.
Not to be self-aggrandizing; but I have about a 95% "works first time" rate, in case you think I just stumble around for 60 hours a week. And I'm the guy that tends to get all the "I don't even know how you could do that" Projects.
People can try to push those old jokes all they want, but the fact is that Apple did remove the standard 3.5mm headphone jack and they did call it "courage". If the technology to replace something is of lower quality than what it replaces, I don't call it "courage" I call it "stupidity".
How would a digital interface with the chance to use a better DAC than the iPhone has internally be better than an analog interface with a nasty reputation for intermittent behavior?
Maybe if apple didn't want to be laughed at it wouldn't say and do such stupid things.
You mean like releasing a computer with no floppy and no serial or parallel ports in 1998? ...or releasing a phone with no keyboard?
Yeah, they were sure proven wrong there...
Opera had tabbed browsing really early on. It used to be pretty fast compared to everything, too. It had its day in the sun.
I think it had a spotless record as far as exploits go, too.
I never liked it; but there's something to be said for no exploits, ever...
Several years ago, Apple stopped including SAMBA in OS X, and instead developed their own SMB protocol stack from scratch.
At the time, it seemed like an odd move for an OS that already contained many F/OSS Projects.
But maybe they knew something that made them feel like it wasn't a salvageable Project...