Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox
by bsagdiyev on Monday April 15, 2019 @06:42PM
(#19669558)
Of course, rewriting in Rust is the only moral choice, right?
[ Parent
| on HN ]
Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox
by maximilianburke on Monday April 15, 2019 @07:18PM
(#19669738)
I wouldn’t say moral choice but watching these types of issues crop up again and again even when the original vulnerable code has been written and reviewed by people with impeccable credentials and with the best intentions should give pause to those who wish to pursue new development with fundamentally vulnerable technologies, especially when there are alternatives that exist where these problems are much less likely to happen.
Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox
by Waterluvian on Monday April 15, 2019 @07:23PM
(#19669764)
We don't tear down every building when we update the building code. We just improve how we build the new ones.
Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox
by goalieca on Monday April 15, 2019 @08:08PM
(#19669971)
Or we require people to bring it up to code when they do major renovations (seems more in line with the Firefox rewrite)
Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox
by s_y_n_t_a_x on Monday April 15, 2019 @11:28PM
(#19670902)
FF does abide by this rule in-fact. Almost every new component is written in Rust. https://wiki.mozilla.org/Oxidation
Re:Virtually Unlimited Memory: Escaping the Chrome Sandbox
by s_y_n_t_a_x on Monday April 15, 2019 @07:30PM
(#19669809)
So a new browser?