Live data from Hacker News

We shrunk our Javascript monorepo git size

jonathancreamer.com

101–110 of 226 posts

Re: We shrunk our Javascript monorepo git size

#101
post #76
post #32

For those wondering where this new git-survey command is, it's actually not in git.git yet! The author is using microsoft's git fork, they've added this new command just this summer: https://github.com/microsoft/git/pull/667

[flagged]

No, this is cathedral vs bazaar development

Re: We shrunk our Javascript monorepo git size

#102
post #83

Earlier quoted context omitted.

Not in the UK. Still on 80Mbit VDSL here.

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 there are no full fibre options.

Re: We shrunk our Javascript monorepo git size

#104

> 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.

I was not sure what this meant either. I know personally I have downloaded and uploaded some very very large files transatlantic (e.g. syncing to cloud storage) with absolutely no issues, so not sure what they are talking about. I guess perhaps there are issues with git cloning such a large amount of data, but that is a problem with git and not the infrastructure.

FWIW every school I've seen (and I recently toured a bunch looking at them for my kids to start at) all had the internet and the kids were using iPads etc for various things.

Anecdotally my secondary school (11-18y in UK) in rural Hertfordshire was online in the 1995 region. It was via I think a 14.4 modem and there actually wasn't that much useful material for kids then to be honest. I remember looking at the "non-professional style" NASA website for instance (the current one is obviously quite fancy in comparison, but it used to be very rustic and at some obscure domain). CD-based encyclopedias we're all the rage instead around that time IIRC - Encarta et al.

Re: We shrunk our Javascript monorepo git size

#106

> 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.

Re: We shrunk our Javascript monorepo git size

#107

> We work in a very large Javascript monorepo at Microsoft we colloquially call 1JS. I used to call it office.com.. Teams is the worst offender there. Even a website with a cryptominer on it runs faster than that junk.

We were all impressed with google docs, but office.com is way more impressive. Collaborative editing between a web app, two mobile anpps and a desktop app with 30 years of backwards compatibility and it pretty much just works. No wonder that took a lot of JavaScript!

> No wonder that took a lot of JavaScript!

To the point where they quickly found the flaws in JS for large codebases and came up with Typescript. I think. It makes sense that TS came out of the office for web project.

Re: We shrunk our Javascript monorepo git size

#109
post #36

Earlier quoted context omitted.

To be fair, we were impressed with Google Docs 15 years ago. Not saying office.com isn't impressive, but Google Docs certainly isn't impressive today. My company still uses GSuite, as I don't like being in Microsoft's ecosystem and we don't need any advanced features of our office suite but Google Docs and the rest of the GSuite seem to be intentionally held back to technology of the early 2010's.

Google docs certainly haven't changed much the last 5-10 years. I wonder if that's an intentional choice, or if it is because those that built it and understand how it works are long gone to work on other things.

No more development? Time for Google to kill Google Docs!

Re: We shrunk our Javascript monorepo git size

#110
post #61

Earlier quoted context omitted.

Hey, I worked with Jonathan on 1JS a while ago (on a team, Excel). Just a note OMR (the office monorepo) is a different (and actually much larger) monorepo than 1JS (which is big on its own) To be fair I suspect a lot of the bloat in both originates from the amount of home grown tooling.

I thought Microsoft had one monorepo. Isn't that kind of the point? How many do they have?

The point of a monorepo is that all the dependencies for a suite of related products are all in a single repo, not that everything your company produces is in a single repo.
Post reply on HN