Immediately after switching the page, it will work with CSR.
Please reload your browser to see how it works.

Source:https://github.com/SoraKumo001/next-streaming

⬅️ How Not to Release Historic Source Code
nialv7 11 daysReload
This article irritates my in several ways:

* Complaining about someone doing a good thing

  Remember, Microsoft doesn't have to release this! Microsoft could choose to never release this and they will be completely in their rights to do so. Having something release at all is better then nothing. Calling it "not good enough", and asking for more sounds very entitled to me.
* Blaming the wrong tool

  Git doesn't care about file encoding, it can handle binary files perfectly fine. The most it will do is converting the line endings if you ask it to. The binary data is likely botched during encoding conversion, not by git.
* There are much better ways to achieve what the author wants

  I can see 2 possibilities. Either the files are botched when they were imported into the repo, in which case the original files are intact so nothing is lost. They could just asked for the original files, and they will most likely  get them. Or, the files were like this even before they were imported, perhaps corrupted at some point in the past. In that case writing an article to complain really won't achieve anything.
kazinator 11 daysReload
> But please please don’t mutilate historic source code by shoving it into (stupid) git. First of all, git does not preserve timestamps, which causes irreversible damage.

Git isn't stupid. A version control system must touch files to the current time whenever it changes them, otherwise timestamp-based incremental builds won't be correct.

Git records dates on a commit (which is an entire baseline of files). You can set that to whatever you want.

You can use that to record the file times, by creating commits which add the specific files, using their exact times.

codetrotter 12 daysReload
Sounds like uploading a zip to the releases page of the GitHub page, and linking it from the readme would be a good way to fix this. Then you have something close to the original that OP wants, and also have the git repo that people can clone and fork and experiment with.
jwnin 11 daysReload
Mistakes were made, but articles like this don't incentivize volunteers to continue to spend more time on preservation work.
gtirloni 11 daysReload
> First of all, git does not preserve timestamps, which causes irreversible damage

> the misguided use of git not only made some comment lines too long for MASM, but it also actively destroyed the original source code.

Nothing was mutilated or destroyed. These are not paper records. Nothing was lost. Someone just have to also release as a zip.