So, it's been one year since I use Zed daily, and I didn't encounter this issue, or any other issue for instance, everything is smooth and I never encountered a failure or a crash.
I work on large (everything is relative, though) monorepos, that would probably qualify for this limit, and I remember already did the kind of "workaround" discussed in this issue years ago on this device. I think it's hard to blame the software when the default file limit is so low depending on the languages you work with.
Anyway, if you would encounter this problem, you would have already encountered it with other tools, or else this is fine.
The logical conclusion from statistics is hybrid work. I am full remote because of the distance, bust most of my company is hybrid, and my experience is exactly as described by the results of the Microsoft studies.
I go on site 3-5 days per month, and I always connect more (more than 0) with people outside my team and happens, even on work related topics which enable new interesting findings and what not.
It helps that the company where I work has a culture that make people want to go to the offices even if they are not required to do so. There are pics days when the office is full because people want to see each others, then they are free to remote work any time it is wanted/needed.
I think that works out if you are alone, if you are with other people, the waiter will probably interrupt the socialization you are doing with the people you are with, causing stress even for the waiter.
Also we should recognize that the waiter is often looked down at, it is not a very nice job, and as a human being, having a poor experience with some customers will probably pass on to other customers, etc...
I'd go as far as having a job with "wait" in the name, and having to wait, calmy and happily or else you don't get your tip, is not so far from slavery.
Having a waiter come over for ordering causes stress? The whole point of going out for drinks or food is not having to prepare it yourself and having someone else do the dishes. Depending on the venue getting waited on is a feature, not an inconvenience.
If interacting with the people facilitating that is stressful I would recommend finding a bench near a vending machine, having someone else in your party handle the interaction, or, not going out.
Is this just an issue in countries where waiters depend on tips for their income?
The food is still prepared to restaurant standard and brought out by waiters. The dishes are still done by someone else. You just skip the awkward, inefficient, and disruptive step of the waiter coming up to your table (or worse, having to flag them down) to order, order more drinks, ask for the bill, pay for the bill, etc...
Absolutely disagree with this description of the job a waiter does.
A waiter orchestrates and coordinates the experience for the diners they are looking after.
They slow down orders to stop the kitchen getting overwhelmed.
They upsell on the menu in a way that is helpful and informative.
They understand the dietary requirements of guests.
They hold complex orders in their head and drop the right plate to the right person.
They know the flow of a table and engage or back off as appropriate.
Don't undervalue a role that can make a night out magical or a simple coffee memorable.
> Most Git GUIs map fairly closely to the underlying git model.
Maybe, but most Git GUIs don't provide clear error messages. This is the case of VSCode, which my teamates keep using. When you use Git CLI you can just have the original error message and know what's wrong.
I was also burned by sourcetree some years ago where it lost part of my code while doing a merge I didn't even understand.
I am not a Git expert. But I can remember the 5 commands needed to do my job every day: `commit`, `push`, `pull`, `rebase`, `checkout`. (you can also add `add` and `status` to the list if you want)
They're straighforward, except for `checkout` which is adressed by `switch` for the main usage.
If you use it wrong, Git CLI will tell you in most of the cases, and even tell you how to do what you intented to do. Git GUIs will probably tell you something wrong happened and left you at that or try to be more intelligent than you are and do something wrong.
> Isn't that just being incredibly lazy.
-> this is what I'd answer to do those Git GUIs.
> Isn't that just being incredibly lazy.
-> this is what I'd say to people who won't write these 5 commands on a sticky note or something and keep it for a month before realizing it wasn't hard to remember once you _commit_ to it and that Git is not hard, minus exceptional problems but Git GUIs absolutely won't help you with these exceptional problems.
I work on large (everything is relative, though) monorepos, that would probably qualify for this limit, and I remember already did the kind of "workaround" discussed in this issue years ago on this device. I think it's hard to blame the software when the default file limit is so low depending on the languages you work with.
Anyway, if you would encounter this problem, you would have already encountered it with other tools, or else this is fine.