J Andrew Scott – http://rubberchickenfarm.com/ History of APIs RSS Advantages Fast & reliable Easy to consume Almost no technical footprint Disadvantages Read-only Static content No authentication No user-driven content (i.e. comments, favorites, etc) DIY API Advantages Dynamic content User-driven content App & user authentication Roles & permissions based Connected applications Disadvantages DIY OAuth Redundant URI scheme Mediocre performance Large technical footprint WP-API Advantages Succinct URI scheme Improved performance Small technical footprint Available in WordPress core Disadvantages Granular transactions No batch uploads Increased number of API calls What once required 2 web servers now required 12-15 servers WP-API Disadvantage Factors & Solutions Number of content types Solution: consolidate endpoints Volume of individual API calls Solution: batch processing endpoints Frequency of individual API calls Solution: page-level caching Lessons…
Something mentioned in the comments of the article is the danger in reconfiguring the defaults in the case that you are in another development environment. I can see that standpoint, and in that vain I’ve always gravitated to sticking with the command line for SCM rather than using some IDEs GUI integration of of the SCM tool. One nice feature of git is to use aliases and give yourself a shorthand, which of course when you find yourself using a development environment outside of your normal setup you’ll quickly recall the need to use the long hand to get what you are after.
git config --global alias.hop 'pull --single-branch --rebase=preserve'