When less is less: google code dead

When Steve Jobs given some suggestions to Google, I fear he was still upset for the Android-carbon-copy of the iPhone. Because Jobs suggested Google to focus on a small subset of product (no more then five) and Google did it. And google started killing a lot of lab projects.

Google Code Search was one of this projects.

Today I hit this nice article on how google code search was implemented, and I find it very nice. So I’d like to point it out, because it is a worth read with also an implementation attached to it.

I like to know if there is a Redis+{Ruby|Python|Java} code which is able to store a inverted tri-gram index on redis, because it would be a nice shot.

Someone out of there can help?

Is JavaScript a better evil then Dart? I am your father Luke….

And so you like JavaScript Html5 Web app, which can run on Safari iPhone, Nokia Windows Phone, Android web browser, Black Berry and so on? Are you on the mantra of multi platform mobile programming, aren’t you? Well,  Google mega corporation will soon awake you in a new nightmare: a new programming language!

Continue reading “Is JavaScript a better evil then Dart? I am your father Luke….”

dapper-dot-net – Simple SQL object mapper for SQL Server – Google Project Hosting

 

 Dapper is a single file you can drop in to your project that will extend your IDbConnection interface.
[…]

A key feature of Dapper is performance. The following metrics show how long it takes to execute 500 SELECT statements against a DB and map the data returned to objects.

The performance tests are broken in to 3 lists:

  1. POCO serialization for frameworks that support pulling static typed objects from the DB. Using raw SQL.
  2. Dynamic serialization for frameworks that support returning dynamic lists of objects.
  3. Typical framework usage. Often typical framework usage differs from the optimal usage performance wise. Often it will not involve writing SQL.

via dapper-dot-net – Simple SQL object mapper for SQL Server – Google Project Hosting.

linqbridge – Re-implementation of LINQ to Objects for .NET Framework 2.0 – Google Project Hosting

LINQBridge is a re-implementation of all the standard query operators in Framework 3.5’s System.Linq.Enumerable class. It’s designed to work with the C# 3.0 compiler, as used by Visual Studio 2008. LINQBridge comprises a LINQ to Objects API for running local queries. (It doesn’t include an implementation of LINQ to SQL, nor LINQ to XML; a good compromise can be to force Framework 3.5 out to just the server machines, allowing LINQ to SQL to be used where it’s needed most).

via linqbridge – Re-implementation of LINQ to Objects for .NET Framework 2.0

There are a lot of legacy project out of there. Some customer will ask you to add a simple .NET 2.0 web service to a big application, and they will not switch to C# 3.5 for that.

So it is nice to know LINQ could be backported, also because the LINQBridge code can teach us a lot of things!

For Java Guys:
LambdaJ is a very good alternative to LINQ, and it rocks too!