8 ms·
Sealed Rust Update
- sliken 7y agoThe working URL https://ferrous-systems.com/blog/sealed-rust-the-plan/ https://ferrous-systems.com/blog/sealed-rust-the-plan/
- jnordwick 7y agoI want much more runtime performance out of rust more than anything else. Faster builds are second on the list. This probably doesn't even make top 10. Who is this aimed at? And I would hate for those top goals to be subverted for this.
- banana_smoothie 7y agoFrom the previous blog post ("Part 1: The Pitch"[1]): > We hope that the Sealed Rust effort would be applicable to any developers working in safety critical software domains, such as: > Automotive (under safety standard ISO26262) > Industrial (under safety standard IEC61508) > Robotics (under a number of safety standards deriving from IEC61508) > Medical Devices (under safety standard IEC62304) > Avionics (under safety standard DO-178) [1]: https://ferrous-systems.com/blog/sealed-rust-the-pitch/ https://ferrous-systems.com/blog/sealed-rust-the-pitch/
- sriram_sun 7y agoI work in medical devices and out-of-the-box rust would be a much better option than the C++ systems we build! There is competition in this space from qnx as well. Take a look at the medical device alarms standard IEC 60601-1-8. It's possible to provide a very generic implementation of the standard for high, low and medium priority alarms. Could act as a trojan horse to introduce your back end messaging, logging, shared memory infrastructure - all developed according to ISO 62304 (of course)!
- tashoecraft 7y agoDifferent people have different needs. There’s also room for many different people to work on different problems at the same time without imposing constraints on each other.
- reificator 7y ago1.) Do you work in safety critical software? If not, this is not for you. 2.) This is a third party, this is not taking resources from generic rust.
- im3w1l 7y agoI know some of those words... Sounds really neat. Hope it goes well.
- analognoise 7y agoI don't get why there is so much love for Rust but so little love for Ada?
- im_down_w_otp 7y agoThere's a lot of love for Ada. Unlike Rust, Ada is already an approved language and toolchain for safety-critical software development. That Sealed Rust is trying to do what it takes to get Rust into the approved language & toolchain category along side Ada is entirely the point, and what makes it interesting.
- ajxs 7y agoThere's plenty of love for Ada, more than ever. https://blog.adacore.com/the-emergence-of-a-new-ada-era https://blog.adacore.com/the-emergence-of-a-new-ada-era
- justinclift 7y agoPotentially interestingly, it looks like there's ongoing work to get Ada compiling to wasm via LLVM too. Hello World style demo: https://blog.adacore.com/use-of-gnat-llvm-to-translate-ada-applications-to-webassembly https://blog.adacore.com/use-of-gnat-llvm-to-translate-ada-a...
- pjmlp 7y agoI guess, due to a couple of things. 1 - There is a younger generation that thinks C and C++ are the only game in town, and never learn about myriad of systems programming languages going back to 1961. 2 - This same generation is very averse paying for tooling and among the six surviving Ada compiler vendors, GNAT is the only free one, and even then discussions about its licensing pop up ('cause lets have free beer) 3 - Ada suffers from the whole bondage vs cowboy programming theme that was so common in the early 90's. Where many could not grasp the benefits of type driven programming. 4 - You need a strong engineering background, specially on high integrity computing domain, to understand why Ada offers what it does 6 - Due to high integrity computing domain, Ada tends to be used in domains that many don't find cool, government contracts, train control systems, airplane avionics, pages long contracts with project management very waterfall like even when they pretend to be agile now 7 - It is definitely not a language for the Silicon Valley culture. However thanks to Ada being there first, having the certified compilers, being deployed into production during the last 40 years, with the increasing number of security exploits, some companies have been adopting Ada, NVidia being one of them. https://blogs.nvidia.com/blog/2019/02/05/adacore-secure-autonomous-driving/ https://blogs.nvidia.com/blog/2019/02/05/adacore-secure-auto... Two of the reasons, for why Ada and not Rust, was precisely the lack of maturity of Rust on high integrity computing and Ada being more approachable to their engineers. They did a webinar about the adoption process.
- _bxg1 7y agoThis is an important effort, but it's weird (disconcerting?) to me that something so fundamental as a formal language specification (for a language that advertises safety as a key feature) is being bootstrapped not by the core team, but by a third party. It doesn't feel like that's something you only need "collaboration with" the core team about. I can't think of anything that's more "core". The rest of it makes sense as an auxiliary effort: working directly with relatively niche industries on certification, narrowing down a fully-safe subset of the language, etc. But I don't see how Rust can ever come into its own in the space that it's targeting without having a real specification outside of the compiler.
- chrismorgan 7y agoSpeaking bluntly: Almost everyone using the language at present is getting by just fine without this. As a normal Rust developer, I don’t particularly care about a formal language specification existing. It’s a long way down my list of nice-to-haves—yeah, it would be nice to have, but there are quite a few other things that would be more nice to have. The core team are compiler and language developers. I’d much rather have them working on the language, rather than a formalisation of the language that isn’t going to benefit me particularly for many years. If there are other people that are interested in doing that work, good on ’em; it’ll be interesting to see what happens, but I don’t want the core developers distracted with this sort of speculative work—for this is a heavily experimental area. This is absolutely a place for only a collaboration, rather than having it being managed by the core team. If the core team were focusing on this, everything would collapse in a heap. The core team is a very finite resource that does not specialise in this sort of thing in any way.
- saurik 7y agoI think the argument is that if you said that about C++ everyone would be "yeah: this is just a useful tool, so why do I care?"... but Rust is about safety, and if you don't have a formal model of the language by what reasoning could you possibly have to know it is safe? (And, in fact, every now and then--much less often these days, but still--someone finds a soundness issue in Rust itself, something you would hope to have been able to disprove at the outset using a proof over a formal model.)
- xvilka 7y agoI am surprised they didn't mention Iris[1] and RustBelt[2] projects. Iris works on creating the formalization framework based on separation logic and Coq. They have the Rust code model specifically[3]. [1] https://iris-project.org/ https://iris-project.org/ [2] https://plv.mpi-sws.org/rustbelt/ https://plv.mpi-sws.org/rustbelt/ [3] https://gitlab.mpi-sws.org/iris/lambda-rust https://gitlab.mpi-sws.org/iris/lambda-rust
- Argorak 7y agoThis is mainly a lapse. Thanks for highlighting them, they do awesome work! They are also not quite what Sealed Rust is about. RustBelt is about formally verifying Rust and improving the understanding of the language. Sealed Rust is mainly about the industrial adoption process. It's not meant as a replacement or competing project, quite the contrary: RustBelt existing is a huge motivator and a major stepping stone to build on. We are also personally in touch through the Rust project.