Skip to content

Instantly share code, notes, and snippets.

@stubailo
stubailo / answer.md
Last active July 12, 2016 06:46
Answer to Blaze question on Crater.io

Answer to Blaze question on crater.io

https://crater.io/comments/ucDz7fibgDcJqHtFu

Many of us want Blaze 2.0 and not Angular or React. Is MDG committed to continuing the development of Blaze? If so, how? Thanks!

TL;DR: I think the best thing to do is probably build Blaze 2.0 on top of the React rendering system to get a nice developer experience while taking advantage of new tech like React Native and the React component ecosystem.

Blaze is a very interesting part of the Meteor platform, from a platform point of view. Let's look at where we are now. Here are some of the benefits of Blaze:

@jawb
jawb / cssImage.php
Last active July 31, 2016 14:23
Image to CSS
<?php
/*
Demos:
https://jsbin.com/gakudi/1/edit?output
https://jsbin.com/xunifo/edit?output
Usage:
php cssImage.php scale image output
*/
@FredericJacobs
FredericJacobs / gist:b1b518125b7066880359
Last active November 7, 2021 09:54
Some notes about Reporta app since some people expressed worry about Reporta's security.

Analytics

Analytics track you, but they also keep local files really useful for forensics to gather evidence against you.

Google Analytics

Because of course, you need to know if people actually use it when it's developed by a PR firm. Google Analytics tracks a lot of your moves and stored locally in a cache then uploaded to Google servers. Every action is logged.

@paulirish
paulirish / what-forces-layout.md
Last active October 13, 2025 11:13
What forces layout/reflow. The comprehensive list.

What forces layout / reflow

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.

Element APIs

Getting box metrics
  • elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
@paulirish
paulirish / how-to-view-source-of-chrome-extension.md
Last active October 10, 2025 13:28
How to view-source of a Chrome extension

Option 1: Command-line download extension as zip and extract

extension_id=jifpbeccnghkjeaalbbjmodiffmgedin   # change this ID
curl -L -o "$extension_id.zip" "https://clients2.google.com/service/update2/crx?response=redirect&os=mac&arch=x86-64&nacl_arch=x86-64&prod=chromecrx&prodchannel=stable&prodversion=44.0.2403.130&x=id%3D$extension_id%26uc" 
unzip -d "$extension_id-source" "$extension_id.zip"

Thx to crxviewer for the magic download URL.

anonymous
anonymous / amazon.md
Created August 19, 2015 18:34

I would like to tell my story of burnout at Amazon, considering the fact that there is so many stories out there on both sides of the issue. My story is also on both sides of the issue, and I've had a lot of time to think about why people can see the same culture but come away with completely different conclusions. This is a throwaway because I still work there and I don't plan on changing that, and I don't exactly trust the company to take this in good faith, despite the fact that I mean this as a purely constructive criticism for a company that I really do like.

I am an autodidact (my formal education only tangentially describes what I can do), and a polymath (capable of holding my own amongst PhD-level Operations Researchers, Statisticians, Econometricians, Data Scientists, Computer Scientists, as well as Software Engineers). I love to solve real world problems, and in many ways am the perfect type of person for Amazon's culture. I started in a level 5 position, but felt from the beginning that I warrant

@mnot
mnot / snowden-ietf93.md
Last active November 5, 2024 06:22
Transcript of Edward Snowden's comments at IETF93.
@laughinghan
laughinghan / InterVer.md
Last active January 6, 2024 07:22
Interface Versioning - Never break backcompat, keep the API nimble

Interface Versioning (InterVer)

Never break backcompat, keep the API nimble

An extension of SemVer with a stricter (yet more realistic) backcompat guarantee, that provides more flexibility to change the API, for libraries that are packaged and downloaded (not services accessed remotely over the Internet (see Note 4)).

@atcuno
atcuno / gist:3425484ac5cce5298932
Last active October 9, 2025 17:52
HowTo: Privacy & Security Conscious Browsing

The purpose of this document is to make recommendations on how to browse in a privacy and security conscious manner. This information is compiled from a number of sources, which are referenced throughout the document, as well as my own experiences with the described technologies.

I welcome contributions and comments on the information contained. Please see the How to Contribute section for information on contributing your own knowledge.

Table of Contents