Earlier quoted context omitted.
UWP everywhere now though.
Is that true? Which larger app is written in UWP? Something like Office, Skype or Visual Studio.
Windows itself is gradually rewriting its shell components in UWP XAML.
The largest Git repo
281–290 of 416 posts
Re: The largest Git repo
#282Earlier quoted context omitted.
No, it should be hard to make arbitrary changes. If you change the word "arbitrary" to "necessary" (implying a different bias than the one you went with) then all of a sudden this attitude sounds less helpful. Similarly "easy to limp along with a bad architecture" could be re-written as "easy to work with the existing architecture". At the end of the day, it's about getting work done, not making decisions that are th…
You have to balance getting work done vs. purity, and Microsoft has spent years trying to fix a bad balance. Windows ME/Vista/8 were terrible and widely hated pieces of software because of "getting things done" instead of making good decisions. They made billions of dollars doing it, don't get me wrong, but they've also lost a lot of market share too and have been piling on bad sentiment for years. They've been pivot…
Those releases (well, Vista and 8 anyway, I don't know about ME) came out of a long and slow planning process - if they made bad decisions I don't think it was about not taking long enough to make them.
Re: The largest Git repo
#283Earlier quoted context omitted.
No, it should be hard to make arbitrary changes. If you change the word "arbitrary" to "necessary" (implying a different bias than the one you went with) then all of a sudden this attitude sounds less helpful. Similarly "easy to limp along with a bad architecture" could be re-written as "easy to work with the existing architecture". At the end of the day, it's about getting work done, not making decisions that are th…
> At the end of the day, it's about getting work done, not making decisions that are the most "pure". This attitude will lead to a total breakdown of the development process over the long term. You are privileging Work Done At The End Of The Day over everything else. You need to consider work done at every relevant time scale. How much can you get done today? How much can you get done this month? How much can you get…
> This attitude will lead to a total breakdown of the development process over the long term.
As evidenced by Microsoft following the one repo rule and not being able to release any new software.
Wait, what ?
Re: The largest Git repo
#284Archive Team is making a distributed backup of the Internet Archive. http://archiveteam.org/index.php?title=INTERNETARCHIVE.BAK Currently the method getting the most attention is to put the data into git-annex repos, and then have clients just download as many files as they have storage space for. But because of limitations with git, each repo can only handle about 100,000 files even if they are not "hydrated". http:…
Could bup be useful in addition to git-annex?
https://github.com/bup/bup
Re: The largest Git repo
#285Earlier quoted context omitted.
> At the end of the day, it's about getting work done, not making decisions that are the most "pure". This attitude will lead to a total breakdown of the development process over the long term. You are privileging Work Done At The End Of The Day over everything else. You need to consider work done at every relevant time scale. How much can you get done today? How much can you get done this month? How much can you get…
The linux codebase exists in stark contrast to your claim. Assuming your claim is that broken up repos is the better way.
No it doesn't. I think you are thinking of the kernel, which is separate from all the distros.
Linux by itself is just a kernel and won't do anything for you without the rest of the bits that make up an operating system.
Re: The largest Git repo
#286Maybe I missed it, but I wish they would have compared times to what they were using before (Source Depot).
I guess I would more specifically like to know what pain points drove Microsoft to even try such a massive change.
Re: The largest Git repo
#287Earlier quoted context omitted.
> At the end of the day, it's about getting work done, not making decisions that are the most "pure". This attitude will lead to a total breakdown of the development process over the long term. You are privileging Work Done At The End Of The Day over everything else. You need to consider work done at every relevant time scale. How much can you get done today? How much can you get done this month? How much can you get…
> This attitude will lead to a total breakdown of the development process over the long term. As evidenced by Microsoft following the one repo rule and not being able to release any new software. Wait, what ?
The text I quoted had nothing to do with monolithic repos.
Re: The largest Git repo
#288Earlier quoted context omitted.
UWP everywhere now though.
Is that true? Which larger app is written in UWP? Something like Office, Skype or Visual Studio.
There is a watered-down version of Office in UWP.
The built-in OneNote is actually this UWP. It uses a different stylus filtering algorithm from the desktop version, which is why I don't use it myself, but rest assured it works just fine.
Re: The largest Git repo
#289Re: The largest Git repo
#290A handful of us from the product team are around for a few hours to discuss if you're interested.
I'm currently investigating using GitLFS for a large repo that has many binary and other large artifacts. I'm curious, did you experiment with LFS for prior to building GitVFS? Also, I know that there is an (somewhat) active effort to port GitVFS to Linux, do you know if any of the Git vendors (GitLab and/or GitHub) are planning to support GitVFS in their enterprise products?
We at GitLab are looking at GitVFS but have not made a decision yet https://gitlab.com/gitlab-org/gitlab-ce/issues/27895