Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why would support for Rust be a problem here?


Two language development stack, with the complexity it entails, when the product is mac only.


They mentioned elsewhere it started off as a fork of the Xi editor which is written in Rust. Xi separates the text-editor idea into backend and frontend, and Xi itself is primarily the Rust-based backend which concerns itself with making editing operations very fast, and then you can write a front-end client for whatever language/platform you want.

In this case, they can use a fast Rust backend for multiple platforms (or just one) and then use Swift to make a nice, native front-end for MacOS and other native UI languages for other platforms if they wish.


Which is why I made the point on my comment about what the cross platform goals were, but the RIR folks are too quick to jump the gun in any kind of critic and only read half of it.


But you're making the exact opposite mistake, it was already written in Rust, you're asking them to Rewrite in Swift.


Cross platform future aside, they want to use all the good libs Rust has for ropes and the like. The code is based on another editor earlier work, and that's in Rust.

They also know Rust so if they want to use Rust, what's the problem in using it? They don't seem to have any problem with building a UI on top, it's built and looks/works fine.


No problem, hence why I wanted to know why. Maybe I should have read the post better.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: