Aaron Jensen - All Comments

re: Introducing Machine.Specifications (or MSpec for short)

aaronjensen — Tue, 13 May 2008 14:27:01 GMT

James,

I hear you. It's definitely a stretch of C#. The benefits of using C# are clear though. The tool and the framework support make it worth it in my opinion. Like I said in the post though, this is an experiment. I've got no ego behind this and I'm not pushing for widespread adoption. I'm just kind of dropping it on the community and seeing if it sticks at all :)

re: Mock Framework Benchmarks

james.kovacs — Sat, 10 May 2008 18:09:27 GMT

I was equally confused when looking at a performance trace of Moq vs. Rhino. (I don't have TypeMock installed.) The majority of the time in both Moq and Rhino was spent creating proxies and both frameworks are using DynamicProxy2 for proxy creation. Something was definitely up. Excellent work tracking down the problem!

Weekly Web Nuggets #11

Code Monkey Labs — Fri, 09 May 2008 14:57:56 GMT

Understanding Model-View-Controller : Introducing developers to the MVC concept can, at times, be a challenging endeavor. Jeff Atwood has put together a very informative post that may be able to help! Mocking Frameworks Benchmarked : In search of a faster

Weekly Web Nuggets #11

Code Monkey Labs — Fri, 09 May 2008 14:57:54 GMT

re: Introducing Machine.Specifications (or MSpec for short)

jamesthigpen — Fri, 09 May 2008 14:38:52 GMT

This is very awesome. However...

While I understand your choice for doing it in C#, I feel that by not using a language that would allow for a more fluent DSL syntax, you have created something that will hamper it's adoption.

The way you are using C# goes against the grain of how users are taught to use C#. static fields and what look like fancy function but end in semicolons. If I brought this to my team it'd be very confusing for them because it *is* C# but it's not the C# they're use to.

That could be just dumped into the "learning curve" bucket, but I see it being a recurring problem with the context switching required between MSpec and C# when bouncing between tests and code.

It could be argued that the context switching between MPsech C# and "regular" C# when bouncing back and forth between tests and code is no more grating than if it were a completely separate DSL, but I feel that all the syntactic sugar required to make this work prevents me from forgetting that it is C#. There is a certain amount of muscle memory in "private Account fromAccount;"

Dew Drop - May 9, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - May 9, 2008 | Alvin Ashcraft's Morning Dew — Fri, 09 May 2008 12:47:57 GMT

Pingback from Dew Drop - May 9, 2008 | Alvin Ashcraft's Morning Dew

re: Rhino.Mocks Performance Issue Fixed

Ray — Fri, 09 May 2008 07:24:03 GMT

Cheers mate! Well done

Reflective Perspective - Chris Alcock » The Morning Brew #90

Reflective Perspective - Chris Alcock » The Morning Brew #90 — Fri, 09 May 2008 07:04:17 GMT

Pingback from Reflective Perspective - Chris Alcock » The Morning Brew #90

re: Rhino.Mocks Performance Issue Fixed

Casey — Fri, 09 May 2008 06:49:07 GMT

And I was waiting till this morning to comment that your post would be like a red rag to a bull, and I fully expected Oren to drop all other work until Rhino was ten times faster than the others :)

Apart from that flipant comment, nice work!!!

Rhino.Mocks Performance Issue Fixed

Community Blogs — Fri, 09 May 2008 06:29:45 GMT

Just wanted to quickly note that I tracked down the performance issue in Rhino.Mocks and patched it

Rhino.Mocks Performance Issue Fixed

Aaron Jensen — Fri, 09 May 2008 05:56:16 GMT

Just wanted to quickly note that I tracked down the performance issue in Rhino.Mocks and patched it

re: Mock Framework Benchmarks

aaronjensen — Fri, 09 May 2008 04:25:37 GMT

I don't really consider NMock2 a framework worth considering, as it lacks a strongly typed, refactor friendly syntax, so no, I didn't. Feel free to add a Strategy though and give it a shot.

re: Mock Framework Benchmarks

Lex Y. Li — Fri, 09 May 2008 02:24:37 GMT

What about NMock 2? Did you test on that?

re: Introducing Machine.Specifications (or MSpec for short)

Rodrigo B. de Oliveira — Fri, 09 May 2008 00:46:57 GMT

That's pretty cool.

re: Mock Framework Benchmarks

Colin Jack — Thu, 08 May 2008 17:26:24 GMT

Does this contribute to the 2 articles you have to write about liking TypeMock for the free license? :)