Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We shrunk our Javascript monorepo git size

jonathancreamer.com

Post reply on HN
Print view View original

141–150 of 226 posts

Re: We shrunk our Javascript monorepo git size

#141

Post by tom_ »

59nadir wrote: post #106
triyambakam wrote: post #9

> we have folks in Europe that can't even clone the repo due to it's size. What is it about Europe that makes it more difficult? That internet in Europe isn't as good? Actually, I have heard that some primary schools in Europe lack internet. My grandson's elementary school in rural California (population <10k) had internet as far back as 1998.

Most european countries have connections with more bandwith and less base latency for cheaper than the US, it's not a connection issue. If there was an issue it's that the repo itself is hosted on the other side of the world, but even so the sidenote itself is odd.

I wouldn't say it's odd at all - it's basically what's justifying actually trying to solve the problem rather than just going "huh... that's weird..." then putting it on the backlog due to it not being a showstopper.

This sort of thing has been a problem on every project I've worked on that's involved people in America. (I'm in the UK.) Throughput is inconsistent, latency is inconsistent, and long-running downloads aren't reliable. Perhaps I'm over-simplifying, but I always figured the problem was fairly obvious: it's a lot of miles from America to Europe, west coast America especially, and a lot of them are underwater, and your're sharing the conduit with everybody else in Europe. Many ways for packets to get lost (or get held up long enough to count), and frankly it's quite surprising more of them don't.

(Usual thing for Perforce is to leave it running overnight/weekend with a retry count of 1 million. I'm not sure what you'd do with Git, though? it seems to do the whole transfer as one big non-retryable lump. There must be something though.)

Re: We shrunk our Javascript monorepo git size

#142

Post by mb7733 »

dijit wrote: post #133
atombender wrote: post #130

Earlier quoted context omitted.

Which examples?

VSCode is a prominent one that is in everyones mind, its starting its journey into extinguish. For more examples I would consult your local greybeard; since the pattern is broad enough that you can reasonably argue that “this time, its different” which is also what you hear every single time it happens.

What is being embraced, extended and extinguished by vscode?

Re: We shrunk our Javascript monorepo git size

#143

Post by dagw »

mb7733 wrote: post #142
dijit wrote: post #133

Earlier quoted context omitted.

VSCode is a prominent one that is in everyones mind, its starting its journey into extinguish. For more examples I would consult your local greybeard; since the pattern is broad enough that you can reasonably argue that “this time, its different” which is also what you hear every single time it happens.

What is being embraced, extended and extinguished by vscode?

A lot of new and popular features in VSCode are only available in the official MS version of VSCode. Using any of the forks of VSCode thus becomes a lesser experience.

Microsoft Embraced by making VSCode free and open source. Then they Extended by using their resources to make VSCode the go to open source IDE/Editor for most use cases and languages, killing much of the development momentum for none VSCode based alternatives. Now they're Extinguishing the competition by making it harder and harder to use the ostensibly open source VSCode codebase to build competing tools.

Re: We shrunk our Javascript monorepo git size

#144

Post by Deathmax »

mattlondon wrote: post #102
_joel wrote: post #83

Earlier quoted context omitted.

You must be unlucky, according to Openreach "fibre broadband is already available in more than 96.59 per cent of the UK."

Is that "fibre" or "full fibre". They lied a lot for a good few years saying "OMG fibre broadband!" When in reality is was still copper for the last mile so that "fibre" connection in reality was some ADSL variant and limited to 80/20mpbs. Actual full fibre all the way from your home to the internet is I think still quite a way behind. Even in London (London! The capital city with high density) there are places where…

According to ThinkBroadband's tracking [1], the headline figures are 85.20% of premises are gigabit capable (FTTP/FTTH/Cable [DOCSIS]) with 71.86% being full fibre.

[1]: https://www.thinkbroadband.com/news/10343-85-gigabit-coverag...

Re: We shrunk our Javascript monorepo git size

#145

Post by sshine »

rettichschnidi wrote: post #34

I'm surprised they are actually using Azure DevOps internally. Creating your own hell I guess.

> I'm surprised they are actually using Azure DevOps internally. Creating your own hell I guess.

Even the hounds of hell may benefit from dogfooding.

Re: We shrunk our Javascript monorepo git size

#146

Post by acdha »

yunusabd wrote: post #10

> For many reasons, that's just too big, we have folks in Europe that can't even clone the repo due to it's size. What's up with folks in Europe that they can't clone a big repo, but others can? Also it sounds like they still won't be able to clone, until the change is implemented on the server side? > This meant we were in many occasions just pushing the entire file again and again, which could be 10s of MBs per fil…

My guess is that “Europe” is being used as a proxy for “high latency, low bandwidth” – especially if the person in question uses a VPN (especially one of those terrible “SSL VPN” kludges). It’s still surprisingly common to encounter software with poor latency handling or servers with broken window scaling because most of the people who work on them are relatively close and have high bandwidth connection.

Re: We shrunk our Javascript monorepo git size

#147

Post by deskr »

jakub_g wrote: post #67

Paraphrasing meat of the article: - When you have multiple files in the repo which have the same trailing 16 characters in the repo path, git may wrongly calculate deltas, mixing up between those files. In here they had multiple CHANGELOG.md files mixed up. - So if those files are big and change often, you end up with massive deltas and inflated repo size. - There's a new git option (in Microsoft git fork for now) an…

> in Microsoft git fork for now

Wait, what? Has MS forked git?

Re: We shrunk our Javascript monorepo git size

#148

Post by singron »

zelphirkalt wrote: post #72
0points wrote: post #57

Earlier quoted context omitted.

What european countries still dont have fiber? //Confused swede with 10G fiber all over the place. Writing from literally the countryside next to nowhere.

If you really need it pointed out, take it from a German neighbor: Telekom is running some extortion scheme or so here. Oh we could have gotten fiber to our house already ... if we paid them 800+ Euro! So we rather stick with our 100MBits or so connection that is not fiber but copper. If the German state does not intervene here, or the practices of ISPs and whoever has the power to build fiber changes, we will for th…

Is 800 euros that bad? In the US, we were quoted $10k a few years back. Even if fiber is already at the road, $800 is probably a fair price just to trench the line from the road to your home and install an entry point. If they provide free installation, then they have to make up the cost by raising your rates.

Re: We shrunk our Javascript monorepo git size

#149

Post by mb7733 »

dagw wrote: post #143
mb7733 wrote: post #142

Earlier quoted context omitted.

What is being embraced, extended and extinguished by vscode?

A lot of new and popular features in VSCode are only available in the official MS version of VSCode. Using any of the forks of VSCode thus becomes a lesser experience. Microsoft Embraced by making VSCode free and open source. Then they Extended by using their resources to make VSCode the go to open source IDE/Editor for most use cases and languages, killing much of the development momentum for none VSCode based alter…

From the wikipedia definition EEE goes like this:

> Embrace: Development of software substantially compatible with an Open Standard.

> Extend: Addition of features not supported by the Open Standard, creating interoperability problems.

>Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors who are unable to support the new extensions.

As I see it, there no open standard that Microsoft is rendering proprietary through VSCode. VSCode is their own product.

I see your point that VSCode may have stalled development of other open source editors, and has proprietary extensions... but I don't think really EEE fits. It's just competition.

Re: We shrunk our Javascript monorepo git size

#150

Post by smashedtoatoms »

develatio wrote: post #136
Cthulhu_ wrote: post #108

Earlier quoted context omitted.

Yeah, have 2500 separate Git repos with all the associated overhead.

Can’t we split the packages into logical groups and maybe have 20 or 30 monorepos of 70-100 packages? I doubt that all the devs involved in that monorepo have to deal with all the 2500 packages. And I doubt that there is a circular dependency that requires all of these packages to be managed in a single monorepo.

People act like managing lots of git repos is hard, then run into monorepo problems requiring them to fix esoteric bugs in C that have been in git for a decade, all while still arguing monorepos are easy and great and managing multiple repos is complicated and hard.

It's like hammering a nail through your hand, and then buying a different hammer with a softer handle to make it hurt less.

Post reply on HN