3 ms·

A lot of that is probably static art assets. A lot of big corporate projects are guilty of just throwing everything in one tree like this where for some bizarre

by zanny 9y ago

A lot of that is probably static art assets. A lot of big corporate projects are guilty of just throwing everything in one tree like this where for some bizarre reason you are checking out jpgs and video files. It is part of the reason why the Chrome or Unreal Engine repos are preposterously large (hundreds of megs to gigabytes each).

ansible 9y ago
And there was an article a few weeks back about how certain content creation tools (Adobe) stuff in lots of metadata into these assets by default. Some of the MS teams were good about stripping those out for release, others, didn't seem to notice.
- ygra 9y ago
  Well, to be fair, the metadata in those files amounted to 5 MiB over the whole of Windows, so while there is a little overhead, it won't make up a significant chunk.
  - ansible 9y ago
    Oh, I didn't see that part. That's not nearly as bad as I thought based on my reading of the original article.
MaulingMonkey 9y ago
> A lot of big corporate projects are guilty of just throwing everything in one tree like this where for some bizarre reason you are checking out jpgs and video files. Would you want to build chrome without it's icons for bookmark folders, the launcher, etc.? No? What about a game without it's intro videos? Even if you need to debug a crash during the initial intro, related to playing said video? Some people prefer this kind of content to be managed with a different, media focused version control system, or a separate tree, but now you have 2+ disparate distribution / version control systems to try and keep in sync. You do have options like git submodules now for some VCSes, but I haven't been impressed with their workflow, and they weren't always an option. I will gladly burn several gigs just to simplify my workflow - I've got the spare SSD and bandwidth. I've had fully built checkouts in the hundreds of gigabytes range. And don't get me wrong, "hundreds of gigabytes" is getting annoyingly large if the IT department skimped and bought me a 250GB SSD. I'll abuse directory junctions to offload some of that onto mechanical drives. This is relatively fire and forget though - multi-repository is not.

by zanny 9y ago

ansible 9y ago

And there was an article a few weeks back about how certain content creation tools (Adobe) stuff in lots of metadata into these assets by default. Some of the MS teams were good about stripping those out for release, others, didn't seem to notice.

ygra 9y ago
Well, to be fair, the metadata in those files amounted to 5 MiB over the whole of Windows, so while there is a little overhead, it won't make up a significant chunk.
- ansible 9y ago
  Oh, I didn't see that part. That's not nearly as bad as I thought based on my reading of the original article.

MaulingMonkey 9y ago

> A lot of big corporate projects are guilty of just throwing everything in one tree like this where for some bizarre reason you are checking out jpgs and video files. Would you want to build chrome without it's icons for bookmark folders, the launcher, etc.? No? What about a game without it's intro videos? Even if you need to debug a crash during the initial intro, related to playing said video? Some people prefer this kind of content to be managed with a different, media focused version control system, or a separate tree, but now you have 2+ disparate distribution / version control systems to try and keep in sync. You do have options like git submodules now for some VCSes, but I haven't been impressed with their workflow, and they weren't always an option. I will gladly burn several gigs just to simplify my workflow - I've got the spare SSD and bandwidth. I've had fully built checkouts in the hundreds of gigabytes range. And don't get me wrong, "hundreds of gigabytes" is getting annoyingly large if the IT department skimped and bought me a 250GB SSD. I'll abuse directory junctions to offload some of that onto mechanical drives. This is relatively fire and forget though - multi-repository is not.