Earlier quoted context omitted.
> it's actually way more important this time. How so? All the old legacy apps that nobody wants to (or can) recompile were just jettisoned in the 64 bit transition, as TFA duly noted. "In retrospect, the move to 64-bit software may have been made not just for its own sake, but in contemplation of the ARM transition."
32 bit is going back a lot longer, although my machine which I haven't upgraded to Catalina still has a few 32bit applications kicking around on it including one that I was using in my professional work only 6 months ago. Plenty of 64 bit software exists that isn't being updated often or at all anymore.
Osborning the Mac, or not
121–130 of 253 posts
Re: Osborning the Mac, or not
#1221. Apple designed chips are already faster per-core than a top-end MacBook Pro. 2. There's no reason dedicated ASIC modules for specialized tasks (like video rendering) can't be connected by Thunderbolt 3 just as external video/compute modules are now. 3. There's no reason a dedicated x86-64 dongle can't be sold for ARM-powered Macs that need to run software that hasn't been ported yet. It would be a spectacular coup…
I think the last thing the MacBooks need are more dongles.
Re: Osborning the Mac, or not
#123I’m just real glad that my personal upgrade cycle is at the point where I won’t be looking for a new computer until at least the second year of ARM Macs, when most show-stopping bugs should be ironed out of the OS and the Adobe tools I spend most of my work time in. I was an early adopter of PPC and OSX, I’m not gonna sit there trying to get work done via the old-cpu emulation again.
Also: On a desktop machine, there’s no benefit in lower power dissipation and slimmer bodies If you’re in a hot climate then every little bit helps. Lower your power bill due both to lower consumption on the part of your computer and due to the AC coming on that much less. Run the computers fan less. Maybe even have a Mini that does a surprising amount of what you’d buy a Pro for. Make the iMac that much more of a fl…
Intel desktop CPUs are where they have problems and you would assume that this is where Apple has the most frustration with Intel. That's where I'd start.
Also, by keeping ARM and Intel around simultaneously for a few years (both as first-class citizens) forces developers to maintain portable code. If you are using Swift in the manner that they want you to use it, this is already the case. If you're using some other language/approach then you have to either think about adopting Swift or putting in more work.
Re: Osborning the Mac, or not
#1241. Apple designed chips are already faster per-core than a top-end MacBook Pro. 2. There's no reason dedicated ASIC modules for specialized tasks (like video rendering) can't be connected by Thunderbolt 3 just as external video/compute modules are now. 3. There's no reason a dedicated x86-64 dongle can't be sold for ARM-powered Macs that need to run software that hasn't been ported yet. It would be a spectacular coup…
When it's a laptop, I'm quite the fan of having as much as possible built into the machine as a single unit. That's the point of the form factor, after all. I think the last thing the MacBooks need are more dongles.
Dongles for legacy functions in the process of deprecation that some users may not want/need seems sensible.
Re: Osborning the Mac, or not
#125Earlier quoted context omitted.
Even back in 2006, there were at least 7-8 different ways to define a string on Windows depending on which API you were using.
You may have missed GP's point. Microsoft is casts a very wide net, running on a huge array of hardware and trying to do everything from mobile to console gaming to datacenter servers. The dev experience is equally diverse: you don't even need a Windows box to develop for Windows. Apple jettisoned all of that diversity to refine a few precious use cases to earn that "quality" aura. I think this move to ARM is signali…
- Microsoft is a non starter in mobile
- trying to run Windows on low end Surfaces is painful
- Windows is horrible as a touch first interface.
- even with Azure there are more Linux VMs than Windows.
-it takes literally years and multiple failures every time that MS tries to release a new version of Windows.
- They finally through in the towel when it came to IE and was forced to use a competitors engine.
MS is not exactly the shining example of how to successfully pivot as technology changes.
Re: Osborning the Mac, or not
#126Earlier quoted context omitted.
I envy your enthusiasm. Apple has not been quite as attentive regarding the Mac as it used to when those transitions happenned. I do believe ARM Macs will do fine, eventually.
Even for the Mac Pro workstations? I bet Apple Audio and VFX shops will not be happy
Re: Osborning the Mac, or not
#127Earlier quoted context omitted.
Also: On a desktop machine, there’s no benefit in lower power dissipation and slimmer bodies If you’re in a hot climate then every little bit helps. Lower your power bill due both to lower consumption on the part of your computer and due to the AC coming on that much less. Run the computers fan less. Maybe even have a Mini that does a surprising amount of what you’d buy a Pro for. Make the iMac that much more of a fl…
I read that paragraph and had a completely orthogonal thought. Intel mobile CPUs compare favorably to all established competition (AMD) and the iPad with Magic Keyboard is almost a laptop anyway. Why start with a mobile device? Intel desktop CPUs are where they have problems and you would assume that this is where Apple has the most frustration with Intel. That's where I'd start. Also, by keeping ARM and Intel around…
Re: Osborning the Mac, or not
#128Earlier quoted context omitted.
Have you read Raymond Chen's MS blog about all of the hacks that are in Windows just to keep backwards compatibility with one bad app? Maintaining backwards compatibility forever increases the security vulnerability to footprint, the testing surface for regressions, code size etc. Have you seen how badly Windows runs in low resource environments like the low end Surface line? IE and the collapse of MS's browser marke…
You’re sort of picking the worst example, the alternate is the fact that Windows has maintained a gargantuan desktop OS market share for decades in large part because of their dedication to application compatibility.
No one cares about PCs as a business anymore.
Re: Osborning the Mac, or not
#129Earlier quoted context omitted.
I read that paragraph and had a completely orthogonal thought. Intel mobile CPUs compare favorably to all established competition (AMD) and the iPad with Magic Keyboard is almost a laptop anyway. Why start with a mobile device? Intel desktop CPUs are where they have problems and you would assume that this is where Apple has the most frustration with Intel. That's where I'd start. Also, by keeping ARM and Intel around…
The thing is, the majority of Macs sold are laptops. It doesn’t make sense for them as a business to build a strategy around what’s best for desktop machines.
Re: Osborning the Mac, or not
#130Earlier quoted context omitted.
Have you read Raymond Chen's MS blog about all of the hacks that are in Windows just to keep backwards compatibility with one bad app? Maintaining backwards compatibility forever increases the security vulnerability to footprint, the testing surface for regressions, code size etc. Have you seen how badly Windows runs in low resource environments like the low end Surface line? IE and the collapse of MS's browser marke…
I didn't say there were not any tradeoffs made to support those users with legacy systems. What do you define as a low end Surface line on x86? I have a Surface Pro 1 that I still use to this day. I also have a GPD Win handheld that's running an Atom processor that is surprisingly good for what it is. I also have some older Atom based stick PCs that are pretty bad (only 2GB RAM), but those are designed for signage an…
The iPads can actually run well with 2GB of RAM. Microsoft Office is a much better experience on an iPad without a keyboard than any hardware that Apple sells.