On Mar 15, 2012, at 7:11 PM, Alex Hitchins wrote:
> Is there anything I could do to assist. My time is very limited however
> perhaps if there are a few things I could incorporate these in my dealings.
If time is limited, I'd suggest that you not help. The project is effectively
leaderless & dead (unless/until someone with lots of free time comes in).
I outlined some suggestions for where I think it could go:
http://groups.google.com/group/dblinq/browse_thread/thread/fcf68d14912da4e7/6abdfadebab99b8f?lnk=gst&q=development+status#6abdfadebab99b8f
http://groups.google.com/group/dblinq/browse_frm/thread/8260047816a6a148
At this point, though, I really wonder about the utility of DbLinq. There are
competing (maintained!) projects such as dapper, which is high performance and
used by stackoverflow.com:
http://code.google.com/p/dapper-dot-net/
There's still re-linq and their re-store ORM:
https://www.re-motion.org/web/
There's SQLite-net ORM:
https://github.com/praeclarum/sqlite-net
I'm still working on Mono for Android, so I'm largely focused on mobile these
days. Android provides SQLite, but anything else is largely crazy (unless it
was designed as an embedded DB), and I think mobile-focused development is
largely the future. (Not that I'm alone in this...)
So I personally see less need for a cross-DB/cross-platform ORM today.
- Jon
--
You received this message because you are subscribed to the Google Groups
"DbLinq" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/dblinq?hl=en.
