Then why even consider buying Macs in the first place?
I'll probably buy the next iMac for home use. Email and such. But the nMP on my desk has been a disappointment and will be my last Mac for work uses.
Then why even consider buying Macs in the first place?
For Apple? You use what Apple dictates to you. For every other platform you use what works best for your application. Simple...eh?What do you use on Apple when ALL workloads will use Metal on Apple platform?
Have you ever thought about that?
This is an excellent point. If Apple doesn't provide direction on the Mac Pro (either with regular releases or communication) pro application developers may decide to move away from the platform. If I were the developer of a pro application I'd have to think hard about why I would continue to support a platform which hasn't seen an update in so long.Windows? It's not likely that many cross-platform software developers will waste time porting to yet another soon-to-be-abandoned API pushed by Apple.
OSX is in this akward place where it has enough market share for developers to think about supporting it, but not enough that they have to, and not enough to influence industry-wide trends. Especially when the environment (apple) is so hostile to 3rd party development.
Just like Apple invested a lot of R&D in:
With that history, would you invest in rewriting your software (yet again) to suit the latest "API of the week" from Apple?
- Just like Apple invested a lot of R&D in Pink - what became of that?
- Just like Apple invested a lot of R&D in Copland - what became of that?
- Just like Apple invested a lot of R&D in Rhapsody - what became of that?
- Just like Apple invested a lot of R&D in Yellow Box - what became of that?
- Just like Apple invested a lot of R&D in Blue Box - what became of that?
- Just like Apple invested a lot of R&D in Newton - what became of that?
- Just like Apple invested a lot of R&D in Pippin - what became of that?
- Just like Apple invested a lot of R&D in PowerPC - what became of that?
- Just like Apple invested a lot of R&D in OpenCL - now what's becoming of that?
- Just like Apple didn't invest a lot of R&D in OpenGL - now what's becoming of that?
- What about the fling with Objective C - a proprietary programming language for a proprietary OS?
- What about Swift - a proprietary programming language to replace a proprietary programming language for a proprietary OS?
- What about Cocoa and Carbon?
- What about Carbon 64 - an evolution of Carbon that was promised and even beta tested - then dropped even as major partners were in beta?
On the other hand, new colors for Apple watch bands are a hot development area.
The last true innovation from Cupertino happened shortly after Next bought Apple.
[doublepost=1468449905][/doublepost]
Apologies for taking this out of context - but it's precious!
Tiger was a long, long time ago.im just replying because i can, im not to prove anyone here right or wrong but in regards to the list you gave several things did become successful and some are still in use today
"Just like Apple invested a lot of R&D in Rhapsody - what became of that?" Rhapsody was developed into OS X (there was nextstep openstep Rhapsody DR1 DR2 then OS X DP releases DP3 introduced aqua and there was the OS X 1.x server releases)
"Just like Apple invested a lot of R&D in Yellow Box - what became of that?" Yellow box became Cocoa IIRC
"Just like Apple invested a lot of R&D in Blue Box - what became of that?" Blue Box became the classic environment in OS X through to tiger
LOL. Asked and answered.
You've dodged my honest question: can you show it's a success?
This, I respect. Reticuli and I can disagree without mental gymnastics and tiresome semantics.
The best estimates I have seen (based on some anonymous source) put the nMP at less than 1% of mac sales.
http://architosh.com/2016/06/if-jobs-failed-twice-why-would-ives-team-succeed-rip-new-mac-pro/
Does that prove me right? No. Does it prove Linuxcooldude wrong? No. But so far, the only info out there(admittedly questionable and in no way proven reliable) leans toward the nMP being a sales flop.
Apple is very likely selling Mac computers of all kinds to approximately 3/4 of a million architectural users worldwide. But...if....our source is correct, if.....the Mac Pro is less than 1 percent of all Macs sold, than the vast majority of architects worldwide are using iMac desktops and Mac mobile computers and somehow making do.
To conclude, if...... Apple’s Mac Pro sales are so paltry that they yield just 150,000 to 200,000 per year (less than 1%), this is just one quarter of Power Mac sales in 2002. Put another way, if.... Mac Pros today actually account for about 4% of all Mac sales, they approximate 2002 sales for Power Macs.
My two part answer.
1) According to the forum rules a member can ask another member for sources to back up their facts. So even with MacRumors believes the burden of proof is on you.
2) Than we have what is known as the burden of proof fallacy or "Argumentum Ad Ignorantiam" In which some one tries to shift the burden of proof to the other person claiming "If you can't prove me wrong, I must be right"]
presumably readying something new
What about Swift - a proprietary programming language to replace a proprietary programming language for a proprietary OS?
No, I am not wrong on this. Currently you have a choice of form (Mac Mini - i.e. smaller size, consumes less power) and functionality (nMP - i.e. larger size, consumes more power). If form (i.e. size, consumes less power) were really important to you then you would choose the Mini. You do not because you value the added capability the Mac Pro offers over the Mini.
This is no different than those who value the expansion capability and faster speed of the cMP configuration over the nMP configuration. You are arguing the nMP's strengths over the cMP to be smaller size and less energy consumption despite the fact these people tell you they value expansion of the cMP configuration above that. At the same time you're doing the exact same thing when I say you should be using a mini if form factor is at the top of your list...as you have done to the cMP advocates. Then you perform a complete 180 as argue capability is most important to you and then form factor. It's the same arguement.
This is the exact same argument cMP advocates have been making. The nMP is slower and less functional than what it replaced (this argument assumes an updated cMP which would have included the technology used in the nMP).
My feeling is that if Apple do not introduce some sort of pro tower to replace the Tube then they should simply discontinue the Xeon line. If a job is worth doing then it is worth doing well - only a loser goes about things in a half-arsed way.
Not once have I seen such an argument. People complained about the missing internal hard drive slots and PCI-e slots. Nobody said that it's slower than what would have been. How could it? Uses the same components as before.
you could install as much memory as before
Exactly, nMP is not a slow system at all, it may be missing the slots and bays, but in performance is as it should be.
One thing that many forgot is that when it was released it's ssd speed was phenomenal.
Sorry, I am not following the nMP's stuff very closely. The nMP can install 128GB RAM now?
Yes, it can, although when I checked the ram used at this density (32GB per DIMM) was of a lower clock speed than the 16GB DIMMS. This may have changed in the last year or so.
Therein lies the problem with the nMP to people who want the capability of the cMP form factor. For them the nMP does not "do" what the previous cMP did. Are you now seeing why they're objecting to it?I don't know what's so hard about this to understand. I prefer the small form factor of nMP as long as it does what the cMP does, and it does. Apple did not make it slower. It had as many cores as before of the same type of CPU's, you could install as much memory as before, and you could have as many GPU's in full-size buses as before. And they made it smaller while keeping everything intact. My only issue was being forced into buying two GPU's, but I can live with that.
It's slower than what it could have been had Apple retained the same capability of the cMP and upgraded the technology contained within. Yes the nMP has the equivalent number of cores as the older technology offered in the cMP. However had Apple upgraded the technology in the cMP to the nMP equivalent it could have twice the cores. Or the same number of cores at a lower cost (because two 6-core processors cost less than a single 12-core processor not to mention both processors will have a higher clock speed offer more performance than the single core offering). Twice the memory. Twice the PCI lanes.Not once have I seen such an argument. People complained about the missing internal hard drive slots and PCI-e slots. Nobody said that it's slower than what would have been. How could it? Uses the same components as before.
I agree with this. The question is: Why hasn't Apple already done so? The parts are available all Apple needs to do is use them.I agree that a refresh of the current design is the most likely outcome.
I can't say I agree on water cooling through. This couldn't be implemented without significant changes to the shape of the case and its internals. It won't happen, I'd put money on it.
We can debate here, however... DP1.3 and 1.4 is what they might have wanted.I agree with this. The question is: Why hasn't Apple already done so? The parts are available all Apple needs to do is use them.
In the meantime they could have upgraded the processors, memory, and GPUs.We can debate here, however... DP1.3 and 1.4 is what they might have wanted.
DP1.3 makes sense for 5K resolution SST. DP1.4 - 8K at 60Hz...
It doesn't have to be XCode...
Therein lies the problem with the nMP to people who want the capability of the cMP form factor. For them the nMP does not "do" what the previous cMP did. Are you now seeing why they're objecting to it?
It's slower than what it could have been had Apple retained the same capability of the cMP and upgraded the technology contained within.
Yes the nMP has the equivalent number of cores as the older technology offered in the cMP. However had Apple upgraded the technology in the cMP to the nMP equivalent it could have twice the cores.
Or the same number of cores at a lower cost (because two 6-core processors cost less than a single 12-core processor not to mention both processors will have a higher clock speed offer more performance than the single core offering).
More like six times the memory.... Twice the memory. ...
All the apple specific and essential libraries are. Obj-c or swift without those is pretty much crap.Neither Obj-C or Swift is proprietary.
Then we need hear nothing more about how these people should accept the nMP.Yes, and that's not the same as it being "slower". I already said that for some people losing internal HD slots and PCI-e lanes diminished functionality.
Because the CPUs would be available.If they offered 2x12 Core CPU's, yes. Apple probably would have offered 2x6 Cores BTO as before. When they released 2012 MP's, there were 8 Core Xeons available yet Apple did not offer 2x8 BTO's. Same with 2009 MP's. Why do you assume that suddenly in 2013 Apple would have offered the max amount of single cores per CPU?
Poor argument given the nMP lost that very motherboard and the savings were not passed along.Lower cost? So we are only paying attention to the cost of the CPU's and not to the boards that host 2 CPU's instead of one.
I didn't want to go down the theoretical path given Apple would probably only go four DIMMs per CPU.More like six times the memory.
The MP6,1 has 4 DIMM slots. A dual socket E5-26xx v2 can have 24 DIMM slots. (4 channels per socket, 3 DIMMs per channel)
View attachment 640190
I'm not exactly sure of the cloud based development environment your talking about. I know Apple recommends only to use their software downloaded from their servers. Had problems before with downloading it from third party sites that injected malware into apps.