It was always a big deal. But back then it was often pretty obvious when it was a fake. It's getting harder and harder to tell.

Yeah that's the real issue lol

You've linked to the save page and it's failing. The link works if you remove /save/ from it

But that's more key presses than just using existing keys

Don't really get your point here.

They virtualize the file because it's big. They know the size.

It does indeed scale with the size of the file. That's exactly the problem.

No it relies on the c# project files. It looks for all projectreference tags in the projects file and recursively grabs all of them and turns them into filters.

You have a list of filters like "src/libs/whatever/*" if there is a change the pipeline runs.

I wrote a tool that automatically updates these based on recursive project references (c#)

So if any project referenced by the service (or recursively referenced by dependencies) changes the service is rebuilt.

If pretty much gets compiled to a goto statement. Well more a jumpif but same principle

What about the kitchen?

A certain world event being a 3rd party piece of software having a bad update.

We use a mono repo for a new cloud based solution. So far it's been really great.

The shared projects are all in one place so we don't have to kick things out to a package manager just to pull them back in.

We use filters in azure pipelines so things only get built if they or dependent projects get changed.

It makes big changes that span multiple projects effortless to implement.

Also running a local deployment is as easy as hitting run in the ide.

So far no problems at all.