Swap Chrome/Chromium for Firefox

poisson

https://www.zdnet.com/article/chrome-70-of-all-security-bugs-are-memory-safety-issues/

Looks like Chrome has hit a wall. Move to Firefox in the meantime.

vyas

Welcome back

Solaire

Blaming a programming language for your own faults.

Iroshan464

Main reason I use chrome is the instant history sync with phone and pc.
I may be an idiot but I prefer to have Google keep my search history, so that I might find something I looked up in 2013 on history.google.com ?

Rahul

@Iroshan464 said:
Main reason I use chrome is the instant history sync with phone and pc.
I may be an idiot but I prefer to have Google keep my search history, so that I might find something I looked up in 2013 on history.google.com ?

As Far As I Know,

@poisson said: Firefox

Has something like that too, maybe not exactly like

@Iroshan464 said: history.google.com

But, still works.

FlamingSpaceJunk

@Rahul said:

@Iroshan464 said:
Main reason I use chrome is the instant history sync with phone and pc.
I may be an idiot but I prefer to have Google keep my search history, so that I might find something I looked up in 2013 on history.google.com ?

As Far As I Know,
Has something like that too, maybe not exactly like

Yes, Firefox Sync. It works well.

@poisson said:
https://www.zdnet.com/article/chrome-70-of-all-security-bugs-are-memory-safety-issues/

Looks like Chrome has hit a wall. Move to Firefox in the meantime.

Ugh, ZDnet, and engilsh majors writing about technology.

I'm a Firefox user, so it really is the content of the article and not some Google fetish or large corp bootlicking.

@Solaire said:
Blaming a programming language for your own faults.

Right.

"Going forward, Google says it plans to look into developing custom C++ libraries to use with Chrome's codebase, libraries that have better protections against memory-related bugs."

Where have I heard that before? Oh yeah, in my college CS classes and OpenBSD. I thought this was common practice in the industry for working with C and C++?

serv_ee

People still use chrome. Smh.

Solaire

@FlamingSpaceJunk said:
"Going forward, Google says it plans to look into developing custom C++ libraries to use with Chrome's codebase, libraries that have better protections against memory-related bugs."

Where have I heard that before? Oh yeah, in my college CS classes and OpenBSD. I thought this was common practice in the industry for working with C and C++?

Yeah it is, that's why I'm so surprised to see this coming from a Google engineer. A bunch of things are written in C, including the Linux kernel and various services. It might be more difficult to implement code in a secure way using C, but it's not exactly rocket science either.

poisson

@vyas said:
Welcome back

Not exactly back full-time, but I hope to clear enough off my plate to.

serverian

As a result, both C and C++ let programmers have full control over how they manage an app's memory pointers (addresses) and don't come with restrictions or warnings to prevent or alert developers when they're making basic memory management errors.

FlamingSpaceJunk

@Solaire said:
Yeah it is, that's why I'm so surprised to see this coming from a Google engineer. A bunch of things are written in C, including the Linux kernel and various services. It might be more difficult to implement code in a secure way using C, but it's not exactly rocket science either.

Indeed. SEI CERT C Coding Standard

As others will point out, memory safety is great for stuff running in userspace, and it's mostly about programmer productivity. When memory safety is turned off, for the kind of things that happen in kernel space for instance, the memory safe language is just as error prone as C.

I want to say this had something to do with OpenBSD, and a mailing list discussion about why they aren't switching to Rust.

g4m3r

I don't like pointers either.