News for hackers. Stuff that matters.
Re:Sealed Rust Update by jnordwick on Thursday February 13, 2020 @08:38PM (#22323239)
I 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.
Re:Sealed Rust Update by banana_smoothie on Thursday February 13, 2020 @08:47PM (#22323289)
From 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/

Re:Sealed Rust Update by sriram_sun on Friday February 14, 2020 @01:50AM (#22324490)
I 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)!

Re:Sealed Rust Update by tashoecraft on Thursday February 13, 2020 @09:13PM (#22323413)
Different 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.
Re:Sealed Rust Update by reificator on Thursday February 13, 2020 @10:00PM (#22323626)
1.) 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.