# macbook air Published articles for macbook air. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## M6 MacBook Pro vs M5 MacBook Air: What Does the Extra $900 Buy? DevFeed: [M6 MacBook Pro vs M5 MacBook Air: What Does the Extra $900 Buy?]() Original publisher: [Read original article]() Author: TechRepublic Staff Published: 2026-10-30T09:26:51Z Content type: comparison Language: en Sources: [TechRepublic]() Topics: [upgrade](), [On-device AI](), [screen brightness](), [color]() Tags: [ai](), [air](), [apple](), [apple-m5](), [apple-m6](), [apple-silicon](), [applications](), [business](), [business-laptops](), [buyers-guides](), [camera](), [color](), [compare](), [comparisons](), [compatibility](), [configuration](), [connectivity](), [costs](), [display](), [hardware](), [laptop-comparison](), [m6](), [macbook](), [macbook-air](), [macbook-pro](), [news](), [pcs-and-peripherals](), [performance](), [storage]() ### AI overview The 14-inch M6 MacBook Pro starts at $1,999, $900 above the 13-inch M5 MacBook Air. The premium buys a 12-core CPU and GPU versus the Air's 10-core CPU and 8-core base GPU, twice the starting storage, a brighter 1,600-nit peak HDR display with a higher refresh rate, and HDMI, SDXC, and a third Thunderbolt 4 port. Those features may suit HDR editors, camera-file workflows, and some demanding development or local AI tasks; the lighter, fanless Air is presented as sufficient for documents, web apps, and video calls. Both start with 16GB memory, upgrade to 32GB, support Wi-Fi 7, Bluetooth 6, and up to two external displays. Apple's stated M6 speed gains compare it with the previous base M5 Pro, not the M5 Air, so they do not establish the Pro's performance advantage over the Air. The article recommends configuration-matched testing for sustained workloads. ### Source excerpt The M6 MacBook Pro costs $900 more than the M5 MacBook Air. Compare the display, ports, storage, and performance claims before choosing. The post M6 MacBook Pro vs M5 MacBook Air: What Does the Extra $900 Buy? appeared first on TechRepublic. ## Modern MacBook benchmarks for Android development DevFeed: [Modern MacBook benchmarks for Android development]() Original publisher: [Read original article]() Author: Kirill Rozov Published: 2022-01-29T15:56:46Z Content type: comparison Language: en Sources: [Kirill Rozov]() Topics: [Benchmark](), [software-development](), [Android](), [Gradle](), [Intel Core]() Tags: [android](), [android-app-development](), [android-development](), [android-studio](), [androiddev](), [apple](), [apple-m1](), [apple-silicon](), [arm](), [benchmark](), [benchmarks](), [build](), [cpu](), [gradle](), [imac](), [intel](), [intel-core](), [jdk](), [mac](), [macbook](), [macbook-air](), [macbook-pro](), [performance]() ### AI overview Across six Android projects, Apple Silicon generally built faster than the tested 2019 Intel MacBook Pros. In ExoPlayer, the M1 scored 39.4 seconds, the 10-core M1 Pro/Max 28 seconds, and the best Intel result 43.9 seconds; in Telegram, which relies heavily on native C/C++ tooling, Intel i7 and i9 beat the MacBook Air M1 because its native compilation ran through Rosetta 2 while Android NDK support was incomplete. Results are averages of ten Gradle Profiler runs after two warm-ups, using Gradle 7.3.3 and JDK 11 (Zulu ARM on Apple Silicon). The author recommends an M1 Air with 16 GB RAM for most mobile developers, and a 10-core M1 Pro for larger projects or more memory; M1 Max showed no meaningful development benchmark advantage over M1 Pro. The comparison reflects the tested projects and software available at the time, heading into 2022. ### Source excerpt Photo by Danial Igdery https://unsplash.com/photos/FCHlYvR5gJI Choosing a device is never easy as it is, but the new Apple Silicon SoCs for Mac have given the market a good shake and made the choice even harder. Which MacBook should I buy? How different are they? It's hard to figure out. Besides, searching for thorough tests is one hell of a job. In this article, I'll give you a proper comparison of build speeds using some real-life Android projects and a number of different MacBook models. In addition to that, I'll tell you which one to buy heading into 2022. Test computers In this test, I used the latest MacBook Pro laptops powered by Intel as well as some of the latest MacBooks with M1. iMac 27" Late 2015 Intel Core i7 6700K | 24 GM RAM MacBook Pro 16" 2019 i7 9750H 6 CPU cores/12 threads | 16 GB RAM MacBook Pro 16" 2019 i9 9880H 8 CPU cores /16 threads | 32 GB RAM MacBook Air 2020 M1 | 16 GB RAM MacBook Pro 14" 2021 M1 Pro 8 CPU | 16 GB RAM MacBook Pro 14" 2021 M1 Pro 10 CPU | 32 GB RAM MacBook Pro 16" 2021 M1 Pro 10 CPU | 32 GB RAM MacBook Pro 16" M1 Max | 32 GB RAM I added my old iMac 27" Late 2015 to the test to see how much progress the new models of Macs made.Test method Making sure all computers work in equal conditions isn't easy, but I've tried to make it perfect: Using the latest revision of JDK 11. For Apple Silicon I used Zulu ARM JDK Using Gradle 7.3.3 to build projects (the latest available version in moment of testing) Disconnecting the external displays Connecting all computers to a power source Close as many programs as possible, including the background ones Close Android Studio! Switch computer into performance mode (if available) Placing all laptops on a hard flat surface to let the airflow come in and cool down the laptop Not touching the computers during tests Turning off the Spotlight indexing or adding the test project folder to exceptions. If you know of any other conditions to be considered before benchmark testing, I'd be happy to read ## Meet dpi.lv: More than you probably wanted to know about screen DPI DevFeed: [Meet dpi.lv: More than you probably wanted to know about screen DPI]() Original publisher: [Read original article]() Author: Lea Verou Published: 2013-06-10T00:00:00Z Content type: release Language: en Sources: [Lea Verou's blog]() Topics: [screen](), [User interface design](), [JSON](), [Responsive Design]() Tags: [app](), [batteries](), [blog](), [calculator](), [canada](), [code](), [console](), [devices](), [displays](), [dpi-ppi](), [faq](), [file](), [flight](), [hassle](), [json](), [laptop](), [macbook-air](), [math](), [original](), [releases](), [screen](), [separate](), [thunderbolt]() ### AI overview dpi.lv is an open-source DPI/PPI calculator built to make screen pixel-density calculations easier. It includes a JSON-backed list of devices with pre-calculated data, DPI/PPI FAQs, and URL-hash link sharing. Its result display resizes and animates to match the selected resolution's aspect ratio. On displays with multiple dots per pixel, such as Retina screens, its guessed resolution may be wrong, so users need to enter the correct resolution in the editable fields. The author says the project is MIT-licensed and notes that its JavaScript still needs cleanup. ### Source excerpt Yesterday (Sunday) I was on a 9.5 hour flight from Canada with no inflight entertainment (well, thanks Air Canada), so I did what every bored human being would do instead of watching movies: I decided to code an app! And out of the infinite set of possible apps somebody can make, I decided to make an app to calculate screen DPI/PPI. You might be wondering if I'm still (?) sane, but you might be surprised to hear I found myself calculating screen PPIs quite frequently and wanted to save myself the hassle of doing the math every time. I'm a curious person and I wanted to know, even about products I would never buy and even when it wasn't listed in the tech specs. Yes, my hobbies are somewhat weird. :o I first thought about doing such an app a while ago, but never found the time to code it. The last time I had thought about it was a few days ago at the SF Apple Store with a friend. We were looking at the 27" Apple Thunderbolt displays in awe and thought they must have huge pixel density. After a few calculations in the console (which ironically produced a result faster than the Apple guy my friend asked), it turned out it was only ...102. "I need to code an app to make this sort of calculation easy! People are being misled by marketing!" I thought. Fast forward to my flight. You didn't expect my laptop battery to last for 9.5 hours, right? Yeah, MacBook Air batteries are good, but not *that* good. Of course it eventually died so I had to find other ways to pass my time (I ended up sleeping -- or trying to). However, by the time it died, I had gone over the threshold of being able to give it up, so I spent the rest of the day finishing it, despite my obvious jetlag and sleepiness. I was in the zone -- You don't just go sleeping when you're in the zone, right? Besides the DPI/PPI calculator, I added a few other fun things too: A list of devices with pre-calculated data (stored in a separate JSON file, which makes it easy to update -- *hint, hint*) Wrote a few FAQ items about