-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should rust be abandoned for fix protocol? #1
Comments
Hello @PipsqueakH! If performance is your biggest concern, I recommend using one of the existing open source C++ libraries which have been optimized and battle tested. I don't know if Rust should be abandoned for FIX but I don't think it's the right choice today. The first two problems I listed are being worked on but the third is a problem with Rust itself.
I think today's Rust fits into a niche where you want safety above all else, at least ~95% of C++'s performance, and don't depend on third-party libraries. |
thank you so much for your most valuable information and good luck to u. |
Do you feel the issues are well understood/communicated to the Tokio and Rust core teams? |
@mjmeehan Yes, I do. There was a recent discussion where people covered most of the problems I've had: https://users.rust-lang.org/t/what-does-rust-need-today-for-server-workloads/11114 I feel like tokio is in a situation similar to what happened with KDE 4.0. It was pushed too early as an already usable platform. In reality, it's more of an experiment that needs many iterations and will hopefully work completely differently some day. |
@jbendig Even though development has been halted, thank you for this library. |
@emileindik I would not recommend using this library in its current state. It has been awhile since I last worked on fix-rs but two really big hang-ups come to mind regarding FIX 4.2.
|
hi @jbendig ! I know that you halted on development a while ago on this - but have you looked at the recent state of the rust ecosystem to determine whether or not you feel that it is right to begin development on this again? Do you plan to pick up this crate in the future at any time? Thanks! |
hello @jbendig, I was going to ask the same question as @jakeschurch. Are there any plans to pick up on the development of this crate? I am seriously considering using Rust for a project and a library like yours would be really useful. Thanks. |
And here we are again in April 2020. Today's state of Async IO in Rust is way better. IMO async_std or Tokio 0.2 is a way to go. Moreover, Rust 2018 gives you much more power in controlling memory allocations. I'm going to work on FIX/FAST anyways regardless of the state of this library but It would be nice to revisit it |
@rucoder Nice. I think Rust is a good fit for this domain. @jbendig Btw, you can use something like Btw, I've been using Rust since 2014 and I haven't found that it leads to unnecessary cloning at all. Usually you can avoid cloning by adding references to your types (OR using clone-on-write OR using something like |
Given the state of this crate, about a year ago I started experimenting on my own to lay the foundations for another FIX implementation in Rust. I recently resumed development and I've got a generous sponsor which helps greatly. The name of the project is FerrumFIX. Mind you, it's in a very early stage. It kinda works, but you should refrain from using it in any meaningful way for now. I'm just posting this in case someone wants to take a look at the APIs or offer suggestions and get valuable feedback. Hopefully Rust will have a nice and up-to-date FIX library in a few months :) |
Hi all, So some more time has passed and I see @neysofu has started their own project which is looking quite good indeed. I'm interested to hear if @jbendig has any updates to their opinions about the state of the Rust ecosystem - both the language itself, and the tokio project? I'm quite new to the language myself and see its massive potential. |
The text was updated successfully, but these errors were encountered: