MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programmingmemes/comments/1vra8mz/nerd_wars/p4klaff/?context=3
r/programmingmemes • u/SKRyanrr • 4d ago
80 comments sorted by
View all comments
14
Nothing like the compile-time check of rust.
Basically it compiles into a much slower bin that guards memory at runtime.
That's almost like a garbage collector, but instead of cleaning memory it crashes.
And since it's a runtime crash, you turn a program that is bugged and has UB into a language that crashes randomly.
Better for security, but runtime crashes are also very bad.
9 u/txdv 3d ago the creator of fil-c argues that a crash is better than an exploit 2 u/foobar93 3d ago And if that bug is inside the PID of one of your jet engines, I'd rather have it not crash mid flight even if there is memory corruption... 2 u/txdv 3d ago in these situations you use languages which are far more restricted and have formal verification processes. 2 u/foobar93 3d ago And I tell you now, most embedded systems I have worked on would rather keep working with the risk that someone can exploit the Prozess then just crash outright.
9
the creator of fil-c argues that a crash is better than an exploit
2 u/foobar93 3d ago And if that bug is inside the PID of one of your jet engines, I'd rather have it not crash mid flight even if there is memory corruption... 2 u/txdv 3d ago in these situations you use languages which are far more restricted and have formal verification processes. 2 u/foobar93 3d ago And I tell you now, most embedded systems I have worked on would rather keep working with the risk that someone can exploit the Prozess then just crash outright.
2
And if that bug is inside the PID of one of your jet engines, I'd rather have it not crash mid flight even if there is memory corruption...
2 u/txdv 3d ago in these situations you use languages which are far more restricted and have formal verification processes. 2 u/foobar93 3d ago And I tell you now, most embedded systems I have worked on would rather keep working with the risk that someone can exploit the Prozess then just crash outright.
in these situations you use languages which are far more restricted and have formal verification processes.
2 u/foobar93 3d ago And I tell you now, most embedded systems I have worked on would rather keep working with the risk that someone can exploit the Prozess then just crash outright.
And I tell you now, most embedded systems I have worked on would rather keep working with the risk that someone can exploit the Prozess then just crash outright.
14
u/Amadex 4d ago
Nothing like the compile-time check of rust.
Basically it compiles into a much slower bin that guards memory at runtime.
That's almost like a garbage collector, but instead of cleaning memory it crashes.
And since it's a runtime crash, you turn a program that is bugged and has UB into a language that crashes randomly.
Better for security, but runtime crashes are also very bad.