No chance Apple will have more than two standalone computers. The "desktop" in the middle will never happen, because there is so little perceived market for it.
The mini is meant to be a computer for switchers - "Not willing to pay for an iMac with a nice new screen/keyboard/mouse? Get the Mini and supply your own." It was never meant to be the pro/workstation substitute it has been in the dearth of Mac Pro releases. I could see the Mini switching to a lower TDP processor in its next rev.
And unfortunately, I expect a Mac Pro pricing to start past where the (non-Pro) iMac pricing ends - I'd be shocked if they had a baseline model at $2499.
It might be in a few years - effectively as an eGPU, to deal with being detached from system memory.
Software is not optimized for the latency and DMA cost of eGPUs yet enough to make this a viable default. I'd also worry about the heat affecting the screen.
Windows 98 Era PCs on the internet? I am shocked that is even possible!
I've seen unpatched windows xp machines completely break down due to the volume of competing viruses on them, and forgetting the open networking they haven't gotten a modern browser update in what, a decade?
I contested the latter point, but it turns out it doesn't matter, because it's still not (by Apple's own admission) fixed in the 3rd gen.
That is a misinterpretation. Apple said the design didn't change to resolve any keyboard reliability issues, because they haven't said the previous generation had any design issues affecting reliability (and won't unless compelled by law).
1) The Mac Mini and Mac Pro haven't seen a meaningful update in years and basically get ignored 2) The Mac Pro design is stupid and needs to be fixed ASAP
Apple has announced they are working on the Mac Pro and why the current model stagnated. They also released a new pro machine December, the iMac Pro. This very article is talking about a Mac mini update, and it was nicely put in the summary for those who didn't want to read the article
3) Apple still can't get seamless integration between their operating systems and devices for files and data
In what way? App data integration and iCloud Drive are pretty darn seamless.
4) Apple still doesn't have a decent application for proper note taking with the Apple Pencil
Its called "Notes", or do you have a particular qualm?
5) It's time for the lightning connector to die in a fire and be replaced with USB-C
Half right - they'll kill lightning connectors and replace them with wireless charging/accessories.
6) Apple needs more than a single USB-C port on certain of their laptops
It'd be nice, although surprisingly only an actual blocker once in two years worth of ownership of said model.
7) Dongle hell
Buy USB-C cables from Monoprice if this is an issue.
8) Apple Pay still not accepted enough places
Blame the members of the Merchant Customer Exchange (MCX).
9) Apple Pencil is a total afterthought with basically no useful software support unless you are a digital artist focused on the iPad (useless on a Mac)
So its an optional accessory?
10) Apple treats cases for their phones as an afterthought rather than an important part of the device despite nearly every customer buying one
I have no idea what your complaint is here
11) iPhones can have a power cord or a wired headset attached but not both at the same time.
Best to avoid 8+ hour conference calls on your phone then. Or if this is a legitimate problem, there are numerous accessories.
12) Apple Maps still lags behind Google's offerings
This will likely always be the case, as Google plans for maps to be a direct profit center via advertisements. But both are well above "good enough" at this point.
13) Apple is ignoring equipment for serious artists (why don't they buy Wacom?)
Because the sales volume would be so low that it would just serve as a distraction? It would be an accessory that only 1% of Mac users would want, where the Mac makes up 10% of their business.
They don't even sell first party monitors anymore, farming that off to LG.
14) It's still unclear what Apple's next Big Thing will be. To grow the company they can't coast on the iPhone forever.
The list goes on and on. Apple does a lot of things right but they could be doing so much more/better.
Part of Apple's corporate culture is to not tell people what they are planning their next Big Thing to be. Look for existing products with widespread potential appeal being underserved by some/all of the existing manufacturers for their ideal targets.
basically, they couldn't upgrade to the new Intel CPUs because their design just wouldn't be able to handle the heat.
I believe it was the GPUs, not CPU - CPU TDP has stayed pretty steady (and as a result, performance has been pretty stagnant). T the GPU complexity has been continuing to go up, bringing lots more heat.
It has a prerequisite of TLS, so it is as susceptible as TLS is. If the browser accepts a fraudulently issued certificate, that fraudulent site can coordinate with the legitimate site to MITM you. This is a common weakness of TLS, and one of the reasons the browser/OS vendors have been ratcheting up their requirements for CA processes and certificate transparency.
The individual public key credentials which are issued as part of webauthn are basically scoped to the relying party website, so paypalonline.com has little hope to get a credential usable on paypal.com.
It does leverage a newer feature of TLS called token binding. With this, you can "bind" sessions cookies, oauth tokens, etc to the browser TLS. Even if the cookies/tokens accidentally leak to a malicious party, they won't be able to be used since they can't duplicate the TLS session.
Sure, although they may have not known the side-effects of what they were doing (breaking phones that use unofficial parts that apple has never tested and doesn't qualify).
The system will attempt to upgrade the boot drive with High Sierra to APFS automatically if it is an SSD. Any other hard disk (SSD or not) will not be automatically updated, but can be updated easily from Disk Utility.
If it were an 'official' successor, it would have an Apple logo on it. Apple pushed LG to make a thunderbolt 3 monitor, in turn for carrying them at apple stores and mentioning them during a keynote. Hardly 'official'.
The confusion comes in that both Airplay and the Lightning adapter use the platform H.264 encoding to stream the video. The iPad Mini they were testing couldn't handle 1080p MPEG encoding in hardware - but it would stream 1080p pre-encoded video just fine, for instance - it isn't a limitation of the cable throughput.
value types are always passed by copying. An inout parameter means "copy to pass in, copy to pass out, assign to original variable" - but the compiler is free to optimize that.
Swift strings are value types, just like C++ or C#. The value type contains a reference to the string text. (Ok, libc++ in llvm will actually tag the pointers on 64 bit platforms to stuff small strings *into* the struct directly, but I digress)
Swift strings are copy on write, where the reference count is used to determine if you possess a unique reference to the string before mutation. This is similar to how libstdc++ works, or at least used to work.
I believe C++ libraries have been migrating away from CoW strings because of the atomicity costs of the reference counting. Swift, maintaining compatibility with Objective C, already needed to have support for ref-counted strings.
So it was a different trade-off - the ref-counted Swift strings can be bridged to Objective C, while a non-reference-counted string would need to be copied. If they make the decision to have reference counted strings to make the interoperability faster, then they might as well add CoW support to make them more efficient/faster in other cases.
I am insulted when I tell guests to grab anything they want out of my fridge and they then ask if I have pop.
Sounds like you have an issue if you tell them to grab anything they want, and then you get upset if what they want is pop. Perhaps you should phrase your offer differently
Three apple platforms now: iOS, Mac OS X and watchOS.
Swift has had a lot of up-front design decisions made to ease what will be a long transition from objective C - methods with named parameters to match Objective C rules, the ability to see if you have a single reference (a feature of reference counting) is a feature needed to optimize string and collection types, so use in a non-reference-counted system would be a pain. Also things like the error model are quite different.
This would make it more difficult to compile to java/dalvik byte code or.Net CIL (java/dalvik being way harder). This does not preclude native compilation via the open-source compiler and bridging.
While Apple audited their APIs to make sure their API bridging generator worked well and created nice APIs everywhere, and even added some language features to Objective C to fill in the gaps, a third party like Google or Microsoft would not have such 'guided' translation - they would need to design Swift-like APIs to expose.
Slashdot Mirror
Apple has since fixed it, but there was a little icon on their page with a 'pi' symbol on it, he must have found that and clicked on it.
They were primarily acquired via Java and Flash through IE, IIRC. I don't believe IE was sandboxed until Vista.
No chance Apple will have more than two standalone computers. The "desktop" in the middle will never happen, because there is so little perceived market for it.
The mini is meant to be a computer for switchers - "Not willing to pay for an iMac with a nice new screen/keyboard/mouse? Get the Mini and supply your own." It was never meant to be the pro/workstation substitute it has been in the dearth of Mac Pro releases. I could see the Mini switching to a lower TDP processor in its next rev.
And unfortunately, I expect a Mac Pro pricing to start past where the (non-Pro) iMac pricing ends - I'd be shocked if they had a baseline model at $2499.
It might be in a few years - effectively as an eGPU, to deal with being detached from system memory.
Software is not optimized for the latency and DMA cost of eGPUs yet enough to make this a viable default. I'd also worry about the heat affecting the screen.
Windows 98 Era PCs on the internet? I am shocked that is even possible!
I've seen unpatched windows xp machines completely break down due to the volume of competing viruses on them, and forgetting the open networking they haven't gotten a modern browser update in what, a decade?
I contested the latter point, but it turns out it doesn't matter, because it's still not (by Apple's own admission) fixed in the 3rd gen.
That is a misinterpretation. Apple said the design didn't change to resolve any keyboard reliability issues, because they haven't said the previous generation had any design issues affecting reliability (and won't unless compelled by law).
1) The Mac Mini and Mac Pro haven't seen a meaningful update in years and basically get ignored
2) The Mac Pro design is stupid and needs to be fixed ASAP
Apple has announced they are working on the Mac Pro and why the current model stagnated. They also released a new pro machine December, the iMac Pro. This
very article is talking about a Mac mini update, and it was nicely put in the summary for those who didn't want to read the article
3) Apple still can't get seamless integration between their operating systems and devices for files and data
In what way? App data integration and iCloud Drive are pretty darn seamless.
4) Apple still doesn't have a decent application for proper note taking with the Apple Pencil
Its called "Notes", or do you have a particular qualm?
5) It's time for the lightning connector to die in a fire and be replaced with USB-C
Half right - they'll kill lightning connectors and replace them with wireless charging/accessories.
6) Apple needs more than a single USB-C port on certain of their laptops
It'd be nice, although surprisingly only an actual blocker once in two years worth of ownership of said model.
7) Dongle hell
Buy USB-C cables from Monoprice if this is an issue.
8) Apple Pay still not accepted enough places
Blame the members of the Merchant Customer Exchange (MCX).
9) Apple Pencil is a total afterthought with basically no useful software support unless you are a digital artist focused on the iPad (useless on a Mac)
So its an optional accessory?
10) Apple treats cases for their phones as an afterthought rather than an important part of the device despite nearly every customer buying one
I have no idea what your complaint is here
11) iPhones can have a power cord or a wired headset attached but not both at the same time.
Best to avoid 8+ hour conference calls on your phone then. Or if this is a legitimate problem, there are numerous accessories.
12) Apple Maps still lags behind Google's offerings
This will likely always be the case, as Google plans for maps to be a direct profit center via advertisements. But both are well above "good enough" at this point.
13) Apple is ignoring equipment for serious artists (why don't they buy Wacom?)
Because the sales volume would be so low that it would just serve as a distraction? It would be an accessory that only 1% of Mac users would want, where the Mac makes up 10% of their business.
They don't even sell first party monitors anymore, farming that off to LG.
14) It's still unclear what Apple's next Big Thing will be. To grow the company they can't coast on the iPhone forever.
The list goes on and on. Apple does a lot of things right but they could be doing so much more/better.
Part of Apple's corporate culture is to not tell people what they are planning their next Big Thing to be. Look for existing products with widespread potential appeal being underserved by some/all of the existing manufacturers for their ideal targets.
basically, they couldn't upgrade to the new Intel CPUs because their design just wouldn't be able to handle the heat.
I believe it was the GPUs, not CPU - CPU TDP has stayed pretty steady (and as a result, performance has been pretty stagnant). T the GPU complexity has been continuing to go up, bringing lots more heat.
It has a prerequisite of TLS, so it is as susceptible as TLS is. If the browser accepts a fraudulently issued certificate, that fraudulent site can coordinate with the legitimate site to MITM you. This is a common weakness of TLS, and one of the reasons the browser/OS vendors have been ratcheting up their requirements for CA processes and certificate transparency.
The individual public key credentials which are issued as part of webauthn are basically scoped to the relying party website, so paypalonline.com has little hope to get a credential usable on paypal.com.
It does leverage a newer feature of TLS called token binding. With this, you can "bind" sessions cookies, oauth tokens, etc to the browser TLS. Even if the cookies/tokens accidentally leak to a malicious party, they won't be able to be used since they can't duplicate the TLS session.
You can use a PIN/passcode, but the client software on the computer is the UX for it - Firefox in this case, the operating system in others.
iTunes.
Sure, although they may have not known the side-effects of what they were doing (breaking phones that use unofficial parts that apple has never tested and doesn't qualify).
Pretty good, but needed more lens flares
The system will attempt to upgrade the boot drive with High Sierra to APFS automatically if it is an SSD. Any other hard disk (SSD or not) will not be automatically updated, but can be updated easily from Disk Utility.
Blipverts
If it were an 'official' successor, it would have an Apple logo on it. Apple pushed LG to make a thunderbolt 3 monitor, in turn for carrying them at apple stores and mentioning them during a keynote. Hardly 'official'.
Not true and not true.
The confusion comes in that both Airplay and the Lightning adapter use the platform H.264 encoding to stream the video. The iPad Mini they were testing couldn't handle 1080p MPEG encoding in hardware - but it would stream 1080p pre-encoded video just fine, for instance - it isn't a limitation of the cable throughput.
value types are always passed by copying. An inout parameter means "copy to pass in, copy to pass out, assign to original variable" - but the compiler is free to optimize that.
Swift strings are value types, just like C++ or C#. The value type contains a reference to the string text. (Ok, libc++ in llvm will actually tag the pointers on 64 bit platforms to stuff small strings *into* the struct directly, but I digress)
Swift strings are copy on write, where the reference count is used to determine if you possess a unique reference to the string before mutation. This is similar to how libstdc++ works, or at least used to work.
I believe C++ libraries have been migrating away from CoW strings because of the atomicity costs of the reference counting. Swift, maintaining compatibility with Objective C, already needed to have support for ref-counted strings.
So it was a different trade-off - the ref-counted Swift strings can be bridged to Objective C, while a non-reference-counted string would need to be copied. If they make the decision to have reference counted strings to make the interoperability faster, then they might as well add CoW support to make them more efficient/faster in other cases.
SAML, using TV Everywhere
How on earth would you expect a macbook to have a gig-E port?
Seriously, where would you put it?
Unlike in the US where taxes are separate, GST (10%) is included in the app store price.
$0.99 US pre-tax + 10% GST = $1.089 US post-tax
currently $1 US = 1.3713 AUD
so $1.089 US = 1.4933457 AUD
So Aussies are in fact getting a $0.0033457 AUD discount over the US.
I am insulted when I tell guests to grab anything they want out of my fridge and they then ask if I have pop.
Sounds like you have an issue if you tell them to grab anything they want, and then you get upset if what they want is pop. Perhaps you should phrase your offer differently
I prefer PLOW, the Platform, Language, Operating system and Web server stack.
Three apple platforms now: iOS, Mac OS X and watchOS.
Swift has had a lot of up-front design decisions made to ease what will be a long transition from objective C - methods with named parameters to match Objective C rules, the ability to see if you have a single reference (a feature of reference counting) is a feature needed to optimize string and collection types, so use in a non-reference-counted system would be a pain. Also things like the error model are quite different.
This would make it more difficult to compile to java/dalvik byte code or .Net CIL (java/dalvik being way harder). This does not preclude native compilation via the open-source compiler and bridging.
While Apple audited their APIs to make sure their API bridging generator worked well and created nice APIs everywhere, and even added some language features to Objective C to fill in the gaps, a third party like Google or Microsoft would not have such 'guided' translation - they would need to design Swift-like APIs to expose.
Its possible, but not close to free.