If you think about it, you eat instant noodles, hum songs, and surf the Internet, and suddenly find that the browser can't be used, how uncomfortable it is.
Of course, this is not a bad reviewer blindly taking the rhythm, because this thing is really a little bit likely to happen.
Because Chrome, one of the most popular browsers in the world, is about to release its 100th version. This update is likely to cause some bugs, resulting in the web page can not be opened directly.
If the surfboard is broken, how can we surf?
Chrome is all too familiar to everyone, and this browser, known as the memory eater, has more than 2 billion installed capacity on this planet.
At least in the newsroom, with the exception of a few Safari users, Chrome's coverage is neither 90% nor 80%. And the rest are mostly using various chromium "shell" browsers.
Then the problem comes, other people's software updates are not built-in Unreal Engine, add some new features, or fix some bugs, so that the product is more stable.
Chrome, you billionaire celebrity, have updated it, but instead fixed the "bug with too few bugs"?
Isn't this putting users into treasure?
In fact, this pot really can't blame Google's engineers, and what triggered this bug is a thing called version number.
Because in the eyes of some websites, the version number 100 is less than 40.
Next, please prepare potato chips and cola, bad reviewers will talk to everyone about what happened behind this hot pot can do the right thing than the size of the problem, this bug that makes everyone may not be able to get on the net.
Simply put, when you visit a small website, the website needs to know what browser and version you are using.
On the one hand, websites can show users with the latest version of the browser new features, new interactions, and in turn provide content that suits the "antique" browsers.
Just like IE Browser before IE9 does not install plug-ins, it does not support SVG functionality. For today's major browsers, SVG has long been a mediocre thing.
On the other hand, for reasons of network security, websites can also directly refuse browsers that have not been updated to access the website according to the version number.
In general, the website knows "who is coming", and then decides whether to pick up the customer or not, and after the pick-up, it looks at the dish.
The upcoming version number 100 update brought by chrome browser is likely to make some websites recognize the wrong guests and then directly turn users away.
Take the Chrome browser used by the bad reviewer as an example, the website will check the following browser UA (User Agent String) to check a wave of accounts:
Mozilla/5.0( Windows NT 10.0; Win64; x64 ) AppleWebKit/537.36 ( KHTML , like Gecko )Chrome/97.0.4692.99Safari/537.36
There's a lot of stuff in there, and we're looking for Chrome/97.0.4692.99.
For most website developers, they only need to pay attention to the character "97" immediately after Chrome/, which is actually enough for the website to identify the browser and look at the dish according to the version.
And it just so happens that a small foreign famous web design toolkit named Duda is lazier.
Because it only reads the two numbers behind Chrome/...
So after chrome's version number goes up to 100, when you visit websites developed with Duda, they will only recognize half of the words and think your version number is 10.
Even more mind-provoking, Duda also automatically blocks Chrome browser access with a version number lower than 40...
So in their eyes 100 = 10, your browser is thus forbidden to access.
Although this wave is undoubtedly the pot of Duda programmers, to some extent, Chrome programmers actually have a pinch of responsibility.
The mistake is that Chrome's programmers are too explosive, resulting in Chrome updates being too diligent.
Let's put it this way, Chrome, which is 13 years old this year, was updated only once every 12 weeks in the early days, accelerated to 6 weeks, and updated every 4 weeks later.
In this way, Chrome's version number has quickly soared, and the 100th version is about to be ushered in by March this year.
So if Chrome's engineers had touched more fish and put more, this bug wouldn't have appeared so early.
Finish the pot, but the problem must always be solved.
Google, which has long been aware of the possibility of bugs, provided a test flag last year.
Just type chrome ://flags into the browser and then type and open #force-major-version-to-100 to make the site break the two-digit spell and force the version number to be 100.
The temperament of foreigners also seems to be reconciled and compromised, because some netizens have proposed another moderate solution.
That is to make Google's version stop at 99 forever, and then the update will change to the decimal point.
However, no matter how these people come up with advice, they are all "the emperor is not anxious about eunuchs", and you must know that the old saying is good: you must tie the bell to the ringer!
Fortunately, the real culprit, Duda, made an announcement shortly afterwards, saying that it had updated the code and solved the problem.
On Google's website, which reported the bug, the problem has also been marked as Fixed.
After the version numbers of Chrome and FireFox browsers really reach 100, how many Duda-like bugs have not been discovered, we don't know.
It can only be said that the "millennium bug" problem in the browser world has only been temporarily solved.
In addition, poor friends with a better memory should remember that at the beginning of this year, Microsoft also had a similar millennium bug problem.
It has left Microsoft employees with a long time.
The general plot of this BUG is that on January 1 of this year, many companies using Microsoft Exchange found that the mailbox could not be sent.
The reason behind this is actually quite simple, that is, Microsoft uses a symbolic variable called "yymmddhhmm" (year, month, month, day, day, hour, minute) to store time.
The signed int32 can only store -2147483648 to 2147483648 data, which is 2 to the 32nd power.
Originally set up in the last century to save storage space, it has become a bug. Because the last two digits of 22 in 2022 are brought into the "yymmddhhmm", they directly exceed the value range of int32...
Fortunately, under the overtime of Microsoft Siege Lion, the relevant problems have been solved, and catching insects overnight may be their New Year's gift.
In general, in the field of science and technology Internet, there has always been a similar ancestral code, or for compatibility, or to save time and not to repeat the wheel, those codes with the limitations of the times, as well as the bugs in the code for thousands of years, have been passed down from generation to generation.
And everyone also calls these stinky and bug-rich code mountains.
So, bugs like browser version numbers and date stores aren't the first, and certainly won't be the last.
Finally, you can wait for another wave of upcoming 2038 issues.
Of course, there should be no 32-bit devices at that time, perhaps, it will be gone.
Author: Jiang Jiang Editor: Noodle Beauty Editor: Huan Yan
Images, sources:
The question: Will Chrome 100 create the "Millennium Bug" reality again? @FydeOS's answer
New Zhiyuan, Chrome browser global big rollover? "Over 100 minus 90" has left more than 2 billion users without access to the Internet.
Qubits, Microsoft 2022 New Bug: A large number of programmers work overtime overnight only because of date data overflows