ashumeow

// How fast can you get all the intervals that overlap with another interval?
// WTF.. who cares.  Well if you are given the task to find all the stories 
// from a facebook timeline visible to the user, 
// how would you do that without blocking the user's scrolling?
// Imagine, you mark the stories as read and notify the server that the user saw those stories.
 
// It turns out you can achieve this task in log time using a segment tree.
// More about segment trees: 
// http://community.topcoder.com/tc?module=Static&d1=tutorials&d2=lowestCommonAncestor#Segment_Trees
// Sample:

ashumeow

class sample {
public override bool Equals(object Hello_Object)
    {
    if (Hello_Object == null) {
       return true;
   	} else {
   		return false;
   	}
    } }

ashumeow

Navigation and Resource Timing provides timing data for the fetch, but currently there is no interoperable way for the server to communicate own timing information to the client. For example:

• What steps were taken to generate the resource, and how long each took. Many sites already embed this type of information via HTML comments - e.g. wordpress emits <!--Page generated in X.X seconds.--> , and many sites provide more detailed stats (cache, db, generation) to enable performance debugging.
• If proxied, where was the time spent - e.g. time to fetch from origin, time to process response, etc.

Instead of relying on arbitrary HTML comments, we can define an HTTP header that can be used to send key-value pairs in a well defined format. Making this data available via a well defined interface would...

• Allow UA and other developer tools to automatically annotate appropriate timelines.
• Allow analytics vendors to gather this data for operational analysis.
• Allows proxies and CDNs to append custom timing d

ashumeow

        [Fact]
        public void RemoveBom()
        {
            foreach (var file in new DirectoryInfo("..\\..").EnumerateFiles("*", SearchOption.AllDirectories))
            {
                try
                {
                    var allBytes = File.ReadAllBytes(file.FullName);
                    var allText = File.ReadAllText(file.FullName);
                    if (allBytes.Length - allText.Length == 3 &&

ashumeow

// This event emitter emits events, but reserves the right to publish events to
// for its creator. It uses a WeakMap for true encapsulation.

const eesToEventMaps = new WeakMap();

export default class EventEmitter {
    constructor(publisher) {
        const eventMap = Object.create(null);
        eesToEventMaps.set(this, eventMap);

ashumeow

// unminifed version of https://apis.google.com/js/plusone.js
// see https://developers.google.com/+/plugins/+1button/#getting-started

window.___jsl = window.___jsl || {};
window.___jsl.h = window.___jsl.h || 'm;\/_\/apps-static\/_\/js\/gapi\/__features__\/rt=j\/ver=zVTxVnVbJog.en_US.\/sv=1\/am=!FRwcaGMpC1CIJ0aI4g\/d=1\/';
window.___jsl.l = [];
window.___gpq = [];
window.gapi = window.gapi || {};
window.gapi.plusone = window.gapi.plusone || (function () {
  function f(n) {

ashumeow

In architectural terms, the way we craft large-scale applications in JavaScript has (in my opinion) changed in one fundamental way in the last three years. Once you remove the minutia of machinery bringing forth data-binding, immutable data-structures and virtual-DOM the one key concept that many devs seem to have organically converged on is composition. Composition is incredibly powerful, allowing us to stitch together reusable pieces of functionality to "compose" a larger application. Composition eschews in a mindset of things being good when they're modular, smaller and easier to test. Easier to reason with. Easier to distribute. Heck, just look at how well that works for Node via npm. Composition is one of the reasons we regularly talk about React "Components", "Ember.Component", Angular directives, Polymer elements and of course, straight-up Web Components. We may argue about the frameworks and libraries surrounding these different flavours of component, but not that co

ashumeow

//Code to create a list of touches called pointerList
 
var pointerList = []; //Array of all the pointers on the screen
window.addEventListener("pointerdown", updatePointer, true);
window.addEventListener("pointermove", updatePointer, true);
window.addEventListener("pointerup", remPointer, true);
window.addEventListener("pointercancel", remPointer, true);
 
function updatePointer(e) { 
  if(e.pointerType === "touch") {

ashumeow

let tee = (a) => {console.log(String(a)); return a}

// our applicator
let $_ = (n) => {
  let args = new Array(n);
  for (let i = 1; i <= n; i++) {
    args[i-1] = `$${i}`
  }
  return (raw, ...values) =>
    Function(...args.concat(tee('return ' + raw.reduce(

ashumeow

SELECT respSize, respCookieLen, respHeadersSize, respHttpVersion, resp_vary, _cdn_provider, resp_cache_control, resp_content_encoding, _gzip_save, resp_transfer_encoding, resp_age, resp_connection, resp_accept_ranges, resp_server, urlShort 
FROM [httparchive:runs.latest_requests] 
LIMIT 10