All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
Updated: Just use qutebrowser (and disable javascript). The web is done for.
| func takeScreenshot(view: UIView) -> UIImageView { | |
| UIGraphicsBeginImageContext(view.frame.size) | |
| view.layer.renderInContext(UIGraphicsGetCurrentContext()) | |
| let image = UIGraphicsGetImageFromCurrentImageContext() | |
| UIGraphicsEndImageContext() | |
| UIImageWriteToSavedPhotosAlbum(image, nil, nil, nil) | |
| return UIImageView(image: image) | |
| } |
Even if you know the basics, making the right choices matters a lot. A minor mistake can destroy the security of your system.
repo: https://github.com/reaperhulk/pycon2015-crypto-tutorial
gist: https://gist.github.com/dmend/9a7269d5c521e72cc221
vm: https://4a95d8c077a100de3278-188294849580e8742c8bb57afd78c06c.ssl.cf2.rackcdn.com/pycon-2015-ubuntu.ova
Rich Hickey • 3 years ago
Sorry, I have to disagree with the entire premise here.
A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.
Mastery comes from a combination of at least several of the following:
| defmodule App.Router do | |
| use Phoenix.Router | |
| resources "users", Controller.Users | |
| options "/users", Controller.Users, :options | |
| end |
| package java8tests ; | |
| import java.util.function.BiFunction ; | |
| import java.util.function.Function ; | |
| public class Currying { | |
| public void currying() { | |
| // Create a function that adds 2 integers | |
| BiFunction<Integer,Integer,Integer> adder = ( a, b ) -> a + b ; |
RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.
On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.
So, many developers have started going straight t
| (ns wikiparse.core | |
| (:require [clojure.java.io :as io] | |
| [clojure.data.xml :as xml] | |
| [clojure.zip :refer [xml-zip]] | |
| [clojure.data.zip.xml :refer [xml-> xml1-> text]]) | |
| (:import [ org.apache.commons.compress.compressors.bzip2 BZip2CompressorInputStream]) | |
| (:gen-class :main true)) | |
| (defn bz2-reader | |
| "Returns a streaming Reader for the given compressed BZip2 |
