Now I DuckDuckGo

Stop using Google and start using DuckDuckGo.

I remember looking at DuckDuckGo a few years ago and thinking it didn’t look polished.

Screen Shot 2016-09-01 at 11.54.55 p.m.

Now it does – they live up to the claim of smarter search with less clutter.

Screen Shot 2016-09-02 at 12.04.37 a.m..png

And, of course, real security. Switching to DuckDuckGo for routine searches is one small change that should greatly clean up your web footprint. There’s a lot more you can do to be secure on the internet, and DuckDuckGo has very much advice on that topic. But just changing the default search engine in your browser from Google to DuckDuckGo is a big step in the right direction.

Screen Shot 2016-09-01 at 11.08.10 p.m.

Turning off all those other options also helps reduce clutter.

App List (August 2016)

Just a list of third party Mac and iPhone apps I use. Sorry, no links or comments. Also, alphabetical.

I have always kept a list of the third party apps I use. It has come in handy when setting up a new computer or phone. I just added the list to my public GitHub notes. Might as well share it. It’s just a list. No links. No comments. Alphabetical order. Subject to change.

Mac

  • 1Password
  • Amphetamine
  • Atom
  • BitTorrent Sync
  • Day One
  • Docker (beta)
  • Dropbox
  • ExpressVPN
  • feedly
  • GitHub Desktop
  • Google Chrome
  • iA Writer
  • Keybase
  • Kitematic
  • Magnet
  • Microsoft Office
  • Pixelmator
  • Pocket
  • Skype
  • TextExpander
  • Twitter
  • Ulysses
  • VLC
  • WordPress.com

iPhone

  • 1Password
  • Alipay
  • Amount Plus
  • Authenticator (Google)
  • Authenticator (Microsoft)
  • 百度地图 (Baidu Maps)
  • Boomerang (Instagram)
  • Chrome
  • Converter (converts Chinese characters to Pinyin)
  • Day One
  • 滴滴出行 (Chinese ride sharing app)
  • Drive (Google)
  • Dropbox
  • Duolingo
  • ExpressVPN
  • Facebook
  • feedly
  • Fender Tuner
  • GIPHY
  • GIPHY CAM
  • Gmail
  • Google
  • Google Maps
  • Google+
  • Hyperlapse (Instagram)
  • iA Writer
  • Imgur
  • iMovie
  • Instagram
  • Just Press…
  • Kindle
  • Layout (Instagram)
  • LinkedIn
  • Medium
  • Messenger
  • PayPal
  • Pixelmator
  • Pocket
  • Prisma
  • QQ Music
  • Reddit
  • Shazam
  • 手机百度 (Baidu)
  • Signal
  • Skype
  • Snapchat
  • Snapseed
  • Sync (BitTorrent)
  • TED
  • TextExpander
  • Translate (Google)
  • Twitter
  • Tydiig
  • Ulysses
  • VLC
  • WeChat
  • WordPress
  • YouTube

Compiling a WordPress Development Environment in OS X

Compiling a WordPress development environment in OS X is something that some people still like to do.

If you want to compile your development environment from scratch, instead of using packages included with OS X, and without resorting to third party package managers like Homebrew, then check out my guide on GitHub (lukejanicke / wp-mac-dev-env).

The guide contains complete instructions for compiling a WordPress development environment in OS X from scratch. All essential packages and their dependencies are compiled from the latest source code and configured manually, including packages already bundled with OS X. This gives you full control over a cutting edge environment at the expense of some convenience.

The development stack is a typical MAMP environment—Macintosh/OS X, Apache, MySQL, and PHP—which, along with WP-CLI, support WordPress.

It’s based on Patrick Bougie’s excellent Compiling a Web Development Environment on Mac OS X. For a more comprehensive web development environment, and instructions for previous versions of OS X, please refer to Patrick’s guide.

My guide only includes the packages and dependencies necessary for a basic WordPress development environment (i.e. themes and plugins). It also adds some necessary steps for newer package versions, and includes instructions for configuring Apache virtual hosts, WordPress and WP-CLI.

The environment described is not suitable for production. To create a local environment that more closely resembles a production environment in terms of security and features, take a look at Vagrant, Docker and Roots.

Compiling Python 3 in OS X

Don’t use the Xcode-beta version of Command Line Tools if you are trying to compile Python 3 in OS X.

You really shouldn’t be compiling Python 3 from source on a Mac. El Capitan comes with Python 2.7.10 and you can easily install the latest Python 3 with the official OS X installer package or via Homebrew. But if you are (at approximately the time of writing this), use the Command Line Tools that come with Xcode proper and not the beta version.

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

There’s a few more details in my post on Stack Overflow.

If you try to make and make install Python 3 (3.5.2 at this time) with the Xcode-beta version of Command Line Tools, you’ll get an error and the build will fail. You’ll get the same error if you try to use pyenv.

If you switch back to the regular “toolchain”, you’ll still get a lot of warnings and notices about uninstallable components when you make and make install Python, but it will compile successfully.