Comment Re:What's the equivalent? (Score 3, Informative) 128
To replace your 5D, check out the conveniently named Canon R5.
To replace your 5D, check out the conveniently named Canon R5.
That's demonstrably false. The Mac OS had TCP/IP in 1988 via a commercial product; by 1994 it was a standard part of the operating system. And AppleTalk became TCP/IP compatible (i.e., the protocol could run over IP instead of its proprietary packet scheme) in the late 90s, years before OS X was released.
Man, you've got a lot of unsupported assertions going on.
"Notebooks" vs "laptops" is semantics, not specifications or benchmarks. There is no implied performance differential between them.
"They only run MacOS software" - as the other poster noted, almost any open source UNIX-based software can be successfully compiled and run on MacOS.
"No Windows via emulation" - false, you can totally run ARM Windows via emulation. The licensing of this is another question.
"Not a lot of MacOS software out there" - I don't even know what this means. There is plenty of software that runs natively on MacOS.
"You must use their native language to access their native UI controls" - false, there are several languages that outright support native Mac UI elements and at least a dozen cross-platform frameworks that work in C-like languages.
Have you done any long-term management of Macs? I've seen even the non-upgradable 2012 Retina MacBook Pros still ticking along 7-8 years later. Apple hardware is generally very long-lived, provided it isn't physically abused, and the initial investment in extra RAM/storage will pay off in a machine you don't have to replace for a long, long time.
Granted, we haven't had the ARM machine around long enough to know their eventual useful lifespan, but I have no particular reason to imagine that it will be much different. Apple typically uses high quality components in their manufacturing - after having learned some tough lessons in the 90's.
Third-party mice do this quite handily on Mac OS.
Their new approach does mean that there is only one version of any library in memory - the one with ARM executable code. The original poster was asserting that both Intel and ARM versions of libraries were being loaded and overextending RAM into swap, which isn't the case.
As for the Apple-provided code in the OS and applications, my guess would be that they are virtually all compiled for ARM. Apple has done CPU transitions before and back in the halcyon days of PowerPC 2001-2005, they were secretly maintaining a version of OS X that was compiled for Intel "just in case". Ever since then, they've been hammering it into developers that code should make very, very few assumptions about the underlying architecture. If you follow their guidelines, Xcode makes it as easy as a checkbox to recompile your code for new architectures.
There are possibly-apocryphal reports from inside Apple during this time that OS engineers who weren't privy to the Intel build would get these strange tickets requesting that they change endian-dependent code to be independent of that CPU attribute – despite the fact that there was no apparent reason for this to be an issue on CPU-uniform platform like OS X. Later, this was important corroborating evidence to piece together the story that Apple was preparing to make the transition to Intel.
It is very different this time, actually. Intel binaries are translated to the ARM instruction set once, the first time they are launched (or loaded, if we're talking a library) and the results cached to disk. No Intel code is ever loaded into RAM for the purposes of execution.
The Late 2008-Early 2009 MacBook Pros have an honest-to-bog tool-free replaceable battery, with a latch and panel that pops off the bottom of the laptop. I believe this was the last model to feature this capability.
What... what did I just read?
I wonder if this was a botpost or a human typing.
These are great, and I use them on all my gear. The kit includes a variety of sizes and shapes. The adhesive is very strong and will stick to virtually any surface, and the label is protected by a transparent plastic coating that makes it very resistant to scratches. The printing is rated for fade resistance after several years in the outdoors, and the price is just right.
http://www.mavericklabel.com/p...
Disclaimer: I used to work at this company. They're good people.
Last time I checked, iMacs didn't come with an expiration date stamped on the back, nor do they burst into flames when some imaginary expiration date is met. Apple hardware lasts a *long* time. If you CHOOSE to upgrade, that is your choice, not Apple's.
nebulo
Get a USB extension cable, duh.
nebulo
What doubts would those be? They're displays. You plug them in and they work. If you don't like Thunderbolt displays, feel free to use a DisplayPort monitor. Unless, of course, you have doubts about *them*, in which case I suggest you get a DisplayPort->VGA converter for your 1992 amber-on-black monochrome display.
Troll.
nebulo
A 62-year old friend of mine took an iOS certification course at the University of Washington (Seattle) and promptly found a full-time position at one of the Big Four professional services firms, developing mobile applications for their clients. Prior to this job, he was a self-employed specialty developer, until his wife fell ill and he needed to procure full-time employment.
So hope springs eternal - it's at least possible to get a job after being Of A Certain Age, if you have the right skills for the right field.
nebulo
The article makes a huge logical leap: that US laws governing items on federal lands somehow apply to items that are not on federal lands (for example, the asteroid belt). This is akin to saying that US antiquity laws would prevent a US citizen from prospecting for fossils in, say, Canada. What a load of baloney. The author is trying to conflate and confuse two issues (mining in space and prospecting on US federal lands) which are utterly unrelated.
Nebulo
Function reject.