-
On the subject of the Mac Pro 2019...
"Where I think this whole saga gets very frustrating for a lot of current and potential Mac Pro customers is that Apple is describing a product — a powerful, professional-grade, modular desktop computer — that already exists: it’s the tower-style “cheese grater” Mac Pro. While Apple is working away to reinvent one of the most critical components of a professional user’s workflow, those users are stuck with product choices that may not quite fit." - Nick Heer, Pixel Envy.
This should be embossed onto Apple's Professional Workflow's HQ. To paraphrase Paul Haddad, just throw some Xeons in a box. This should be the easiest product release in Apple's entire lineup. Pros just want a box that can house multiple storage devices, PCIe slots, the latest I/O (even thunderbolt is entirely optional when you have PCIe) and lastly, user serviceable. That's really it. They could literally reuse the case from the Power Macintosh 9600 and we wouldn't care.
Apple envisioned the 2013 as a Mac that could be carted onto the set of a Hollywood style shoot and edit dailies on the spot with Final Cut Pro X, but conceptualizing it entirely in a vacuum. While Apple takes the approach the customer doesn't know what they want, that's true in the consumer market but a massive mistake when you're dealing with professional. They know exactly what the want.
If you want evidence of the demand for such a mythical device: search "12 core Mac Pro" in eBay and try and name another computer from 2010 that fetches over 1000. Many cost more than the current 5k iMac, new from Apple.
-
Installing a GeForce GTX 1060 / 1070 / 1080 into a Mac Pro 2010/2012
Updated 04/03/19: When I wrote this guide, NVidia drivers were still being released for the current version of macOS, 10.12-10.13. Sadly, Apple and NVidia relations have seemed to have come to a head. NVidia states that it is actively being blocked from releasing drivers for its GeForce cards for 10.14.x+. I highly recommend AMD video cards over NVidia as this seems unlikely to change. My GPU section of the Definitive Mac Pro Upgrade Guide contains more info on this spat, as well as current information. For posterity, I've left the upgrade guide below largely intact with a few minor edits to help reflect more current information.
Years ago, I posted a guide on how to install a GeForce 760 or 770 into a 2008 Mac Pro. I included a fair amount of benchmarks to boot. It's lasted me well over three years and made the jump to a 2010 Mac Pro, but I finally pulled the trigger on a 1060. You can install a 10x0 series into a 2008 Mac Pro as well, but this guide specifically focuses on the 2010-2012 Mac Pros. The main differences between the two are the PCIe power port positions and the lack of the annoying PCIe bar hanger latch. Upgrading only took me a few short minutes, the longest part of the process was plugging/unplugging all my connected devices. There's hardly any special skills or knowledge needed.
Lastly, I've created the Definitive Mac Pro upgrade guide, which includes a lot of information about GPUs (and plenty more) not covered in this article. I suggest taking a look at the GPU section as it covers AMD chipset cards and flashable cards.
Before you get started, there are a few things one should be aware of:

- Important! There are currently no drivers for the off-the-shelf GeForce GPUs for MacOS 10.14.x. When I wrote this guide, a year ago in 2018, this was before Apple stonewalled NVidia from releasing drivers for Mojave. If you want to run 10.14+, it is AMD or bust. I cannot recommend purchasing an NVidia GPU if you have any desire to run 10.14+.
- Both AMD and NVidia make EFI compatible graphics cards that will work on OS X. NVidia cards (GeForce 700 through 1000 series) only require installing the web drivers whereas the Sapphire PULSE Radeon RX 580 8GB is (so far) is the only RX 580 that works without any hacking/flashing.
- The NVidia drivers currently require 10.12 Sierra or above to use the 1000 series cards.
- The NVidia (nor the AMD RX 580) card will not allow you to see the EFI boot screen with the card plugged in (the screen you see if you hold down the option key and the Apple logo). If this is important, I highly recommend keeping an original card around (or flashed). I personally use an ATI Radeon HD 2600 XT (so old that it's not AMD) that shipped with my 2008 Mac Pro computer since its modified to be fanless, but any will do, flashed or factory as long as it can display the Apple logo on boot. You can operate the computer without a card capable of displaying the EFI boot screen. However, you’ll have to manage booting using Start Up Disk in OS X and use the bootcamp tools in Windows to switch boot drives, and you will not see any picture until the login screen.
- The RX 580 and GTX 1060 are fairly evenly performant, but as of writing this, the 1060 is cheaper since any model will suffice, and requires less power and can be found to be significantly quieter in some models. (edit: the part about price was true, now RX 580s are cheap.)
- Modern graphics cards require additional cabling and rarely do the graphics card ship with additional power cables. You'll need to purchase the power cables separately. Also, the Mac Pros require mini PCIe to PCIe power cables.
- Modern GPUs are quite performant (still) on Mac Pros. A 2010 Mac Pro with a GeForce 1080 eats an iMac 5k alive in GPU tests (unsurprisingly).
- Not every GPU port may work with the NVidia drivers depending on the card config. In the case of my GeForce GTX 760, all ports worked sans one of the DVI ports. As a general rule, count on most but not all ports working and do diligent research. The best places to check are MacRumors and TonyMacX86 forums.
Step 1:
If you're upgrading from a stock card, you may be unaware that the PCIe bus doesn't deliver enough power thus PCIe power additional cables are required. The Mac Pros include two power ports for PCIe power but use special low profile cabling often referred to "Mini PCIe" located on the motherboard. To effectively power your GPU, you need to draw power from BOTH ports. To reiterate, you cannot simply use a Y cable from a single motherboard PCIe power port. This seems to be the biggest point of confusion for users.
The GeForce 1060 / 1070 / 1080 require external power. Also, the 1060 requires an 8 pin power cable, the Mac Pro defaults are 6. You'll need a 6 to 8 pin power adapter. I ordered the following: two of the mini PCIe to PCI-e Power Cable (disregard the G5 mislabeling) and a 6 to 8 pin PCIe power adapter, which are much more easily found. Users have informed there are 6 pin mini PCIe to PCI-e Power Cable to 8 pin cables as well.
If you are looking to run cards that draw exceptionally high power (more than 250 watt), please visit House of Moth's Pixlas Mod instructions. This is a modification that allows GPUs to draw more power from the PSU in the Mac Pro. Fortunately, the Mac Pro has a pretty beefy PSU, and users have been known to run dual 1080 Tis or Vega 64s using this modification.
Cable requirements
This may differ between card manufacturer, but the following is true for the base models.
- GTX 1060: Power ports: 6 pin + 8pin power ports
- GTX 1070: 6 pin + 8pin power ports
- GTX 1080: two 8pin power ports
You will likely need to purchase the appropriate cabling as the GPUs will not come with it as the Mac Pros use the mini-PCIe power standard. If you card has two ports: 6 pin and an 8 pin power, you will need to provide both a 6 and 8 pin power cable.
The MSI GTX 1060 is massive, roughly 11 in x 5.5 in x 1.5 in thanks to the oversized cooler.Next any off the shelf GeForce GTX 1060 or GTX 1070 or GTX 1080 will do. Personally, I picked up the GTX 1060 MSI Gaming X 6 GB, which is regarded as one of the least noisy cards on the market. With bitty coins wrecking pricing, I just wasn't willing to pay for the 1070. I hope all cryptocurrency fails so we can go back to normal pricing, but I digress. I paid $355, which isn't great but many of GTX 1060s makes are going for more. Update: GPUs seem to have normalized pricing wise again.
Step 2:
Pre-install the NVidia drivers, especially if you do not have a Mac EFI card. TonyMacX86 has a nice handy guide to what version based on OS 10.13 High Sierra or 10.12 Sierra or alternately.
Plug in your power cables first! The GeForce 1060 is big; it dwarfs my 760. Fortunately, the Mac Pro 2010 / 2012 ports are much easier to access than in a 2008 Mac Pro.
The low profile mini PCIe power cables are located in the bottom back of the PCIe chamber.
Step 3:
Do the usual remove slot thumb screws, remove/move old GPU, etc. The Mac Pro 2010/2012s have a PCIe rail hanger, originally when I installed this, I didn't realize the latch sets and unsets the hanger as it was my first time installing a card into a Mac Pro 5.1. I originally was able to install the card without it using a bit of muscle then shortly thereafter, I discovered the latch but didn't bother updating the guide. Later, Several readers took time to point out that the latch for the PCIe chamber (a few with a bit of a condensing tone, as nothing seems to make some people happier than telling other they're wrong). Rather than save face, here's how you avoid being a dumb dumb like I was. If you're finding it difficult to install the card, the PCIe chamber latch is located on the grey plastic assembly. Press the button the assembly and slide it back. Use the bottom-most slot as the card is dual height.
If you're looking for more information on how to install a PCIe card in a Mac Pro, everymac.com has plenty of information including videos.

Benchmarks
I haven't spent much time with the card, but I did fire up on OS X Tomb Raider (2013) via Steam. At 2560 x 1440 with all settings maxed (16x Anisotropic filter etc.), I managed an average frame rate of 57.6 FPS on a 12x 2.9 GHz 2010 Mac Pro with 32 GB of RAM.
It's no secret that there's always been a gaming performance gap, macOS sadly scores quite poorly compared to its Windows counterpart, so it's only fair to compare Mac to Mac or Windows to Windows and not Mac to Windows when considering the gains. Rather than benchmarking Windows, which isn't my daily driver, I'm more interested in how the GPU affects macOS. Below are my Uniengine v4 benchmarks vs. when I ran them against my 2008 Mac Pro. Despite the low marks when compared to running Uniengine in Windows, The Mac Pro 2010 is twice as fast by the benchmarks as my previous setup of a 2008 Mac Pro running a GeForce 760. One of the more fascinating things I learned when trying my hand at a Hackintosh was that the 3rd generation 3770k i7 wasn't quite enough to completely best the over-engineered Mac Pro despite having a faster bus / CPU, but merely matched it. If/when I have more time, I may swap the GPUs to see if the scores are as GPU dependent as they seem.
Uningine Benchmarks
OpenGL 2560 x 1440 8xAA FullScreen Quality:Ultra Tessellation: Extreme
Mac Pro 2010 (Xeon X5670 2x 2.93Ghz) + GeForce GTX 1060 + 32 GB RAM + Samsung 840 750 GB SSD
FPS: 33.2
Score: 837
Min FPS: 7.4
Max FPS: 72.1
Mac Pro 2008 (Xeon E5462 2x 2.8 Ghz) + GeForce GTX 760 + 14 GB RAM + Samsung 840 750 GB SSD
FPS: 16.1
Score: 405
Min FPS: 5.8
Max FPS: 37.4
Hackintosh (i7 3770k 3.5 GHz) + GeForce GTX 760 + 16 GB RAM + Samsung 840 750 GB SSD
FPS: 15.7
Score: 396
Min FPS: 6.9
Max FPS: 37.3
Hackintosh (i7 3770k 3.5 GHz) + GeForce GTX 770 + 16 GB RAM + Samsung 840 750 GB SSD
FPS: 18.8
Score: 474
Min FPS: 7.6
Max FPS: 47.5
Mac Pro 2010 GeForce 1060 vs eGPU setups
I used benchmarks provided by a thread on eGPU.io, credit goes to the forum posters for the comparisons. There aren't any perfect comparisons so here's a run of the GTX 1060 in my Mac Pro 2010 vs. Thunderbolt 3 Mac running the considerably better 1070 and an iMac 2011 running a 1060. Depending on perspectives, the eGPUs do quite well, or the Mac Pro 2010 is fairly viable. The big difference in eGPU vs. internal.
OpenGL 1920 x 1080 8xAA FullScreen Quality:Ultra Tessellation: Extreme
Mac Pro 2010 (Xeon X5670 2x 2.93Ghz) + GeForce GTX 1060 + 32 GB RAM + Samsung 840 750 GB SSD
Score: 1306
FPS: 51.5
Min FPS: 19.3
Max FPS: 106.5
iMac 2011 27 inch (3.4 GHz) + GTX 1060 6GB
Score: 1226
FPS: 48.7
Min FPS: 8.4
Max FPS: 96.9
MacBook Pro late 2016 13 inch (2.9 GHz) + MSI GTX 1070 6GB Aero OC
Score: 1825
FPS: 72.4
Min FPS: 9.8
Max FPS: 138.8
macOS vs Windows
As previously mentioned, this shouldn't come as any sort of surprise, but Windows 10 gaming is still quite a bit of ahead of Apple, although Metal shows promise. As of right now, DX11 is the king regardless of your opinion on it in performance. Windows performs a full 10 FPS faster, or about 24% faster. in the same benchmark with the same settings.
OpenGL 1920 x 1080 8xAA FullScreen Quality:Ultra Tessellation: Extreme
macOS 10.12.6
Score: 1306
FPS: 51.5
Min FPS: 19.3
Max FPS: 106.5
Windows 10, 64 bit, Direct 3D 11
Score: 1609
FPS: 63.9
Min FPS: 21.7
Max FPS: 135.3
I plan to update the benchmarks in time. I may bring in the GeForce 760 for a reference when I have more time and possibly test in a 2008 Mac Pro in the future.
Troubleshooting
It's a good idea for the first boot to keep around an EFI card, as you may have to enable the web drivers. Also, I encountered the error of Mac NVidia Web Drivers fail to update or cannot remove Kext files" when updating my OS recently; you'll want to follow the instructions I posted to deinstall the drivers if this happens to you.
Final Thoughts
Upgrading GPUs isn't something I'd normally wax philosophical on, but we're post-golden era for OS X, and the Mac Pro is a relic.
Ever since NVidia has shipped it's web drivers, gone are the sketchy days of flashing a 6970 and using a rom creator. Installing off-the-shelf GPUs has gone from tribal knowledge to common knowledge for the Mac Pro user since I wrote my "how to" guide for the 760. Ironically, it wasn't until Apple killed upgradability that the dream of off-the-shelf GPUs could be bought without the infamous Apple-tax. I debated even not calling this article a "how to". The downside is despite the EFI compatible ROMs preloaded on the 700+ GeForce cards; they're not EFI boot screen compatible on OSX sadly. The only game in town is macvidcards.com which according to all accounts on MacRumors is a legit source, but I find the idea of hoarding an EFI hack a little irksome. It's hard to complain too much as NVidia has quietly kept the Mac Pro and Hackintosh community happy, self-included. There's no specialized knowledge needed to upgrade your GPU or abnormal risks of a bad firmware flash. The only caveat is you'll want to keep an EFI card around for major OS updates.
Upgrading the GPU is probably second best thing outside of an SSD to make an old Mac Pro feel young if you desire to run 4k and/or use any sort of motion graphics software, play games, etc. It's hard not to recommend upgrading as there's a strong case to be made for removable GPUs. A Mac Pro with armed with a higher end GPU will best even the mighty iMac Pro handedly in GPU related benchmarks.
eGPUs are viable but not as performant. There's just simply no topping a PCIe card slots although we're probably coming to the end of the Mac Pro era if/when Thunderbolt gets an update. Thunderbolt 3 is fast but still has a lot of room for improvement. It's 40 gigabits 5.1 GB/ is approximately the speed of a PCIe 3.0 4x slot. If/when Thunderbolt gets an upgrade (Thunderbolt 4?) Bumping it up two-fold would bring it to roughly 8x PCIe 3.0 or shy of a 4x PCI 4.0. 8x PCIe currently offers roughly 95-99% of the performance for gaming, even with a GeForce GTX 1080. That said, PCIe 4.0 coming out very soon, and PCIe 5.0 may be only a year and change out, boosting PCIe 16x to a truly mind-boggling 63 GB/s a sec (504 gigabits per second). Thunderbolt won't be catching up PCIe any time soon, but it could be for practical purposes concerning consumer GPUs.
Also to add to the end of the cheese-grater era is the ever-looming Mac Pro. The word "modular" has been tossed around recently quite a bit to describe the next iteration. The Mac Pro flames have been stoked yet again with the very curious mention in Bloomberg's rumor-filled article Apple is said to plan to move from Intel to own Mac chips. It's highly unlikely Apple has anything in the pipeline that's even near the iMac's i9 configurations but will sport the same Bridge2,1 ARM A10 CPU that's found in the iMac Pro. Also, the new Mac Pros are at least out to 2019 and will be shaped by workflows.
The Bridge chipsets allow for some truly unexciting features like "Hey Siri" to be always on even when the computer shut down and/or to manage graphical keyboards like the one found in the MacBook Pros.
My gut feeling is if the iMac Pro is any sort of indicator, the next Mac Pro will be absurdly expensive and my guess is it'll sport less upgradability than the 2006-2012 "Cheese grater" Mac Pros but more than the abysmal 2013 "trash can" Mac Pro. Floating rumors around ARM CPUs seems a step away from modularity but a step closer to iOSifying Macs to annual upgrades, stopping the Hackintosh community and locking users out of OS upgrades after five years. I am not optimistic about the future of the Mac Pro or the Macintosh.
The Mac Pro has been a bit of an outlier. I used a 2008 Mac Pro for ten years. When I bought it, I was still in a 3-year upgrade cycle, going from G3 -> G4 -> G5. I used my Mac Pro 2008 longer than all three computers combined and only did I recently replace it with a 2010 Mac Pro. That's a significant reduction in computer sales Apple, to engineer a computer that can be used viably for ten years and I worry they understand that too well. All for the cash, man...
For now, Mac users have only three choices: eGPUs, old Mac Pros, and the elusive Hackintosh. Any path will get you serious gains. My guess is the 1000 series is likely the last stop for most cheese grater users as we're at a crossroads: Thunderbolt is almost fast enough for GPUs (and PCIe enclosure are becoming more popular), and Apple may yet give us a modular computer.
04/3/19 Update
I've been meaning to update this guide, but all my energy has gone into the Definitive Mac Pro upgrade guide which covers much of the ground in here. I've added notes about the Pixlas mod, Mojave compatibility and some minor editing.
08/2/18 Update
Minor Editing update, thanks to Stuart K for spotting a typo.
04/2/18 Update
Some minor proofing and added in a lot more benchmarks. Kids love benchmarks.
04/5/18 Update
Final Thoughts ended up long-winded.
-
Mac nVidia Web Drivers fail to update or cannot remove Kext files
With the nVidia graphics cards, in a Mac Pro (for those of us who refuse to let go) or PCIe Thunderbolt brethren, you probably by now are used to updating the drivers with every OS X version. However, sometimes when trying to update the nVidia drivers will give an installation failed after appearing initially to install correctly, ending with generic a "contact manufacturer" error. This error isn't exactly telling the full story, OS X post 10.10 has feature called System Integrity Protection, which protects certain system files from being modified by even the root user, which stops malicious installers/rootkits from tampering with macOS. This error also can adversely sometimes affect no longer used files such as items placed in the "incompatible items" folder, and when the user tries to delete them, will receive a "can't be modified or deleted because it's required by macOS" error message.
It's very important to understand that you should only do this with installers from a valid source before proceeding, such as directly downloading drivers from nVidia and using its certificate check or to remove offending drivers or files. After performing necessary changes, re-enable System Integrity Protection.
Step 1
First to make sure you have System Integrity Protection, go to the terminal and run
csrutil statusThis should return a status of enabled.
Step 2
Restart your Mac, and hold down Command-R keys during startup. This should boot your computer into recovery mode (alternately, you may be able to hold option and select the recovery partition). This may take a few minutes to boot.
Step 3
Ignore the installer prompt and select from the Utility, Terminal and run:
csrutil disableStep 4
Reboot. Perform the necessary change boot back into recovery mode as before.
csrutil enableReboot. You can now check using the
csrutil statusto see if the csrutil is working.
-
Kite - The Game Release On Steam

Long time friend, James Treneman published his first game on Steam, Kite. I saw in its earliest stages; it's a labor-of-love, a one-man operation, and it's now a full game. It's damn impressive that one person could make a game by himself, more impressive that it's a full-fledged game harkening back to Smash TV/Zombies Ate My Neighbors, mixing in RPG elements, missions, and pixel art.
-
New Old Beginning
I did something today for the first time in a decade. I ordered a Mac desktop. I've been using my Mac Pro 2008 for one decade, a feat I never realized would have been feasible.
What am I replacing my 2008 Mac Pro with? After evaluating the options, the iMac Pro was just too expensive for my blood with shelf life and the regular iMac just not as beefy as I'd like, especially in the GPU department. I ended up ordering a used 2010 Westmere Mac Pro, 12-core 2.93 GHz. I don't expect to get the same use out of it as my 2008. Just a year or two until we see if Apple does replace the Mac Pro with a modular computer.
By the numbers, the 8-year-old Mac Pro 2010 I'll be receiving bests my 2015 2.5 GHz MacBook Retina in most geekbench benchmarks in most scores. It bests even the current round of iMacs (excluding the iMac Pros) CPU performance wise. It'll be performant enough to be a Media PC/server should I choose to replace it in the upcoming years. It still strikes me as absurd that 12 core Mac Pros still hover around the $900-1800 mark depending on configuration. If that doesn't show demand, I don't know what does. Apple needs a modular computer for a certain class of users.
I've spent a fair amount of time blogging about the Mac Pro. The Mac Pro 2006-2012 remain the high water mark of desktops, the most elegantly designed towers, a refined mix of modularity, ease of access and raw power. Opening up the guts to see the (nearly) wire-free world, with an (almost) screwdriver free experience made cracking open a Mac Pro easier than even the era of the G3/G4 tower famed "Folding door" design. It's the painstaking beauty that really makes one appreciate the industrial design chops of Apple at it's best, features that only are touched a few times over the life of the computer are designed to be pleasant if not down right beautiful. The rare PC case today has a locking door that doesn't require screws. Rarer than that are cases that have sleds for storage. Then there's things that remain unique to the Mac Pro. PC cases still do not have handles or raised feet to this day, have chambered cooling, trays for CPU/RAM, or cable free designs. That's not even touching the aesthetics of the garish and utterly unsightly PC cases that still plague (if not make up the entirety of all) the market.
The end of the Mac Pro wasn't a surprise. You could see the tide receding with the rather modest and unimpressive 2012 update that failed to bring USB 3.0, SATA 3 and Thunderbolt to the desktop arena. The last embers of hope could be seen dwindling of the mythical creative professional smolder with the release of Final Cut Pro X. Laptops have crept into even the most hell-or-high-water desktop users lives as they caught up to their aging out-of-date in performance. Perhaps that's what killed the Mac Pro: engineering a computer that could last a decade.
-
Bootstrap 4 isn't quite what it's cracked up to be...
Love it or hate it, bootstrap has been a mainstay of front-end development since 2011. I've watched it grow and now, dare I say, flounder.
Rather than recant the ups and downs of each generation, Bootstrap 3 was wonderful for its simple flexibility. Most of the time, I whittled down Bootstrap to the bare minimums, often using only its grid (modified with my own breakpoints) and in-name-only classes like
.btn, as they're lexiconic to bootstrap. Any project, I could rely on like-markup and classes to Bootstrap even if the project was largely not-bootstrap. Bootstrap 3's Sass logic was simple and easy, but bootstrap 4 is silly.- Bootstrap 4 now uses Sass includes for breakpoints. Why? I cannot fathom a reason a realistic reason why. This is counter-intuitive. Everything is include hell.
- Most of the generative sass logic has been abstracted into mixin hell. It's starting to resemble the clusterfuck that is Foundation.
- The cross-dependency of Sass isn't predictable. Example: If you comment out forms, it will break nav functionality. There's a lot of senseless overhead.
- The JS is starting to suffer bloat. The collapse.js now is 375 lines, now up from 212 lines. Unminified, the Javascript has ballooned from 69k to 163k.
- Lite and dark themes are written into the code in such a way, it's not easily abstracted out.
- While small, some of the icons are inlined SVG images, which means removing if custom icons are used, more senseless payload.
Bootstrap 3 was the right mix of complexity to return on investment, but Bootstrap 4? I'm starting to think otherwise. So far, there's not enough compelling for Bootstrap . Conversion to REM units is nice as well as opt-in to Flex box. Dropping IE8 is a good move. Glyphicons need to go for accessibility. The overall CSS is smaller. I like that. The hackability though? Less so.
-
Bandwidth throttling / simulation in macOS (OS X)
Often as a developer, you want to simulate the experience of limited bandwidth for people with slower internet connections. Chrome and FireFox have this built into the browser, but it only affects the browser and doesn't provide robust parameters for latency or affect the rest of the experience. Safari doesn't have this, and it's in part to the Network Link Conditioner utility provided as an additional tool.
To install the Network Link Conditioner, you'll need the following:
- Apple Developer account (no paid licensing is required)
- Xcode installed
Next, go to downloads for Apple Developers and sign in. The Network Link Conditioner utility is packaged in with other utilities. Search for Additional Tools or use one of the links below.
- OS X 10.10 users should download Hardware IO Tools for Xcode 7.3
- OS X 10.10 users should download Additional Tools for Xcode 8.2
- OS X 10.12 users should download Additional Tools for Xcode 9

Open up the DMG and install Network Link Conditioner.prefPane by double-clicking it. (Note: in Additional Tools, it'll likely be in the hardware folder)
Using Network Link Conditioner

Open up the system prefs on your computer. Click on Network Link Conditioner and click on/off to toggle it on, and the drop down to use presets. You can create your own with the Manage Profiles.
Congrats, now you can enjoy slow internet.
-
Integrating Node KSS with Gulp
First I off, I highly recommend reading CSSTricks' Build a Style Guide Straight from Sass, it's a game changer for auto style guide generation. That said, I assume if you're at this page you're already a convert.
I'm going to assume the following:
- node-kss is installed in the same directory as your gulpfile
- node-kss has been set up and is generating a style guide.
- you have at least very rudimentary understanding of gulp
If either of the first is untrue, please go to the CSS tricks link as it's a wonderful guide and will get you a working spot >Node-KSS has a gulp repository but its wantonly out of date. I recommend not using it. Fortunately chaining it's pretty easy. First, we need to install gulp-shell in our gulp project.
npm install --save-dev gulp-shellNext, we're going to need to require gulp shell in our gulp file, this can vary based on your set up, it may be var or const depending on if you're running ES6 or not or part of a larger declaration:
ES6
const shell = require('gulp-shell')ES5
var shell = require('gulp-shell')Next we're going to create in our gulpfile a task to execute the command to run node-kss (note you can run alterations of said command if your configuration is different, kss is not required to be installed in the same place as gulp.)
gulp.task('kss', shell.task(['./node_modules/.bin/kss --config kss-config.json']));Lastly, we now need to reference this task in another task. Below is an example of how I'm using it, I created a watch task called "styleguide", a slightly modified version of my default task. Your task will differ from mine
gulp.task('styleguide',['serve'], function() { // Watch .scss files gulp.watch(appDefaults.styleDirectory+'**/*.scss', function(event) { console.log('File ' + event.path + ' was ' + event.type + ', running tasks...'); gulp.run('sass'); gulp.run('kss'); }); gulp.watch(appDefaults.myJavascriptDirectory , function(event) { console.log('File ' + event.path + ' was ' + event.type + ', running tasks...'); gulp.run('scripts'); gulp.run('compress'); }); gulp.watch(appDefaults.watchJavascript).on('change', browserSync.reload); gulp.watch(appDefaults.watchHTML).on('change', browserSync.reload); });Note that I applied
gulp.run('kss');after my Sass task has run, this will generate a style guide. Since the style guide generates new HTML on every save, mygulp.watch(appDefaults.watchHTML).on('change', browserSync.reload);is triggered because of my project's directory structure. This is why I created a separate task named "styleguide" as I do not always need my kss task to run, and do not want to interfere with live CSS injection via browserSync. Your needs will vary.
-
Gulp Boilerplate
Every now and again, I remember I have a GitHub account and throw something simple up there. I made a Grunt Boilerplate years ago and finally got around to making one for Gulp. There are a few features I still need to stick in, but I like to have a starting point rather than re-inventing my tasks every project.
Gulp-Sass-JS-BrowserSync-Boilerplate
Features all the greatest hits:
- Sass processing
- CSS Browser auto-prefixing
- CSS minification
- JS Uglify (minification)
- BrowserSync (Inject CSS changes + follow, reload on JS change)
This is mostly for my own benefit, but if anyone finds it useful, I'm glad. You can nab it here Gulp-Sass-JS-BrowserSync-Boilerplate
-
When Node-Sass fails Installing
So you're here because bash is outputting some big mess that looks like the following when you tried to install gulp-sass or node-sass via NPM. You've probably updated Node and NPM, switched versions in NVM or HomeBrew and are beating your head while node-sass isn't installing. The issue is likely not in the node or npm version but the package.json.
> node-sass@0.8.6 install /Users/<path-to-project>/_gulp/node_modules/gulp-sass/node_modules/node-sass > node build.js (node:43004) [DEP0006] DeprecationWarning: child_process: options.customFds option is deprecated. Use options.stdio instead. CXX(target) Release/obj.target/binding/binding.o In file included from ../binding.cpp:1: ../../nan/nan.h:339:13: error: no member named 'New' in 'v8::String' return _NAN_ERROR(v8::Exception::Error, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR' # define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg)) ~~~~~~~~~~~~^ ../../nan/nan.h:343:5: error: no member named 'ThrowException' in namespace 'v8' _NAN_THROW_ERROR(v8::Exception::Error, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR' v8::ThrowException(_NAN_ERROR(fun, errmsg)); \ ~~~~^ ../../nan/nan.h:343:5: error: no member named 'New' in 'v8::String' _NAN_THROW_ERROR(v8::Exception::Error, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR' v8::ThrowException(_NAN_ERROR(fun, errmsg)); \ ^~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR' # define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg)) ~~~~~~~~~~~~^ ../../nan/nan.h:348:9: error: no type named 'ThrowException' in namespace 'v8' v8::ThrowException(error); ~~~~^ ../../nan/nan.h:355:65: error: no member named 'New' in 'v8::String' v8::Local<v8::Value> err = v8::Exception::Error(v8::String::New(msg)); ~~~~~~~~~~~~^ ../../nan/nan.h:356:50: error: expected '(' for function-style cast or type construction v8::Local<v8::Object> obj = err.As<v8::Object>(); ~~~~~~~~~~^ ../../nan/nan.h:356:52: error: expected expression v8::Local<v8::Object> obj = err.As<v8::Object>(); ^ ../../nan/nan.h:357:65: error: too few arguments to function call, expected 2, have 1 obj->Set(v8::String::New("code"), v8::Int32::New(errorNumber)); ~~~~~~~~~~~~~~ ^ /Users/<user>/.node-gyp/8.1.2/include/node/v8.h:2764:3: note: 'New' declared here static Local<Integer> New(Isolate* isolate, int32_t value); ^ In file included from ../binding.cpp:1: ../../nan/nan.h:357:26: error: no member named 'New' in 'v8::String' obj->Set(v8::String::New("code"), v8::Int32::New(errorNumber)); ~~~~~~~~~~~~^ ../../nan/nan.h:369:12: error: no member named 'New' in 'v8::String' return _NAN_ERROR(v8::Exception::TypeError, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR' # define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg)) ~~~~~~~~~~~~^ ../../nan/nan.h:373:5: error: no member named 'ThrowException' in namespace 'v8' _NAN_THROW_ERROR(v8::Exception::TypeError, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR' v8::ThrowException(_NAN_ERROR(fun, errmsg)); \ ~~~~^ ../../nan/nan.h:373:5: error: no member named 'New' in 'v8::String' _NAN_THROW_ERROR(v8::Exception::TypeError, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR' v8::ThrowException(_NAN_ERROR(fun, errmsg)); \ ^~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR' # define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg)) ~~~~~~~~~~~~^ ../../nan/nan.h:377:12: error: no member named 'New' in 'v8::String' return _NAN_ERROR(v8::Exception::RangeError, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR' # define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg)) ~~~~~~~~~~~~^ ../../nan/nan.h:381:5: error: no member named 'ThrowException' in namespace 'v8' _NAN_THROW_ERROR(v8::Exception::RangeError, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:324:11: note: expanded from macro '_NAN_THROW_ERROR' v8::ThrowException(_NAN_ERROR(fun, errmsg)); \ ~~~~^ ../../nan/nan.h:381:5: error: no member named 'New' in 'v8::String' _NAN_THROW_ERROR(v8::Exception::RangeError, errmsg); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:324:26: note: expanded from macro '_NAN_THROW_ERROR' v8::ThrowException(_NAN_ERROR(fun, errmsg)); \ ^~~~~~~~~~~~~~~~~~~~~~~ ../../nan/nan.h:319:50: note: expanded from macro '_NAN_ERROR' # define _NAN_ERROR(fun, errmsg) fun(v8::String::New(errmsg)) ~~~~~~~~~~~~^ ../../nan/nan.h:406:13: error: no member named 'smalloc' in namespace 'node' , node::smalloc::FreeCallback callback ~~~~~~^ ../../nan/nan.h:141:71: note: expanded from macro 'NAN_INLINE' # define NAN_INLINE(declarator) inline __attribute__((always_inline)) declarator ^~~~~~~~~~ ../../nan/nan.h:416:12: error: no matching function for call to 'New' return node::Buffer::New(data, size); ^~~~~~~~~~~~~~~~~ /Users/<user>/.node-gyp/8.1.2/include/node/node_buffer.h:52:40: note: candidate function not viable: no known conversion from 'char *' to 'v8::Isolate *' for 1st argument NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, size_t length); ^ /Users/<user>/.node-gyp/8.1.2/include/node/node_buffer.h:55:40: note: candidate function not viable: no known conversion from 'char *' to 'v8::Isolate *' for 1st argument NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, ^ /Users/<user>/.node-gyp/8.1.2/include/node/node_buffer.h:67:40: note: candidate function not viable: requires 3 arguments, but 2 were provided NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, ^ /Users/<user>/.node-gyp/8.1.2/include/node/node_buffer.h:60:40: note: candidate function not viable: requires 5 arguments, but 2 were provided NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, ^ In file included from ../binding.cpp:1: ../../nan/nan.h:420:12: error: no matching function for call to 'New' return node::Buffer::New(size); ^~~~~~~~~~~~~~~~~ /Users/<user>/.node-gyp/8.1.2/include/node/node_buffer.h:52:40: note: candidate function not viable: requires 2 arguments, but 1 was provided NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, size_t length); ^ /Users/<user>/.node-gyp/8.1.2/include/node/node_buffer.h:55:40: note: candidate function not viable: requires at least 2 arguments, but 1 was provided NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, ^ /Users/<user>/.node-gyp/8.1.2/include/node/node_buffer.h:67:40: note: candidate function not viable: requires 3 arguments, but 1 was provided NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, ^ /Users/<user>/.node-gyp/8.1.2/include/node/node_buffer.h:60:40: note: candidate function not viable: requires 5 arguments, but 1 was provided NODE_EXTERN v8::MaybeLocal<v8::Object> New(v8::Isolate* isolate, ^ In file included from ../binding.cpp:1: ../../nan/nan.h:427:26: error: no member named 'Use' in namespace 'node::Buffer' return node::Buffer::Use(data, size); ~~~~~~~~~~~~~~^ fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 errors generated. make: *** [Release/obj.target/binding/binding.o] Error 1 gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/Users/<user>/.nvm/versions/node/v8.1.2/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23) gyp ERR! stack at emitTwo (events.js:125:13) gyp ERR! stack at ChildProcess.emit (events.js:213:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12) gyp ERR! System Darwin 16.7.0 gyp ERR! command "/Users/<user>/.nvm/versions/node/v8.1.2/bin/node" "/Users/<user>/.nvm/versions/node/v8.1.2/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /Users/<path-to-project>/assets/_gulp/node_modules/gulp-sass/node_modules/node-sass gyp ERR! node -v v8.1.2 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not okGo to package.json and look at the versions. Most likely the version is locked to a very old version of node-sass or gulp-sass in your project (or the project you're using), switch it's version to something recent, (as of writing this, it is
"gulp-sass": "^3.0.0", or"node-sass": "^4.7.2"). Congrats, it'll now install!