Announcement

Collapse
No announcement yet.

Busd Taking Shape As A D-Bus Broker Written In Rust

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • intelfx
    replied
    Originally posted by fitzie View Post
    is tokio supported in rust4linux? heh.
    Are pthreads supported in c4linux? heh.

    Leave a comment:


  • ahrs
    replied
    Originally posted by Quackdoc View Post

    true. I hate how hard it is to build busd
    This is far too many steps, can somebody wrap this up into a
    Code:
    curl … | sudo bash -s -

    Leave a comment:


  • fitzie
    replied
    Originally posted by jacob View Post

    By that analogy C with pthreads is not a system language either. The point is that the assumption that using some sort of runtime system="managed"=slow and inefficient is absolutely not true.
    is tokio supported in rust4linux? heh. but it's not just the somewhat opaque runtime aspects of tokio, it's also the that async isn't fully well integrated with rust, so you lose a bit of rust language when you are in async, like with traits for example.

    Leave a comment:


  • cb88
    replied
    They should just switch to binder... which is already being rewritten in rust, and stop wasting time with dbus which is essentially a failure.

    Leave a comment:


  • bkdwt
    replied
    Originally posted by geerge View Post

    Your mom loved my rust code when I showed it to her last night.
    "yOuR MoN bLa BLa bla"

    So original, dumbfuck...

    Leave a comment:


  • lowflyer
    replied
    I thought I'm not seeing this day in my lifetime: A rust vs. C thread that mostly doesn't conflate C with C++.

    That's quite remarkable.

    Leave a comment:


  • Britoid
    replied
    Originally posted by zeenix147 View Post

    Rust is NOT a managed language. I didn't show memory usage because there was no reason to. If you have done any research whatsoever, you'd know that Rust's performance comes pretty close to C (even better than C++).



    Push back where? Do you see any assembly in the dbus-broker or dbus-daemon code? We snowflakes also write unsafe code where it bring performance benefits and even write C or assembly when needed.
    Agreed, Rusts performance in getting it's zealots to shout Rust everywhere is simply unmatched

    Leave a comment:


  • jacob
    replied
    Originally posted by fitzie View Post

    rust with tokio async (that busd uses) is not a systems programming language. change my mind.
    By that analogy C with pthreads is not a system language either. The point is that the assumption that using some sort of runtime system="managed"=slow and inefficient is absolutely not true.

    Leave a comment:


  • fitzie
    replied
    Originally posted by bug77 View Post

    Rust is mostly meant to be a systems programming language. What "new" do you need in that area? What "new" are you expecting in any area, really?

    On a more serious note, a DBus broker seems like a premier candidate for Rust, memory errors in such a component can open some serious holes in a system.
    rust with tokio async (that busd uses) is not a systems programming language. change my mind.

    Leave a comment:


  • polarathene
    replied
    Originally posted by Vorpal View Post
    I'm a bit surprised by the choice of tokio, since zbus uses async-std instead. I wonder what the reason for tokio here was.
    ​​
    Probably might have something to do with async-std not having had a release for over two years until recently? I don't do much async rust myself to provide much input to why tokio beyond that though.

    Leave a comment:

Working...
X