/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
# Create a directory named "Sublime Text 3 Sync" under iCloud Drive | |
mkdir ~/Library/Mobile\ Documents/com~apple~CloudDocs/SubLime\ Text\ 3\ Sync | |
# Enter Sublime Text 3's directory | |
cd ~/Library/Application\ Support/Sublime\ Text\ 3/ | |
# Move "Installed Packages" directory to iCloud Drive and make a link | |
mv Installed\ Packages/ ~/Library/Mobile\ Documents/com~apple~CloudDocs/SubLime\ Text\ 3\ Sync/ | |
ln -s ~/Library/Mobile\ Documents/com~apple~CloudDocs/SubLime\ Text\ 3\ Sync/Installed\ Packages |
# The packages we'll be using | |
packages <- c("rvest","dplyr","tidyr","pipeR","ggplot2","stringr","data.table") | |
# From those packages, which ones are not yet installed? | |
newPackages <- packages[!(packages %in% as.character(installed.packages()[,"Package"]))] | |
# If any weren't already installed, install them now | |
if(length(newPackages)) install.packages(newPackages) | |
# Now make sure all necessary packages are loaded |
Looking for support tables for HTML/CSS/JavaScript features or details on their implementation status in major browsers?
- Chrome Platform Status (covers Chromium and thus includes Opera)
- Firefox Platform Status
- Microsoft Edge Platform Status
- WebKit Feature Status
- API Catalog
And then there’s Can I use…?.
<?php | |
# Licensed under a CC0 1.0 Universal (CC0 1.0) Public Domain Dedication | |
# http://creativecommons.org/publicdomain/zero/1.0/ | |
$mysite = 'https://adactio.com/'; // Change this to your website. | |
$token_endpoint = 'https://tokens.indieauth.com/token'; | |
$_HEADERS = array(); | |
foreach(getallheaders() as $name => $value) { |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
<script type="text/javascript"> | |
(function () { | |
"use strict"; | |
// once cached, the css file is stored on the client forever unless | |
// the URL below is changed. Any change will invalidate the cache | |
var css_href = './index_files/web-fonts.css'; | |
// a simple event handler wrapper | |
function on(el, ev, callback) { | |
if (el.addEventListener) { | |
el.addEventListener(ev, callback, false); |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
-
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the
secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection. -
Use production SSL certificates locally. This is annoying
/** | |
* Open external links in new tab/window | |
*/ | |
// All http:// links should open in new tab/window. Internal links are relative. | |
var anchors = document.querySelectorAll('a'); | |
for (var i = 0; i < anchors.length; i++) { | |
if (anchors[i].host !== window.location.hostname) { | |
anchors[i].setAttribute('target', '_blank'); |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.