Karmencita versus Linq. Some clarifications.

After I have released Karmencita I received questions about it’s “relationship” with Linq so i thought to write a post about this.

“Am i trying to copy Linq ? “

Heck no. Like i have also mentioned in FAQ the both Karmencita and Linq are OQL implementation. Despite what most people think there is nothing ground breaking in either Linq or Karmencita. It has been done before.

“Linq is static typed but Karmencita isn’t !“

   I would mention that , personally, i think the best thing about Linq is the VS.NET intelissense.  As a guy who dabbs with dynamic languages i prefer Karmencita’s terse and fast to write syntax over’s Linq’s syntax. But it’s just a matter of taste. If you want “static typing” just to avoid stupid typing mistakes then i suggest to take a look at unit testing. By writing unit tests you can catch both typing and logical errors. Also as a side note…..is pretty much impossible now to make a internal DSL static typed since i can’t write compiler plugins for C#/VB.NET  to do the type checking myself. I was taking a few days ago with C# member team from Microsoft and unfortunately they don’t have plans to allows us that.

“Karmencita’s advantages over Linq ?“

Since it’s implemented as a library you can use Karmencita with any .NET language . I’m dabbing with a slighty modified version of it from Boo.

“Plans ?”

Lots of plans…only time is missing . I would like to “bake” a JavaScriptuesque “eval” in there. Also joins . Multithread interpretor  (with option for CPU bounding on multicore machines) to speed up filtering huge data sources.

If you have other questions contact me.

Now playing: Dream Theater - Endless Sacrifice