Announcement

Collapse
No announcement yet.

Google Begins Allowing Rust Code For Developing Android

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

  • ssokolow
    replied
    Originally posted by 60Hz View Post

    The burden of proof is on Rustards.

    It's accomplished almost nothing so far. Even Mozilla found it extremely underwhelming, except for the small team of fanbois that got laid off.
    Ahh, so you're trolling. I'll leave you to have the last word then since further discussion wouldn't be productive.

    Leave a comment:


  • 60Hz
    replied
    Originally posted by ssokolow View Post

    [citation needed]
    The burden of proof is on Rustards.

    It's accomplished almost nothing so far. Even Mozilla found it extremely underwhelming, except for the small team of fanbois that got laid off.

    Leave a comment:


  • ssokolow
    replied
    Originally posted by 60Hz View Post

    They've failed miserably.
    [citation needed]

    Leave a comment:


  • 60Hz
    replied
    Originally posted by ssokolow View Post
    The Rust developers have been crowing since the beginning that "Nothing good about Rust is original" is a virtue. It's always been about taking ideas that have been kicking around in academia for decades and hammering them into a shape the mainstream will accept.
    They've failed miserably.

    Leave a comment:


  • jabl
    replied
    Originally posted by mdedetrich View Post

    WTF is wrong with google using bluez or at least contributing to it if there are problems?
    tl;dr: GPL hate

    From wikipedia:

    "Aiming for a different licensing model, toward the end of 2012, Google switched the Bluetooth stack in Android from the GPL-licensed BlueZ to the Apache-licensed BlueDroid. A new Bluetooth stack, called Gabeldorsche, was developed to try to fix the bugs in the BlueDroid implementation."

    Leave a comment:


  • mdedetrich
    replied
    Originally posted by jabl View Post

    Google is working on a new (the 3rd?) bluetooth stack for android called 'Gabeldorsche', this time (partially) using Rust: https://android.googlesource.com/pla...aster/gd/rust/
    WTF is wrong with google using bluez or at least contributing to it if there are problems?

    Leave a comment:


  • ssokolow
    replied
    Originally posted by 60Hz View Post

    None of those things are innovations of Rust.

    Nothing good about Rust is original and nothing original about Rust is good.
    The Rust developers have been crowing since the beginning that "Nothing good about Rust is original" is a virtue. It's always been about taking ideas that have been kicking around in academia for decades and hammering them into a shape the mainstream will accept.

    Leave a comment:


  • 60Hz
    replied
    Originally posted by andreano View Post
    I see C++ becoming more and more like Rust for each new revision. I predict that by C++2121, we will finally have destructive move semantics, ownership, slices, sum types with exhaustive matching, zero-sized types, zero-overhead optionals, a way to declare that a type is either memcpy-copyable or -movable without implementing 4 functions, compile time reflection, the deprecation of inheritance by something like traits (concepts) and the deprecation of exceptions by something like Result (std::expected).
    None of those things are innovations of Rust.

    Nothing good about Rust is original and nothing original about Rust is good.

    Leave a comment:


  • andreano
    replied
    C++ done right
    I see C++ becoming more and more like Rust for each new revision. I predict that by C++2121, we will finally have destructive move semantics, ownership, slices, sum types with exhaustive matching, zero-sized types, zero-overhead optionals, a way to declare that a type is either memcpy-copyable or -movable without implementing 4 functions, compile time reflection, the deprecation of inheritance by something like traits (concepts) and the deprecation of exceptions by something like Result (std::expected).

    By that time, there will be a lot of obsolete cruft in C++. I also have the impression that the same features are better code reviewed when they go into Rust than when they go into C++.

    Leave a comment:


  • dc_coder_84
    replied
    Originally posted by bug77 View Post
    What does that bring to the table on top of Rust?
    Chris Lattner said the following when comparing Swift to Rust. He said the benefit of Swift is you don't have to always wrap your head around the borrow checker. I think the idea is to use Swift for application programming with no ownership annotations and with them in systems programming. That way you would have one language for application programming and low level software. I have not followed the recent Swift development but I guess Swift is not there yet. But sooner or later...

    Leave a comment:

Working...
X