Technology

59374 readers

3794 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

741

Even Apple finally admits that 8GB RAM isn't enough (www.xda-developers.com)

submitted 4 months ago by [email protected] to c/[email protected]

285 comments fedilink hide all child comments

There were a number of exciting announcements from Apple at WWDC 2024, from macOS Sequoia to Apple Intelligence. However, a subtle addition to Xcode 16 — the development environment for Apple platforms, like iOS and macOS — is a feature called Predictive Code Completion. Unfortunately, if you bought into Apple's claim that 8GB of unified memory was enough for base-model Apple silicon Macs, you won't be able to use it. There's a memory requirement for Predictive Code Completion in Xcode 16, and it's the closest thing we'll get from Apple to an admission that 8GB of memory isn't really enough for a new Mac in 2024.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 4 months ago (3 children)

I'd love to have 8GB of RAM. The SOC I'm working with has only 2K ;-)

[–] [email protected] 7 points 4 months ago (1 children)

Bet your compiler isnt running on that hardware either ;-)

[–] [email protected] 2 points 4 months ago

Luckily, no ;-)

[–] [email protected] 2 points 4 months ago (1 children)

2 kilobytes?

[–] [email protected] 7 points 4 months ago (2 children)

Yes. 2 kilobytes. Coincidentally, this is as big as the displays internal buffer, so I cannot even keep a shadow copy of it in my RAM for the GUI.

[–] [email protected] 2 points 4 months ago

Thanks for clarification.

[–] [email protected] 1 points 4 months ago (1 children)

I've never seen backbuffer called shadow copy.

[–] [email protected] 3 points 4 months ago (1 children)

And I have never heard it called "backbuffer", so we are even.

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 children)

I guess so.

Example: https://www.khronos.org/opengl/wiki/Default_Framebuffer#Double_buffering

EDIT: Wait. Do you have framebuffer at all? Because from sounds of it, you might not even have it at all. If you don't store entire frame in RAM, then you don't have framebuffer, not just backbuffer.

[–] [email protected] 2 points 4 months ago (1 children)

I never said anything about framebuffers. The 256x64 pixel display in 16 brightness levels probably has something comparable inside. I just tell it that i want to update a rectangle, and send it some data for that.

[–] [email protected] 1 points 4 months ago

It should have.

Then, if you don't store contents of entire screen in memory, which simple math says you can't, I was partially wrong(depending on if you don't count buffer in display as framebuffer) when interpreted "shadow copy" as backbuffer.

[–] [email protected] 1 points 4 months ago (2 children)

Come on, man, AVR chips aren't SoCs except in the technical sense.

[–] [email protected] 2 points 4 months ago (1 children)

No AVR, it's a small LPC from NXP. Chosen for the price, of course, but I have to somehow squeeze the software in it. At this point, even 8k would make me happy...

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago)

NXP, fancy. I expected ST, AVR, nRF, WCH or some chinese cheaptroller.

Why them? Something to do with NFC?

[–] [email protected] 1 points 4 months ago

Man, microcontrollers are namegivers of SoC.