How about when connecting an external monitor? My 2019 Mac Book Pro will get very hot after a few minutes and many people report the same.
Apple Silicon M1: Black Magic Fuckery
801–810 of 1001 posts
Re: Apple Silicon M1: Black Magic Fuckery
#802Earlier quoted context omitted.
It also would have no difference between the outgoing Intel ones and the incoming Apple Silicon ones. Same pointer sizes, same app memory management, etc... Some fairly minor differences in overall binary sizes, so no "wins" there or anything either.
All Swift/ObjC software has been doing ARC for ten (?) years. Virtual memory usage will be the same under M1. It will just pay off in being faster to refcount (ie as fast as it already is on an iPhone), and therefore the same software runs faster. Probably won't work under Rosetta 2 with the per-thread Total Store Ordering switch. And it's probably not specific to NSObject, any thread safe reference counter will bene…
You might try reading the article. One example was a large software build taking ~25% less time on a 13" MBP than on a 12-core Mac Pro.
I'm curious about FP/vector performance, but I'm pretty sure it's fine. I'm definitely eyeing a MBP myself! 20 hours of video playback? Crazy...
Re: Apple Silicon M1: Black Magic Fuckery
#803Earlier quoted context omitted.
What Apple could have done is to continue supplying something like the G4 towers. Those where stunningly beautiful machines and practical.
What if they simply decided that they didn't care for that part of the market? At some point we should just accept that.
Sure, but there's a legit gap in the datacenter— not having a sanely, legally rackable OS X machine is a pretty big problem for a lot of organizations. Not everyone wants to do their Jenkins builds or generate homebrew bottles on a Mac Mini under someone's desk.
Re: Apple Silicon M1: Black Magic Fuckery
#804For those of us who are picking up M1 MacBooks as first time Mac users, is there some kind of Mac crash course for devs? What apps are useful, what familiar tools from Linux can we use, etc? I'm aware of Dash, which makes me suspect there are a bunch of other Mac-exclusive tools which will be useful.
Better Touch Tool [1] is a must have for customizing the touchpad and keyboard. I like Karabiner to convert the Caps Lock into a new meta key [2].
[2] https://www.howtogeek.com/409904/how-to-turn-your-mac’s-caps...
Re: Apple Silicon M1: Black Magic Fuckery
#805Not to speak for anyone else, but one thing I gently disagree with: > Given that Hackintoshers are a particular bunch who don’t take kindly to the Apple-tax[...] I have zero issues with an Apple premium or paying a lot for hardware. I think a major generator of interest in hackintoshes has been that there are significant segments of computing that Apple has simply completely (or nearly completely) given up on, includ…
Apple does not want to offer to the hackintosh/enthusiast market because they are the most price conscious segment. Targeting that segment means putting out extremely performant, low-margin commodity machines. Doing so then cannibalizes the market for their ultra-high-end stuff. Not only that, though. Enthusiasts are also extremely fickle and quick to jump ship to a cheaper hardware offering. If you look at all of Ap…
Considering how much the gaming side of the PC market will drop on just a single card I am more of the opinion that Apple chose to avoid this market because it did not want the association with gaming as if that were beneath their machines.
At times there seemed to be a real disdain for the people who loved upgrading their machines as well as those who gamed on them. Apple's products were not meant to be improved by anyone other than Apple and you don't sully them with games. The Mac Pro seems to be the ultimate expression of "You are not worthy" from the base system which was priced beyond reason to the monitor and stand. It was the declaration of, "fine, if you want to play then it will cost you" because they didn't really care about the enthusiast of the wrong use - games and such.
Re: Apple Silicon M1: Black Magic Fuckery
#806Not to speak for anyone else, but one thing I gently disagree with: > Given that Hackintoshers are a particular bunch who don’t take kindly to the Apple-tax[...] I have zero issues with an Apple premium or paying a lot for hardware. I think a major generator of interest in hackintoshes has been that there are significant segments of computing that Apple has simply completely (or nearly completely) given up on, includ…
If you don't have issues with paying a lot for hardware, why don't you buy Mac Pro?
Because even a $3K non-Apple Machine outperforms the $5K base model Mac Pro by a large margin, and if I spent $5K outside Apple it would be even more ridiculous, double RTX 3090 + 24 core Threadripper ridiculous.
Re: Apple Silicon M1: Black Magic Fuckery
#807Earlier quoted context omitted.
Regrets rarely appear 1 week after buying a product :-)
I thought they often happen instantly? Or in the 5 hours after you received the product? I don't ever recall regretting something I've purchased, say, more than 1 month ago. The act of purchase is foregone past by that point.
You've never had something fail 1 month or 6 months after purchase?
Re: Apple Silicon M1: Black Magic Fuckery
#808Earlier quoted context omitted.
I think it's more a design pattern you see more with GC collected languages where people instantiate objects with pretty much every action and then let the the GC handle the mess afterward. Every function call involves first creating a parameters object, populating it, then forgetting about it immediately afterward. I've seen this with java where the memory usage graph looks like a sawtooth, with 100s of MB being all…
Isn't it the case with Java that it will do this because you do have the memory to spend on it? Generally this "handling the mess afterward" involves some kind of nursery or early generation these days, but their size may be use-case-dependent. If tuned for a 8/16 GB environment, presumably the "sawtooth" wouldn't need to be as tall.
Yes, but the reason it does it is to make it fast. The shorter your sawtooth spokes, the slower your app.
Re: Apple Silicon M1: Black Magic Fuckery
#809Earlier quoted context omitted.
Agree completely. I don’t know that the “Apple tax” moniker is really fair anymore, either. The machines have always commanded a premium for things that enthusiasts don’t see value in (I.e. anything beyond numeric spec sheet values), so most critics completely miss the point of them. There’s a valid argument to be made that they’re also marked up to higher margins than rivals even beyond the above, but I’m not sure i…
> The machines have always commanded a premium for things that enthusiasts don’t see value in (I.e. anything beyond numeric spec sheet values), so most critics completely miss the point of them. It's not just intangibles. I really like using Macs, but my latest computer is a Dell XPS 17. This is not a cheap computer if you get the 4k screen, 64GB of RAM and the good graphics card. At those prices, you should consider…
Yes and no. To be honest I did the same back-of-the-napkin math that you did prior to buying my MBP - the thing is the TCO is even worse if you customise the machine.
Example - a Mac is a Mac for resale purposes - if I attempt to later sell an XPS that I've opened up and put an SSD in and a couple of SODIMMS - I now need to recoup my cost on all of those things. The problem is that if someone is looking at a used XPS with upgraded SSD and upgraded RAM they're statistically unlikely to fully investigate and value the (probably really good) parts that you upgraded it with - they're just going to see X,Y,Z numbers and price accordingly.
Generally though, a 5 year old Windows laptop with 16GB RAM still commands the value of a 5 year old Windows laptop as best I could tell looking at resale values.
Re: Apple Silicon M1: Black Magic Fuckery
#810Earlier quoted context omitted.
From the original article: Third, Marcel Weiher explains Apple’s obsession about keeping memory consumption under control from his time at Apple as well as the benefits of reference counting: >where Apple might have been “focused” on performance for the last 15 years or so, they have been completely anal about memory consumption. When I was there, we were fixing 32 byte memory leaks. Leaks that happened once. So not…
But again that didn't change with M1 . We're talking MacOS vs. MacOS here. Your quote is fully irrelevant to what's being discussed which is the outgoing 32gb macbook vs the new 16gb-max ones. They are running the same software. Using the same ObjC & Swift reference counting systems.
We've run full circle there
ARC is not specific to M1, BUT have been widely used in ObjC & Swift for years AND is thus heavily optimized on M1 that perform "retain and release" way faster (even when emulating x86)
Perfect illustration of Apple software+hardware long term strategy.