Chrome 101 Released With Priority Hints, Federated Credential Management API

[phoronix]

Phoronix: Chrome 101 Released With Priority Hints, Federated Credential Management API

Chrome 101 is out today as stable for the newest feature update to Google's cross-platform web browser...

https://www.phoronix.com/scan.php?page=news_item&px=Chrome-101-Released

[andyprough]

They should just announce the latest zero-day exploits in the release notes. Save them the time of writing separate press releases.

[Anvil]

who cares, its Goggle Chrom anyway

[eydee]

Wow they eventually did hit 100 before Firefox. Now the competition is over. Google won.
Let's see if Firefox goes back to 7.12.7 or whatever it's supposed to be right now. It's hard to keep track of it.

[birdie]

Wow they eventually did hit 100 before Firefox. Now the competition is over. Google won.
Let's see if Firefox goes back to 7.12.7 or whatever it's supposed to be right now. It's hard to keep track of it.

This numbering scheme is insanity and should be abandoned. It gives you zero idea what you're running whether it's fresh and actual.

I've proposed a different scheme for years now but no one is listening:

[YY]YY.MM, e.g. [20]22.4 - might not be good if there are several releases a month, see next

or

[YY]YY.NN, e.g. [20]22.5 (NN - is the release number for this year starting with 0).

This makes perfect sense and easy to read.

Ubuntu actually employed it and I'm almost thankful for that except they stick to crazy useless code names (check their mirrors - no actual releases, code names everywhere) which should have never been there in the first place. It's a Debian anachronism and should die ASAP.

[Anvil]

they should release it as 22.4.1 an 22.5.1 etc , kinda the same way Mesa versioning

[Jaxad0127]

This numbering scheme is insanity and should be abandoned. It gives you zero idea what you're running whether it's fresh and actual.

I've proposed a different scheme for years now but no one is listening:

[YY]YY.MM, e.g. [20]22.4 - might not be good if there are several releases a month, see next

or

[YY]YY.NN, e.g. [20]22.5 (NN - is the release number for this year starting with 0).

This makes perfect sense and easy to read.

Ubuntu actually employed it and I'm almost thankful for that except they stick to crazy useless code names (check their mirrors - no actual releases, code names everywhere) which should have never been there in the first place. It's a Debian anachronism and should die ASAP.

Unfortunately, a lot of sites check for simple version numbers, so that will break them.

[kylew77]

Calling Chrome Multiplatform is a bit of misnomer. They have limited Linux support and only officially support a small number of distros and don't even support any of the *BSDs or more exotic OSs. Basically they support ChromeOS, Windows, Mac, and throw crumbs at Linux while giving the middle finger to *BSDs.

[Charlie68]

Wow they eventually did hit 100 before Firefox. Now the competition is over. Google won.
Let's see if Firefox goes back to 7.12.7 or whatever it's supposed to be right now. It's hard to keep track of it.

This is a huge problem! Why not start from 000000001?

[microcode]

who cares, its Goggle Chrom anyway

The overwhelming majority of web users, that's who cares lol.