dlelr.over-blog.com/
18 Janvier 2021
Hi guys, I'm currently on the path of learning app development with Xcode but my MacBook Pro from 2012 is making it impossible to use Xcode comfortably, I'm looking to upgrade. What MacBook is best for Xcode in 2020 and would I be better off with 16GB ram or would 8GB ram suffice? Appreciate any help. Xcode, iOS, Swift and The MacBook Pro The world is different today. Xcode simply doesn't run on an i486 PC, and you can't save your app's source code on a 1.44 MB floppy disk anymore. Your Mac probably doesn't have a CD drive, and you store your Swift code in a cloud-based Git repository somewhere.
Xcode 12 builds Universal apps by default to support Mac with Apple Silicon, often without changing a single line of code. Designed for macOS Big Sur. Xcode 12 looks great on macOS Big Sur, with a navigator sidebar that goes to the top of the window. Use XCode simulator to emulate an iOS device. In this tutorial, we will loo k at how you can use the XCode simulator to debug a web page. XCode is a free IDE available for Mac devices used for developing all kind of apps for Apple devices: iOS apps, Mac apps, Watch apps and more. XcodeBenchmark contains a large codebase to measure the compilation time in Xcode. You are probably familiar with the following question: 'Should I buy an i5, i7, or even i9 processor for iOS/macOS development?' XcodeBenchmark is initially created for Max Tech YouTube channel to compare the performance of new iMacs 2020.
How fast does your MacBook need to be to comfortably code iOS apps with Xcode? Is a MacBook Pro from 2-3 years ago good enough to learn Swift programming? Let's find out!
Here's what we'll get into:
I've answered a lot of 'Is my MacBook good enough for iOS development and/or Xcode?'-type questions on Quora. A few of the most popular models include:
These models aren't the latest, that's for sure. Are they good enough to code iOS apps? And what about learning how to code? We'll find out in this article.
Since 2009 I've coded more than 50 apps for iOS, Android and the mobile web. Most of those apps, including all apps I've created between 2013 and 2018, were built on a 13″ MacBook Air with 8 GB of RAM and a 1.3 GHz Intel i5 CPU.
My first MacBook was the gorgeous, then-new MacBook White unibody (2009), which I traded in for a faster but heavier MacBook Pro (2011), which I traded in for that nimble workhorse, the mighty MacBook Air (2013). In 2018 I upgraded to a tricked out 13″ MacBook Pro, with much better specs. Download adobe reader 11 0 01 offline installer.
Frankly, that MacBook Air from 2013 felt more sturdy and capable than my current MacBook Pro. After 5 years of daily intenstive use, the MacBook Air's battery is only through 50% of its max. cycle count. It's still going strong after 7 hours on battery power.
In 2014, my trusty MacBook Air broke down on a beach in Thailand, 3 hours before a client deadline, with the next Apple Store 500 kilometer away. It turned out OK, of course. Guess what? My current MacBook Pro from 2018, its keyboard doesn't even work OK, I've had sound recording glitches, and occasionally the T2 causes a kernel panic. Like many of us, I wish we had 2013-2015 MacBook Air's and Pro's with today's specs. Oh, well…
Sign up for my iOS development course, and learn how to build great iOS 14 apps with Swift 5 and Xcode 12.
When I was about 11 years old I taught myself to code in BASIC, on a 100 Mhz i486 PC that was given to me by friends. It had a luxurious 16 MB of RAM, initially only ran MS-DOS, and later ran Windows 3.1 and '95.
A next upgrade came as a 400 Mhz AMD desktop, given again by friends, on which I ran a local EasyPHP webserver that I used to learn web development with PHP, MySQL and HTML/CSS. I coded a mod for Wolfenstein 3D on that machine, too.
We had no broadband internet at home back then, so I would download and print out coding tutorials at school. At the one library computer that had internet access, and I completed the tutorials at home. The source codes of turn-based web games, JavaScript tidbits and HTML page snippets were carried around on a 3.5″ floppy disk.
Later, when I started coding professionally around age 17, I finally bought my first laptop. My own! I still remember how happy I was. I got my first gig as a freelance coder: creating a PHP script that would aggregate RSS feeds, for which I earned about a hundred bucks. Those were the days!
The world is different today. Xcode simply doesn't run on an i486 PC, and you can't save your app's source code on a 1.44 MB floppy disk anymore. Your Mac probably doesn't have a CD drive, and you store your Swift code in a cloud-based Git repository somewhere.
Make no mistake: owning a MacBook is a luxury. Not because learning to code was harder 15 years ago, and not because computers were slower back then. It's because kids these days learn Python programming on a $25 Raspberry Pi.
I recently had a conversation with a young aspiring coder, who complained he had no access to 'decent' coding tutorials and mentoring, despite owning a MacBook Pro and having access to the internet. Among other things, I wrote the following:
You're competing with a world of people that are smarter than you, and have better resources. You're also competing against coders that have had it worse than you. They didn't win despite adversity, but because of it. Do you give up? NO! You work harder. It's the only thing you can do: work harder than the next person. When their conviction is wavering, you dig in your heels, you keep going, you persevere, and you'll win.
Winning in this sense isn't like winning a race, of course. You're not competing with anyone else; you're only really up against yourself. If you want to learn how to code, don't dawdle over choosing a $3.000 or a $2.900 laptop. If anything, it'll keep you from developing the grit you need to learn coding.
Great ideas can change the world, but only if they're accompanied by deliberate action. Likewise, simply complaining about adversity isn't going to create opportunities for growth – unless you take action. I leapfrogged my way from one hand-me-down computer to the next. I'm not saying you should too, but I do want to underscore how it helped me develop character.
If you want to learn how to code, welcome adversity. Be excellent because of it, or despite it, and never give up. Start coding today! Don't wait until you've got all your ducks in a row.
The recommended system specs to run Xcode 11 are:
Looking for a second-hand Mac? The following models should be fast enough for Xcode, but YMMV!
When you're looking for a Mac or MacBook to purchase, make sure it runs the latest version of macOS. Xcode versions you can run are tied to macOS versions your hardware runs, and iOS versions you can build for are tied to Xcode versions. See how that works? This is especially true for SwiftUI, which is iOS 13.0 and up only. Make sure you can run the latest!
Pro tip: You can often find the latest macOS version a device model supports on their Wikipedia page (see above links, scroll down to Supported macOS releases). You can then cross-reference that with Xcode's minimum OS requirements (see here, scroll to min macOS to run), and see which iOS versions you'll be able to run.
Awesome! We've discussed what you need to run Xcode on your Mac. You might not need as much as you think you do. Likewise, it's smart to invest in a future-proof development machine.
Whatever you do, don't ever think you need an expensive computer to learn how to code. Maybe the one thing you really want to invest in is frustration tolerance. You can make do, without the luxury of a MacBook Pro. A hand-me-down i486 is enough. Or… is it?
Want to learn more? Check out these resources:
Sign up for my iOS development course, and learn how to build great iOS 14 apps with Swift 5 and Xcode 12.
My current computer (a mid-2010 Macbook Pro, with 16GB of non-native RAM and a non-native SSD) is struggling to cope with the most recent incarnations of Xcode (currently running v9.2). Build and Run commands are still executed in reasonable time, but the speed with which I can write code is at times so slow that I'll be close to tears!. For example, although it takes me just a few seconds to type two or three lines of Swift, it can often take Xcode a minute or more to get the text onto the screen (a stand-alone Dell monitor connected via a mini-display port cable).
The problem seems to be that the autocomplete/code-sense features of Xcode are stretching Xcode to breaking point - the fan starts up within minutes of starting work, and generally don't stop until I do. The standard advice for remedying this (deleting derived data) has little impact. What's more, although restarting the computer does have some effect, it's not long-lasting, and isn't a long-term solution.
I'm at the point now that I'm willing to fork out for a new computer but want to spec it wisely: spending extra money only on upgrades that will make a difference within Xcode. To my untrained eye the choice seems to be between getting extra RAM, a faster processor, or both. Am I right about this? If I am, what should I do? if I'm not, what am I missing?
Native Mac apps built with Mac Catalyst can share code with your iPad apps, and you can add more features just for Mac. In macOS Big Sur, you can create even more powerful versions of your apps and take advantage of every pixel on the screen by running them at native Mac resolution. Apps built with Mac Catalyst can now be fully controlled using just the keyboard, access more iOS frameworks, and take advantage of the all-new look of macOS Big Sur. There's never been a better time to turn your iPad app into a powerful Mac app.
When an app built with Mac Catalyst runs on macOS Big Sur, it automatically adopts the new design. The new Maps and Messages apps were built with the latest version of Mac Catalyst.
Your iPad app can be made into an excellent Mac app. Now's the perfect time to bring your app to life on Mac. The latest version of Xcode 12 is all you need. Begin by selecting the 'Mac' checkbox in the project settings of your existing iPad app to create a native Mac app that you can enhance further. Your Mac and iPad apps share the same project and source code, making it easy to make changes in one place.
Your newly created Mac app runs natively, utilizing the same frameworks, resources, and runtime environment as apps built just for Mac. Fundamental Mac desktop and windowing features are added, and touch controls are adapted to the keyboard and mouse. By default, your app will scale to match the iPad's resolution. On macOS Big Sur, you can choose 'Optimize interface for Mac' to use the Mac idiom, running your app using the native resolution on Mac. This gives you full control of every pixel on the screen and allows your app to adopt more controls specific to Mac, such as pull-down menus and checkboxes.
The new APIs and behaviors in macOS Big Sur let you create even more powerful Mac apps. Apps can now be fully controlled using just the keyboard. You can create out-of-window and detachable popovers, control window tabbing using new window APIs, and make it easier for users to select photos in your app by using the updated Photos picker. iOS Photos editing extensions can now be built to run on Mac. And your app is even easier to manage when it's running in the background with improved app lifecycle APIs.
Mac Catalyst adds support for new and updated frameworks to extend what your apps can do on Mac. HomeKit support means home automation apps can run alongside the Home app on Mac. The addition of the ClassKit framework lets Mac apps track assignments and share progress with teachers and students. Plus, there are updates to many existing frameworks, including Accounts, Contacts, Core Audio, GameKit, MediaPlayer, PassKit, and StoreKit.
Download Xcode 12 and use these resources to build native Mac apps with Mac Catalyst.
/image%2F6313778%2F20210327%2Fob_730804_google-chrome-pc-requirements.png)
/image%2F6313778%2F20210327%2Fob_206ba6_latest-stable-chrome.png)
/image%2F6313778%2F20210220%2Fob_8262ce_watch-directv-on-internet.jpeg)
/image%2F6313778%2F20210220%2Fob_01189c_web-search-protection.png)