abdullin

(ns azurelog.reader
  (:require [clj-time.core :as t]
            [clj-time.format :as f]
            [clojure.java.io :as io])
  (:import [com.microsoft.azure.storage CloudStorageAccount]
           [java.nio ByteOrder ByteBuffer]
           [com.microsoft.azure.storage.blob]
           [java.util.zip GZIPInputStream]
           [org.apache.commons.io.input BoundedInputStream]))

abdullin

// Bookmarklet for making Houzz useful
javascript:$("img.viewImage, img.currentImage, img.space, img[id^=galleryImg], img[class^=browseListImage], .gallery-photo img").each(function() { var newSrc = this.src.replace(/[fs]images\/(\d+).*/, 'simages/$1_0_9-.jpg').replace(/_\d-/,'_16-'); $(this).parents("div.browseListBody").before("<a href='"+newSrc+"'><img src='"+newSrc+"' width=400></a>") });$("div.content-row").remove();

abdullin

// snippet is for http://abdullin.com/journal/2011/6/26/event-sourcing-a-la-lokad.html

// simple helper, that looks up and calls the proper overload of
// When(SpecificEventType event). Reflection information is cached statically
// once per type. 
public static class RedirectToWhen
{
    static class Cache<T>
    {
        public static readonly IDictionary<Type, MethodInfo> Dict = typeof(T)

abdullin

// This is a hacky sample (that works for me) of alternative way to use Lokad-codeDSL
// or any similar way of generating message contracts on-the-fly. Original approach was 
// with using T4 template, that would rebuild cs files from DSL representation, whenever
// we hit Ctrl-S.

// This approach works almost exactly like this (Ctrl-S to rebuild), but does not require VS
// to run or does not require unloading VS to change the underlying generator code.

// in fact it is extremely boring. Lolcats from MightyMoose could be used to improve the situation, though.
// any takers? :)

abdullin

Flow: Actor-based Concurrency with C++

Engineering challenges

FoundationDB began with ambitious goals for both high performance per node and scalability. We knew that to achieve these goals we would face serious engineering challenges while developing the FoundationDB core. We'd need to implement efficient asynchronous communicating processes of the sort supported by Erlang or the Async library in .NET, but we'd also need the raw speed and I/O efficiency of C++. Finally, we'd need to perform extensive simulation to engineer for reliability and fault tolerance on large clusters.

To meet these challenges, we developed several new tools, the first of which is Flow, a new programming language that brings actor-based concurrency to C++11. To add this capability

abdullin

using System;
using System.Collections.Concurrent;
using System.Collections.Generic;
using System.Diagnostics;
using System.IO;
using System.IO.Compression;
using System.Linq;
using System.Threading;

namespace SearchBench {

abdullin

This is a response to Bill Fisher regarding experience with Flux:

@abdullin Also, can you clarify what you mean by "solution structure"? I am thinking about revising the examples soon.

Currently all flux samples (that I've seen) group files into folders based on technical similarity. For example, stores go with stores, action creators reside in the same folder shared with the other action creators.

This pattern works quite well for smaller projects. It feels especially good for the sample projects of various MVC frameworks, when you have just a bunch of controllers, models and views.

However, as we discovered on some production projects, such approach doesn't scale well. At some point you end up with dozens of technically similar files per folder and logically messy solution.

abdullin

	public sealed class RedirectToDynamicEvent
	{
		public readonly IDictionary<Type, List<Wire>> Dict = new Dictionary<Type, List<Wire>>();

		public sealed class Wire
		{
			readonly MethodInfo _method;
			public Type ParameterType;
			readonly object _subject;
			readonly bool _includeVersion;

abdullin

    public sealed class Tracer {

        int _traceId;

        readonly Func<long> _clock;
        StreamWriter _writer;

        public Tracer(Func<long> clock) {
            _clock = clock;
            

abdullin

Structuring Neat .NET Core Console Apps Neatly

So you’ve created a really neat console app, but it’s growing and you need a way to keep it all neatly organized and preferrably with some Good Practices.

The guys at Entity Framework have thought about this and structured their console app really neatly. Today, we’ll take the ninja app we built previously and make it all look pretty and stuff.

I know what I’m doing, just gimme the damn framework!