Did anybody else shudder at "Shrunked"?
Shrunken, shrunked ain't no language I ever heard of.
[deleted]
We shrunk our Javascript monorepo git size
121–130 of 226 posts
Re: We shrunk our Javascript monorepo git size
#122Earlier quoted context omitted.
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!
We use MS Teams at my company. The Word and Excel in the Windows Teams app are so buggy that I can almost never successfully open a file. It just times out and eventually shows a "please try again later" message nearly every time. I've uninstalled and reinstalled the Teams app four or five times trying to fix this. We've totally given up any kind of collaborative document editing because it's too frustrating, or we u…
This is specific to your company’s configuration - likely something related to EDR or firewall policies.
Re: We shrunk our Javascript monorepo git size
#123Earlier quoted context omitted.
[flagged]
Why? You do realize their fork is open source? The fix described in this post have been submitted as a patch to the official Git project. The fix is improving a legitimate inefficiency in Git, and does nothing towards "embracing", "extending", or "extinguishing" anything.
you are in the early extend phase.
it will look good, until the extensions get more and more proprietary- but absurdly useful.
Re: We shrunk our Javascript monorepo git size
#124Earlier quoted context omitted.
We use MS Teams at my company. The Word and Excel in the Windows Teams app are so buggy that I can almost never successfully open a file. It just times out and eventually shows a "please try again later" message nearly every time. I've uninstalled and reinstalled the Teams app four or five times trying to fix this. We've totally given up any kind of collaborative document editing because it's too frustrating, or we u…
This is specific to your company’s configuration - likely something related to EDR or firewall policies.
Really it's anyone using teams on older or cheaper hardware.
Re: We shrunk our Javascript monorepo git size
#125Earlier quoted context omitted.
[flagged]
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.
Re: We shrunk our Javascript monorepo git size
#126Earlier quoted context omitted.
Why? You do realize their fork is open source? The fix described in this post have been submitted as a patch to the official Git project. The fix is improving a legitimate inefficiency in Git, and does nothing towards "embracing", "extending", or "extinguishing" anything.
you are in the early extend phase. it will look good, until the extensions get more and more proprietary- but absurdly useful.
The extend phase starts when they make extensions which only work in their proprietary version. Putting extensive work into contributing them back is not the same.
Re: We shrunk our Javascript monorepo git size
#127Earlier quoted context omitted.
you are in the early extend phase. it will look good, until the extensions get more and more proprietary- but absurdly useful.
The extend phase starts when they make extensions which only work in their proprietary version. Putting extensive work into contributing them back is not the same.
Ok. There are a dozen examples of exactly this behaviour, and exactly this argumentation in response over the years.
Right now the most important thing for them is for people to start thinking the microsoft fork is the superior one, even if things are “backported”.
Re: We shrunk our Javascript monorepo git size
#128Earlier quoted context omitted.
This is specific to your company’s configuration - likely something related to EDR or firewall policies.
Really it's anyone using teams on older or cheaper hardware.
So you’ve tested this with clean installs on unfiltered networks? Just how old is your hardware? It works well on, say, the devices they issue students here so I’m guessing it’d have to be extremely old.
Re: We shrunk our Javascript monorepo git size
#129> 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.
Teams is the running version of that repository... It is hard for them even to store on git.
Re: We shrunk our Javascript monorepo git size
#130Earlier quoted context omitted.
The extend phase starts when they make extensions which only work in their proprietary version. Putting extensive work into contributing them back is not the same.
Ok. There are a dozen examples of exactly this behaviour, and exactly this argumentation in response over the years. Right now the most important thing for them is for people to start thinking the microsoft fork is the superior one, even if things are “backported”.
Which examples?