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

161–170 of 226 posts

Re: We shrunk our Javascript monorepo git size

#161

Post by o11c »

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.

My knowledge is a bit outdated, but we used to say:

* in America, peering between ISPs is great, but the last-mile connection is terrible

* In Europe, the last-mile connection is great, but peering between the ISPs is terrible (ISPs are at war with each other). Often you could massively improve performance by renting a VPS in the correct city and routing your traffic manually.

Re: We shrunk our Javascript monorepo git size

#162

Post by tazjin »

sshine wrote: post #145
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.

houndfooding?

Re: We shrunk our Javascript monorepo git size

#163

Post by [deleted] »

dijit wrote: post #160
acdha wrote: post #158

Earlier quoted context omitted.

I note the conspicuous lack of examples, and it’s irrelevant in this case where they are working to get the changes merged upstream exactly the way, say, Red Hat might have something they work on for a while before it merges upstream. VS Code is the most common example people have, but it’s not the same: that’s always been their project so while I don’t love how some things like Pylance are not open it’s not like tho…

Ok, examples: * SMTP * Kerberos (there was a time you could use KRB4 with Windows because AD is just krb4 with extensions: now you have to use AD). * HTML (activex etc) * CALDAV // CARDDAV * Javas portability breakage * MSN and AOL compatibility. “oh, but its not the same ”. It never is, which is why I didnt want to give examples and preferred you speak to someone who knows the history more than a tiny internet comme…

[deleted]

Re: We shrunk our Javascript monorepo git size

#164

Post by haolez »

PoignardAzur wrote: post #90
clktmr wrote: post #76

Earlier quoted context omitted.

[flagged]

Oh for crying out loud. "EEE" isn't a magic incantation, it's the name of an actual policy with actual tangible steps that their executives were implementing back when the CEO thought open source was the greatest threat to their business model. Microsoft contributing to a project doesn't automatically make it EEE. For one thing, EEE was about adopting open standards in proprietary software. Microsoft during EEE didn'…

Well, most of their extensions to VSCode are proprietary. When their dominance in software development becomes irreversible, it's obvious that they will close things down and create new sources of income. The incentives are clear.

Re: We shrunk our Javascript monorepo git size

#165

Post by madeofpalk »

haolez wrote: post #164
PoignardAzur wrote: post #90

Earlier quoted context omitted.

Oh for crying out loud. "EEE" isn't a magic incantation, it's the name of an actual policy with actual tangible steps that their executives were implementing back when the CEO thought open source was the greatest threat to their business model. Microsoft contributing to a project doesn't automatically make it EEE. For one thing, EEE was about adopting open standards in proprietary software. Microsoft during EEE didn'…

Well, most of their extensions to VSCode are proprietary. When their dominance in software development becomes irreversible, it's obvious that they will close things down and create new sources of income. The incentives are clear.

What has VS Code got to do with any of this?

Re: We shrunk our Javascript monorepo git size

#167

Post by sroussey »

acdha wrote: post #146
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.

Or high packet loss.

Every once in a while, my router used to go crazy with seemingly packet loss (I think a memory issue).

Normal websites would become super slow for any pc or phone in the house.

But git… git would fail to clone anything not really small.

My fix was to unplug the modem and router and plug back in. :)

It took a long time to discover the router was reporting packet loss, and that the slowness the browsers were experiencing has to do with some retries, and that git just crapped out.

Eventually when git started misbehaving I restarted the router to fix.

And now I have a new router. :)

Re: We shrunk our Javascript monorepo git size

#168

Post by neonsunset »

opticfluorine wrote: post #151
dagw wrote: post #143

Earlier quoted context omitted.

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…

To add to this, there are also official Microsoft extensions to VSCode which add absurdly useful capabilities behind subtle paywalls. For example, the C# extension is actually governed by the Visual Studio license terms and requires a paid VS subscription if your organization does not qualify for Visual Studio Community Edition. I'm not totally sold on embrace-extemd-extinguish here, but learning about this case was…

C# extension is MIT, even though vsdbg it ships with is closed-source. There's a fork that replaces it with netcoredbg which is open.

C# DevKit is however based on VS license. It builds on top of base C# extension, the core features like debugger, language server, auto-complete and auto-fixers integration, etc. are in the base extension.

Re: We shrunk our Javascript monorepo git size

#169

Post by wbl »

dijit wrote: post #160
acdha wrote: post #158

Earlier quoted context omitted.

I note the conspicuous lack of examples, and it’s irrelevant in this case where they are working to get the changes merged upstream exactly the way, say, Red Hat might have something they work on for a while before it merges upstream. VS Code is the most common example people have, but it’s not the same: that’s always been their project so while I don’t love how some things like Pylance are not open it’s not like tho…

Ok, examples: * SMTP * Kerberos (there was a time you could use KRB4 with Windows because AD is just krb4 with extensions: now you have to use AD). * HTML (activex etc) * CALDAV // CARDDAV * Javas portability breakage * MSN and AOL compatibility. “oh, but its not the same ”. It never is, which is why I didnt want to give examples and preferred you speak to someone who knows the history more than a tiny internet comme…

You understand in these cases the issue was not contributing back right?

Re: We shrunk our Javascript monorepo git size

#170

Post by wbl »

coliveira wrote: post #125
throwuxiytayq wrote: post #89

Earlier quoted context omitted.

Can you elaborate how exactly git is at risk here? These posts never do.

They will extend git so that it works extremely well with their proprietary products, and just average with other tools and operating systems. That's always the goal for MS.

You know who the maintainer of Git is right?
Post reply on HN