Go for it? The people who think this is the solution are the ones who will need to take up the work. It's not like the people who don't think this is the solu

Go for it? The people who think this is the solution are the ones who will need to take up the work. It's not like the people who don't think this is the solution will do it. Get ready to work hard for 5, 10, 20 years... rewriting sqlite will be a monumental effort and take the laser focus of a strong development team for years, if not decades. It's fraught with risk. Think about it... how many years would it be before a stable version of sqlite based on rust was available with comparable performance and fewer bugs than the c-based version? (Seems likely to me that it would never happen.) I think you'd be better off creating a sqlite competitor, that could start off much smaller with a much smaller feature and much less stringent performance requirements that, nevertheless, has enough for many common cases. Of course, you'd still have to convince people to use it over sqlite. If your main selling point is "significantly fewer bugs than sqlite" I don't think it's going to be very easy to make that true, rust or not.