4 ms·
Compiling and building. A really big C++ project can take hours to build. My 18 core/128GB iMac Pro builds in 2.25 hours what it takes a 64 GB, 12 core Mac Pro
by briandear 9y ago
Compiling and building. A really big C++ project can take hours to build. My 18 core/128GB iMac Pro builds in 2.25 hours what it takes a 64 GB, 12 core Mac Pro over 5 hours to build.
I’m probably on the far extreme of normal, but more cores and more RAM make a huge difference in tasks like rendering, compiling, building projects with huge dependency chains.
For writing some JavaScript web application, the serious horsepower makes a only marginal difference in actual productivity. But on “big” stuff, it can save hours per day, which means savings of real money.
- STRML 9y agoIt still can on JS toolchains. There is multiprocess webpack (happypack) now, Flow threads really well, and the extra cores can even help when restarting a bunch of processes at once and live reloading. Shaving off even a second helps productivity when you do it dozens/hundreds of times a day.
- loup-vaillant 9y ago> A really big C++ project can take hours to build. My 18 core/128GB iMac Pro builds in 2.25 hours what it takes a 64 GB, 12 core Mac Pro over 5 hours to build. While I understand such monsters do exist, I cannot help but balk in horror at the though of millions of lines of code written in such an unsafe language. Things must have gone wrong on several levels to get to this point.