Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple Silicon M1: Black Magic Fuckery

singhkays.com

Post reply on HN
Print view View original

911–920 of 1001 posts

Re: Apple Silicon M1: Black Magic Fuckery

#911

Post by vetinari »

dschuler wrote: post #601
PopeDotNinja wrote: post #535

Earlier quoted context omitted.

I don't mind paying for a new Apple, but I do mind paying for repairs on a system that fails just after the warranty runs out. Paying $1500 for a new computer every 5 years or so is good. Paying $1500 for a computer every 16 months, not so much. The monitor on my MacBook Pro just died, and I bought it July of last year. The repair was about $850 USD. Luckily my credit card covered the hardware warranty, but I'm kind…

AppleCare for the Macs is definitely worth it. They even replaced the display on my MBP after 5 years when I called (that seems to be the key is to call someone at Apple directly). This was a part they should've recalled, but anyway I wouldn't have gotten a new display without AppleCare.

There was a display replacement program for 2012-2015 MBP13s, due to the staingate. Though I recall that it was for 4 years since date of purchase, or so.

Re: Apple Silicon M1: Black Magic Fuckery

#912

Post by llampx »

Shivetya wrote: post #805
chongli wrote: post #408

Earlier quoted context omitted.

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…

Why do they highlight games at every WWDC and product announcement?

Re: Apple Silicon M1: Black Magic Fuckery

#913

Post by [deleted] »

thinbeige wrote: post #623
cjgk wrote: post #608

Earlier quoted context omitted.

> If I wasn't freelance, I could probably get away with some cloud instance to run all my docker stuff, but I'm dealing with too many different environments, for clients with various different legal requirements making this simply 'not an option'. While not the exact same reasons as GP, I also need to be able to do this locally.

Even with legal restrictions: just put an Ubuntu server at home and ssh to it. Then you wouldn't have the GBit connection but still better than using Docker on a non-production OS.

[deleted]

Re: Apple Silicon M1: Black Magic Fuckery

#914

Post by NateEag »

ogre_codes wrote: post #863
NateEag wrote: post #753

Earlier quoted context omitted.

I just got a new MBP this summer from my workplace, running Catalina. Getting it to run software not approved by Apple is a pain. They may always leave a door open somewhere, but I wouldn't want to count on that.

What software are you having trouble getting installed? I've never had issues with getting things from inside or outside the App Store working. Usually it's just dragging the App into the Applications folder and answering a prompt. Sometimes there is an installer. (or I use Home-brew) Maybe you are trying to install something from a developer who doesn't sign their code or doesn't have an Apple Developer ID? I'm curi…

Yes, it's unsigned software.

Several of my virtualenvs are broken on Catalina - apparently the binaries installed by my requirements.txt are not signed for use in Catalina. I had to accept an amount number of dialog boxes by hand to make that work.

There have been others, too, beyond the virtualenvs, which I do not remember offhand.

Re: Apple Silicon M1: Black Magic Fuckery

#915

Post by pertymcpert »

ed25519FUUU wrote: post #401
zamadatix wrote: post #360

Earlier quoted context omitted.

It'll be interesting what happens in a couple of years if server side gets more mixed with ARM as well.

Unless AWS starts selling their graviton CPU, whose going to create chips for the arm server market? The volumes are huge and the margins are tiny, which is not something Apple was ever interested in.

Uhhhh...quite a few companies?

Re: Apple Silicon M1: Black Magic Fuckery

#916

Post by pertymcpert »

oblio wrote: post #807
Aperocky wrote: post #788

Earlier quoted context omitted.

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?

No.

Re: Apple Silicon M1: Black Magic Fuckery

#917

Post by acdha »

nbzso wrote: post #685
sneak wrote: post #406

Earlier quoted context omitted.

If you have an intel mac, you can still install LS 4.x (once you have booted into recovery to permit the kext) on Big Sur. HN user miles pointed this out recently, and it is awesome. https://www.obdev.at/support/littlesnitch/245913651253917 It's 5.x that uses the new restricted APIs. I'm going to contact the developers and ask for an ARM build of 4.x so the same trick will work on M1, at least until Apple forbids all…

This is deal breaker for me and lots of security conscious professionals. I have foreseen this "Apple goal" in the past and the only thing thats keeping me to use MacOS is Little Snitch and Mullvad VPN combination. Sadly in Linux world there is no commercially viable option for access rules per app basis and I don't understand why. I don't have answer for another question: As a business I learned from Apple that keep…

It's because it's very time-consuming but ultimately it's more security theater than any meaningful benefit. An attacker has many ways to easily bypass tools like Little Snitch and they only have to succeed at one of them, whereas you have to hope that you take time away from your job to successfully block all of them.

If you're trying to prevent data exfiltration, you don't trust the client at all — confine it to a dedicated locked-down system on a restricted network which only allows egress to the minimal subset of trusted services. That's a much more winnable battle than trying to prevent every possibility on a general purpose computer running tons of things which are allowed to connect to the internet and legitimately uses lots of outside services.

Similarly, a lot of the data breaches you hear about are caused by people with legitimate access saving the data somewhere insecurely. Spending time on that is a lot more beneficial to most organizations than tracking every TCP socket.

Re: Apple Silicon M1: Black Magic Fuckery

#919

Post by nickjj »

headmelted wrote: post #819
nickjj wrote: post #745

Earlier quoted context omitted.

> Are you sure about that 250$ number? Because I don't think that's a very realistic number. I'm not a student but it's pretty close I think. I invested $350 into a Chromebook that runs native Linux[0] about 4 years ago and it's still going strong as a secondary machine I use when I'm away from my main workstation. It has a 13" 1080p IPS display, 4gb of memory, an SSD, a good keyboard and weighs 2.9 pounds. It's noth…

Right, except that when you stop using the Chromebook every day or move on to something better, will it have residual value or just go to landfill? I love Chromebooks, don't get me wrong, but the problem I've come to realise over time is that many are specced and priced just about at a point where they'll quickly move into obsolescence not long after purchase - at which point the only thing keeping them out of the gr…

To answer your question accurately will depend on how long it ends up lasting for.

For example if it works well enough for another 4 years, now we need to ask the question on whether or not you could get reasonable value out of an 8+ year old Mac. I never sold one so I'm not sure. My gut tells me it's going to be worth way less than what you bought it for even if it's in good condition.

But more generally, yeah I have no intentions on re-selling this thing if I decide I'm done with it before it physically breaks. I'd probably donate it or give it away for free (if someone wanted it).

I don't see that as too bad tho. If I can get 7-8 years out of $350 device I'm pretty happy, especially if the next one costs about the same.

It's a tough comparison tho because a decently decked out MBP is going to be like 8x as expensive but also have way better specs.

Re: Apple Silicon M1: Black Magic Fuckery

#920

Post by Decade »

valuearb wrote: post #835
darren_ wrote: post #87

Earlier quoted context omitted.

This quote doesn’t really cover why M1 macs are more efficient with less ram than intel macs? You’ve got a memory budget, it’s likely broadly the same on both platforms, the speed at which your retains/releases happen isn’t going to be the issue. it’s not like intel macs use GC where m1 uses RC. (It explains why iOS does better with less ram than android, but the quote is specifically claiming this as a reason for 8G…

Yea, this is a BS theory. I have a 16Gb M1 MacBook Air and the real answer is that it has super fast SSD access, so you don’t notice the first few gigabytes of swap. But when swap hits 8-9 Gb, it’s effects start to get very noticeable.

This seems correct. RC vs GC might explain how a Mac full of NSObjects needs less memory than a Windows full of .NET runtimes, but it doesn’t explain how M1 Mac with 16GB of RAM is faster than x86 Mac with 16GB or more of RAM.

Besides, a lot of memory usage is in web browsers, which must use garbage collection.

Looking at the reviews of M1 Macs, those systems are still responsive and making forward progress at a “memory pressure” that would make my x86 Mac struggle in a swap storm. It seems to come down to very fast access to RAM and storage, large on-die caches, and perhaps faster memory compression.

Post reply on HN