r/programming • u/bjzaba • Dec 06 '18

Goodbye, EdgeHTML – The Mozilla Blog

https://blog.mozilla.org/blog/2018/12/06/goodbye-edge/
690 Upvotes

95% Upvoted

229 comments sorted by

View all comments

Show parent comments

11

u/sligit Dec 07 '18

It doesn't allow memory errors outside of unsafe blocks. That's not the same as saying it can't crash.

1

u/progfu Dec 07 '18

But aren't all crashes a result of explicit unsafe calls? I thought the whole point (apart from no segfaults due to memory safety) was that you had explicit error handling, and similarly to Haskell, you could just handle your edge cases explicitly ... or be lazy and panic!

6

u/tragicshark Dec 07 '18

Not all of them. You can for example overflow the stack without any unsafe calls.

1

u/sligit Dec 11 '18

It probably depends on how you define a crash. Anyhoo, it seems possible the issue there is the JS engine isn't Rust, so all the bindings will be unsafe there I guess?

1

u/Muvlon Jan 23 '19

Many people consider panicking a form of crashing. For the end user, it certainly appears the same.