News for hackers. Stuff that matters.
Re:Chrome 81: Near Field Communications, Augmented Reality, ... by bjoli on Wednesday March 11, 2020 @03:35AM (#22543863)
Sure, web browsers implement a proper permission model, but: the surface of a browser is enormous. Just the sheer magnitude of a modern browser gives me vertigo. Chrome has how many compilers? How much code to handle broken input?

Whereas most kernels are easy to understand (even relatively modern ones like seL4), also many parts of a browser are at the frontier of "applied CS".

If I were to build something relatively small today, I don't think I would feel safe if it had to run in a browser due to the enormous complexity of a browser. I just don't think it is possible to secure them fully.

Writing everything myself at least gives me a false sense of security in the sense that I at least believe I understand what is running :)

Re:Chrome 81: Near Field Communications, Augmented Reality, ... by moooo99 on Wednesday March 11, 2020 @04:57AM (#22544218)
Okay, from a software engineering perspective you're 100% right. Browsers are a very complex system and they'll continue to grow. But try to see it from a user perspective.

You as a software developer know how your system works. You know what components you used, how to compile and install and how to secure. Your average user (depending on the target audience) doesn't know anything like this. Most users are happy when their current installation works, they often don't want to update, without realizing that this comes with the cost of their security.

I feel like webapps are the easier way to keep users with no experience secure.

Re:Chrome 81: Near Field Communications, Augmented Reality, ... by saagarjha on Wednesday March 11, 2020 @07:55AM (#22544994)
> Whereas most kernels are easy to understand

Have you taken a look at Linux?!