And, for anyone else considering RUST, you should read it as well.
The aspects listed in that blog, reveal a language that adds extra burden to the programmer. And, causes complexity, or rather, intractability to increase with project size.
In English, that means that RUST is designed to cause project failure.
@hazlin@shortstacksran.ch@Inginsub@clubcyberia.co I read through it. Very good read.In English, that means that RUST is designed to cause project failure.I don't think that's totally fair, but I'm not experienced enough to argue against it. He does explain that it can be quite good for certain projects. I think he's just right that the community has a cult mentality of overpromising and dismissing concerns when people encounter problems that they wouldn't in other languages.
I would love to hear @silverpill@mitra.social's take on this. (Warning the post is long so my TL:DR would be that gamedev needs things rust can't provide easily at the moment and possibly not even for the near future)
@gabriel@Inginsub@hazlin Rust is designed to build stable and efficient software. I don't know about gamedev (I've heard they prefer to build buggy crap that only works on the newest and most expensive hardware), but it works extremely well in my projects.
@gabriel I'd use rusqlite. Sqlite is reliable, stable and it's not going anywhere. ORMs are unnecessary (IMO) and you probably won't need async in desktop application
@silverpill@mitra.social Speaking of which, what (crate+db) would you recommend for a database for a (local) desktop application (I'm building an RSS reader).