To get a better idea if its worth it for your workflow review your apps to see which ones are multithreaded, then figure out what actions you perform that consumes the most time. Then you should be able to extrapolate if given the needed work, costs and risks of damage is worth the effort. As an example is 10 minutes of time waiting for an image to convert from one file type to another going to benefit you? One or two files likely not, hundreds for sure!
I'm a photographer so my needs are a bit different from a game developer,
-
But I'm sure this is not the best system for that as you need a collection of different skills between the coding you need the graphics (drawing) and the animation. All of these really require a more powerful system as well as a larger display to work off of if you are a serious developer for Mac games. IF you are doing iOS gaming then you might be able to work in the smaller screen but I'm sure you'll want more power.
+
But I'm sure this is not the best system for that as you need a collection of different skills between the coding you need the graphics (drawing & animation). All of these really require a more powerful system as well as a larger display to work off of if you are a serious developer for Mac games. IF you are doing iOS gaming then you might be able to work in the smaller screen but I'm sure you'll want more power.
To get a better idea if its worth it for your workflow review your apps to see which ones are multithreaded, then figure out what actions you perform that concusses the most time. Then you should be able to extrapolate if given the needed work, costs and risks of damage is worth the effort. As an example is 10 minutes of time waiting for an image to convert from one file type to another going to benefit you? One or two files likely not, hundreds for sure!
+
To get a better idea if its worth it for your workflow review your apps to see which ones are multithreaded, then figure out what actions you perform that consumes the most time. Then you should be able to extrapolate if given the needed work, costs and risks of damage is worth the effort. As an example is 10 minutes of time waiting for an image to convert from one file type to another going to benefit you? One or two files likely not, hundreds for sure!
I'm a photographer so my needs are a bit different from a game developer,
But I'm sure this is not the best system for that as you need a collection of different skills between the coding you need the graphics (drawing) and the animation. All of these really require a more powerful system as well as a larger display to work off of if you are a serious developer for Mac games. IF you are doing iOS gaming then you might be able to work in the smaller screen but I'm sure you'll want more power.
To get a better idea if its worth it for your workflow review your apps to see which ones are multithreaded, then figure out what actions you perform that concusses the most time. Then you should be able to extrapolate if given the needed work, costs and risks of damage is worth the effort. As an example is 10 minutes of time waiting for an image to convert from one file type to another going to benefit you? One or two files likely not, hundreds for sure!
-
To get a better idea if its worth it for your workflow review your apps to see which ones are multithreaded, then figure out what actions you perform that concusses the most time. Then you should be able to extrapolate if given the needed work, costs and risks of damage is worth the effort. As an example is 10 minutes of time waiting for an image to convert from one file type to another going to benefit you? One or two files likely not, hundreds for sure!
+
I'm a photographer so my needs are a bit different from a game developer,
+
+
But I'm sure this is not the best system for that as you need a collection of different skills between the coding you need the graphics (drawing) and the animation. All of these really require a more powerful system as well as a larger display to work off of if you are a serious developer for Mac games. IF you are doing iOS gaming then you might be able to work in the smaller screen but I'm sure you'll want more power.
The 2012 series came with three options 2.7 or 2.9 GHz (Core i5) or 3.1 GHz (Core i7)
Depending on your applications a single threaded app won't see much improvement, a multi-threaded app will see the most! As you can compare here:
* [https://everymac.com/systems/apple/imac/specs/imac-core-i5-2.7-21-inch-aluminum-late-2012-specs.html|21.5" iMac Core i5 2.7GHz (Late 2012)]
* [https://everymac.com/systems/apple/imac/specs/imac-core-i7-3.1-21-inch-aluminum-late-2012-specs.html|21.5" iMac Core i7 3.1GHz (Late 2012)]
To get a better idea if its worth it for your workflow review your apps to see which ones are multithreaded, then figure out what actions you perform that concusses the most time. Then you should be able to extrapolate if given the needed work, costs and risks of damage is worth the effort. As an example is 10 minutes of time waiting for an image to convert from one file type to another going to benefit you? One or two files likely not, hundreds for sure!