/** | |
Returns a bounding rect for _el_ with absolute coordinates corrected for | |
scroll positions. | |
The native `getBoundingClientRect()` returns coordinates for an element's | |
visual position relative to the top left of the viewport, so if the element | |
is part of a scrollable region that has been scrolled, its coordinates will | |
be different than if the region hadn't been scrolled. | |
This method corrects for scroll offsets all the way up the node tree, so the |
type below:
brew update
brew install redis
To have launchd start redis now and restart at login:
brew services start redis
Disclaimer: Please follow this guide being aware of the fact that I'm not an expert regarding the things outlined below, however I made my best attempt. A few people in IRC confirmed it worked for them and the results looked acceptable.
Attention: After following all the steps run gdk-pixbuf-query-loaders --update-cache
as root, this prevents various gdk-related bugs that have been reported in the last few hours. Symptoms are varied, and for Cinnamon the DE fails to start entirely while for XFCE the icon theme seemingly can't be changed anymore etc.
Check the gist's comments for any further tips and instructions, especially if you are running into problems!
Results after following the guide as of 11.01.2017 13:08:
$ curl --help | |
Usage: curl [options...] <url> | |
--abstract-unix-socket <path> Connect via abstract Unix domain socket | |
--alt-svc <file name> Enable alt-svc with this cache file | |
--anyauth Pick any authentication method | |
-a, --append Append to target file when uploading | |
--basic Use HTTP Basic Authentication | |
--cacert <file> CA certificate to verify peer against | |
--capath <dir> CA directory to verify peer against | |
-E, --cert <certificate[:password]> Client certificate file and password |
Andy Thomason is a Senior Programmer at Genomics PLC. He has been witing graphics systems, games and compilers since the '70s and specialises in code performance.
import React from "react"; | |
import { Formik, Form, Field, ErrorMessage } from "formik"; | |
import DatePicker from "react-datepicker"; | |
import "react-datepicker/dist/react-datepicker.css"; | |
const App = () => ( | |
<div> | |
<Formik | |
initialValues={{ email: "", date: "" }} |
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?
FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.
- By Edmond Lau
- Highly Recommended 👍
- http://www.theeffectiveengineer.com/