Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Are Applications/Software going to Improve or Disimprove with new ARM Architecture?
- Thread starter trevpimp
- Start date
- Sort by reaction score
You don't know the history of operating systems very well.
Bloat usually refers to additional applications and extensions that load with an OS that aren't necessary.The base memory requirements of macOS (and even Windows) haven't changed in a decade and benchmarks show how new hardware and new APIs continue to making computing much faster every few years.
Another big factor is Swift. It's pretty much the only mainstream programming language today that focuses on cooperative resource usage rather than absolute single-application performance. Also, the new concurrency API they launched this year avoids thread explosion, instead trying to match what the system can do efficiently. These are all big things that aim to counteract the inefficient hardware resource of modern applications.
Bloat refers to what it is applied to. macOS now sells on machines that have 8GB minimum. Mavericks was the last OS version which could work on a hard disk. SSDs simply allowed larger and more complex crap which requires faster Macs to stand still. MacOS is trash nowadays.
There is nothing wrong with optimizing the software with modern hardware in mind. Yes, modern Macs don’t work well on HDDs since APFS is designed specifically for SSDs. I fail to see a problem here. HDDs are an obsolete technology for personal computing.
You are confusing the cause and the consequence. MacOS doesn’t run bad on HDDs because it’s “bloated”. It runs bad on HDDs because Apple gave up on the HDD as a storage for the system partition.
Nice troll! what don't you like the new Mac OS because Apple is almost ready to release a new Operating system in coming months!
Forum Rules
Jump to: Instantly Bannable Offenses | Advertising/Self-promotion | Things Not to Do | Minor Problems The following rules govern use of the forums. You are also responsible for observing the Regist...
Minor Problems > section 8
If everyone knows what they're talking about, theres no need to be "that guy" to point out their very minor mistake. It's completely pointless
Mojave was the last build that could run 32-bit apps before Apple ARM-twisted us into submission in subsequent releases. SL was the only version of MacOS to be more efficient on the same HW that its predecessor. It's clear why MacOS has gone downhill since Scott Forstall was run out of Cupertino.
OK you fooled me with this joking around about hard drives and 32 bit apps. Well played.
But if you're serious you can go and demand Scott to come back and make Monterey support 32 bit x86 apps and internal hard drives again. Because reasons.
When Scott Forstall left, there weren't a lot of tears in Cupertino. The only reason he was able to stick around was because Steve liked him. Why stop at 32-bit apps? Why not have MS bring back 16-bit app support? Apple has now managed a major OS transition, across three platform transitions. MS can barely get support for Windows on ARM.
At some point the cost of maintaining backward compatibility becomes too much work for too little benefit. Apple is usually pretty good about giving fair warning, and providing the tools necessary to make the transitions when they happen.
At some point the cost of maintaining backward compatibility becomes too much work for too little benefit. Apple is usually pretty good about giving fair warning, and providing the tools necessary to make the transitions when they happen.
I haven't really taken a hard look at Swift's async/await implementation yet but at least from a syntax point of view it doesn't seem particularly different than other language implementations. Is there something specific that makes it better?
It’s not the API itself (although I think that the Swift team did a tremendous job here - of course, they had years of experience pioneered by other languages to learn from), but the executor. If I understood their presentations correctly, the executor aims to minimize context switches and reduces the amount of spawned threads.
Nah, very different languages. Swift class types are partially compatible with Objective-C objects, and there are overlaps in the runtime, but the basic language design abs philosophy couldn’t be different.
Not at all. Swift is substantially different as a strongly typed language and a lot of static analysis for optimization. Until recently it was difficult to do dynamic programming because Swift is statically typed.
I thought it is just wrapping grand central dispatch. GCD is very good at managing available resources.
I think they were rather clear that it’s a new continuation-aware executor, not GDC. They explicitly mentioned some issues with GDC (like thread explosion) that the new framework solves. They also mentioned things like hopping continuations between threads to improve utilization of multiple CPU cores. The system sounds very sophisticated actually.
yeah keep thinking that. macOS Monterey beta is much better than the macOS Big Sur beta ever was.
I expect when Monterey releases to the public in the Fall it would be WAY better than Big Sur when it was released last year.
Monterey has more useful features than Big Sur like Low Power Mode, Universal Control and native Airplay to mac and more.
Also Apple can easily focus on macOS stability and performance after it finishes its 2 year ARM transition like it for iOS 12.
“
- Corrections. There is no need to point out another poster's spelling or grammatical errors unless you think it is causing confusion. Remember that not all members are native English speakers. Communication, not correctness, is our goal. Examples: Don't correct members who spell Mac in all caps or who call the iPod touch an iTouch. When other people (especially new members) fail to search and start new threads on old topics, don't scold them or make them feel unwelcome. The best way to be helpful is by posting a link to a relevant thread or specific instructions for problem solving. Set a good example yourself by searching first before starting a thread if you have a question that may already have been answered in the forums or you want to discuss a topic that may already have been discussed. The exception is articles appearing on our Front Page, Mac Blog, and iOS Blog. These entries are created by our professional staff. If you notice a spelling or grammar error in these articles, please send an e-mail to tips@macrumors.com.
I now code mostly in swift, but it certainly makes my eyes bleed much more than Objective C. Lots of hard-to-remember syntax that is even harder to read.