>it's too OOP-y for me, I can't really see what it's doing Eh, Rust doesn't have OOP. What do you mean? I get that Rust is a bit hard to read if you aren't use

>it's too OOP-y for me, I can't really see what it's doing Eh, Rust doesn't have OOP. What do you mean? I get that Rust is a bit hard to read if you aren't used to it but apart from that it's fine for me. Don't forget that Rusts verbose-ness also stems from dealing with the borrow-checker which in turn gives you memory safety. Almost every C-project has memory bugs somewhere. The thing with cargo: In general cargo is really painless, the first build does take long but after that build times are ok for most projects. You only run into problems with projects like servo which are huge. build.sh scripts have to be managed by the author while cargo run magically works in basically any Rust project. >Am I too stubborn? Or should a terminal emulator really be not such a massive project? (No offense meant). Depends, this is not only an emulator but also a multiplexer. A simple terminal emulator that supports basic commands is a small program, I mean look suckless st. But if you get into suporting ligatures, UTF8 etc. you will get a lot more complexity that in turn adds code and dependencies. I imagine properly supporting UTF8 and Ligatures in C would be a huge pain.