![]() If the app is slow because of ActiveRecord like database access, it'll be slow in every language.Įven if it isn't much faster because of a database bottleneck (inherit or accidental), I would think that it would still be worth it. Rust is way faster than Ruby, but for web apps the bottleneck can be in the database layer. (This would be a lot of work but at least you wouldn't be starting from scratch) Most of the challenge in getting this right is integrating pre-existing libraries, coming up with good conventions, developing a good cli that can help bootstrap projects and generate boilerplate, writing great documentation, and providing tutorials. An ORM in Rust will be a lot faster and memory efficient than an ORM in Ruby. ORMs are slower but I think it is still worth it. This could be solved by using an async database connection library like tokio-postgres and implementing traits on top of diesel that would use those connections rather than the connections from diesel itself. The main problem I could see is that Rocket is moving to async and Diesel has not found an async api that they like. ![]() ructe seems the most like irb.įor the models, you could use Diesel. By using convention and some macros, you could make something straightforward and easy to use.įor views there are many template engines available. You could possibly build a fairly good mvc framework my integrating a few existing parts.įor the controllers, you could build on top of Rocket or just take inspiration from it. But I could see it being possible in a year or two. I think it might be a bit early for something like this in Rust.
0 Comments
Leave a Reply. |