More relevant ads please.

I just read that Mozilla are going to block third party cookies in the next version of Firefox (optional, but blocking is on per default). That’s great. Let’s get rid of the web site/usage tracking that all advertising services has.

Continue Reading


Azure shut me down again

Yet again I got shut down by Azure. This time the CPU quote was exceeded just a couple of hours into the new quota period.

I’ve switched to “Reserved” mode which doesn’t have the same limits (which is not said anywhere in the management interface).



Azure failed me

(this entry was previously published as a PDF on twitter since I couldn’t access my blog)
I really liked my first experience with Azure. I’m also going to certify myself (I still am). But that’s before things stopped working and I got some not very good support. This blog entry is awas a PDF because I currently can’tcan use my blog. This entry is all about why.

Continue Reading


Downdown again

Sorry for being down again. My website mysteriously at all of my CPU quota at Azure = being suspended without notification.

More about that later (or check my PDF blog post in my twitter account)


Moved to Azure

I’ve moved this blog to Azure.

Everything went really smooth. I must say that I’m impressed with the work that Microsoft has done. Well. Almost everything. I got two complaints.

Continue Reading



Up and running again

I had a server crash and no access to the server room. But everything should be up and running again.



Request for comments: Merging libraries

I currently have a number of libraries which I develop (at github). Most of them are small (less than 50kb) and I’m thinking about merging them into one library instead.

What I mean is that I will add them into a single github project.

Why?

To me, choice is important. You can always choose to use your own favorite container instead of mine for any of the libraries. However, I also do like to make things easy. For instance, if I want to create a dead easy setup for Griffin.Decoupled I have to create several small nuget packages and make sure that different versions of all libraries work together.

I’m developing more and more features which are cross cutting between libraries, and it is increasingly difficult to manage the differences.

How?

I would join all projects which has no other dependencies than .NET into a single assembly (and therefore only namespaced project). The assembly would probably be about 200kb. All projects that got external dependencies would be named after their dependency. For instance “Griffin.Framework.RavenDb”

You will still of course be able to combine different libraries with other external libraries (as all interfaces will still be there).

Request for comments

What do you think? Do you mind to get a 200kb assembly instead of a 44kb assembly if you for instance only want to use Griffin.Networking or Griffin.Container?


Pages:1234567...14