Junior compiler writers exist.

You can have a junior write compiler code, but you won’t have a junior compiler writer. It’s a very specific niche topic which does not have the demand for this.

They don’t teach CLIs and git and debugging in uni.

Well, they do. Version control is extremly useful for doing projects especially in groups and debugging is a necessary tool for building systems. These are not the main topic of the courses, but they are taught and practically mandatory.

Are you hard?! We’re talking about TV sizes, right?

Just because they are equivalent for the labguage does not mean they are interchangeable. I may choose to use single or double quotes in specific cases and need that change to be visible, even if the language rules say it is indifferent.

This is the obvious one: The way the string is written changes, but its content remains the same. There is nothing to highlight for SemanticDiff.

Moreover, my point was about how they phrase it. It seems they dismiss what the code means to developer by mentioning “content” and discarding “the way the string is written”.

Usually my models only store data, meaning the files that contain them don’t have much code. The decision also depends on the tools you are using and who you are working with. I would fallback to the rule of separation of responsabilities and write a new class for the purpuse of serializing the model (which could and should also serialize similiar models). This way is universal in any language and can easily be understood by future you and colleages.

The most obvious option: highlight what changed, the whole string. If you changed the string from interpolated to non-interpolated, the meaning of the whole string changed; it is no longer a method to concatenate variables, it has become a literal string.

Same for the example of single to double quotes. In some languages, double quotes are only used in specific contexts, so its use changes the meaning of the code. The post seems to dismiss this fact too easily.