HNHacker News
TopNewBestAskShowJobs

otis_inf

183 karma · joined December 19, 2014

Creator / Lead developer of LLBLGen Pro (Entity modeling system / ORM for .NET) http://www.llblgen.com || Ex-demoscene || Twitter: @FransBouma || Blog: http://weblogs.asp.net/fbouma
submissionscomments
otis_inf··on Adblock Plus is probably the reason Firefox and Chrome are such memory hogs
I have an atom dual core small PC connected to my TV (it runs windows 7, yeah I know) and it's 'ok-ish' with performance, but starting a browser is a tad slow (chrome) and adblock makes it even slower as it's a plugin which is particularly slow to start. So I don't think blocking ads for performance reasons on slow machines is still cutting it if you take into account the performance penalty of abp.

All things considered however, it's IMHO a small price to pay for having the freedom to decide which content is fetched during page rendering and thus which services won't know whether you're visiting a certain webpage.

otis_inf··on Cello – Higher Level Programming in C
I agree with your argument that C has some bad parts which are desperately in need to be made better, but IMHO it should just stop there. Question of course then is: where is the line where it ends being updating bad parts of C and beginning to become a layer on top of C :) History has taught us that's sadly in the eye of the beholder .
otis_inf··on Cello – Higher Level Programming in C
Let C be C. For the people who don't like C for one reason or another, there are a ton of alternatives available, from x64/x86 targeting languages to manages stacks. Adding these libraries to C might look nice, but if you want to experience the things it brings to the table use a language where it's been borrowed from.
otis_inf··on PostgreSQL 9.4 Released
> Microsoft writing a LINQ provider for PgSql is a great thing for running .NET code on non-Windows platforms.

I've heard nothing of this kind with respect to npgsql, which is the current .NET provider for PostgreSql. Microsoft has never spent a minute on EF support in Npgsql, so that they bother now is a first. The thing is that to support EF in npgsql (or any other ADO.NET provider), the ADO.NET provider has to contain a command interpreter which interprets the command trees coming from EF's linq provider, and which are then to be used to create SQL statements. This isn't simple at all, and as the command trees change with EF7, it will be a struggle for MS to get a lot of ADO.NET providers support EF7 at the start.

Microsoft's only great linq provider is the one in Linq to Sql: it is able to handle a tremendous amount of edge cases. The thing with linq providers is that a general linq provider gets you only that far: a tremendous amount of cases are 'special cases' which have to get their own path to get from the expression-tree to specific sql. e.g.: ctx.A.Select(a=>a.B.Cs);. This gives a set of sets of C instances. To do this, you have to know at the materialization side which C rows belong to which set (as you have to group them by B, which isn't in the projection). Linq to Sql has a specific piece of code for this, it produces a specifically grafted SQL query which contains an extra column so the materializer can know which C rows to group together. EF doesn't, it obtains a big joined soup.

Irony is that EF7's linq provider will be built on Relinq, which is also the base of NHibernate's linq provider, and they didn't re-use the Linq to sql linq provider, which is kind of odd, considering linq to sql's is pretty db agnostic.

Writing a linq provider isn't simple btw. It took me a full year full time to write the one for LLBLGen Pro.

otis_inf··on PostgreSQL 9.4 Released
Thanks, dodyg :)
← PreviousPage 4 of 4