In my experience productivity is up and people get their work done. What I do see is a lot of extrovert getting depressed because they no longer have access to the smorgasbord of interactions at the office. Certain managers also seem worried by this move to remote, since it has become harder for them to "play the game" of office politics.

My own opinion is let the people decide what to do. Once a week, everyday, once a month, only when needed... Let people and teams decide.

>, since it has become harder for them to "play the game" of office politics

I suspect this is the real reason for a push to return to the office.

Plot twist. Posted by a Gitlab employee

Actually, I am not a GitLab employee.

I work for a company called FusionAuth. Check out my profile: https://news.ycombinator.com/user?id=mooreds which includes my LinkedIn: https://www.linkedin.com/in/mooreds/

Cheers!

nah. https://news.ycombinator.com/item?id=30003590

Negative bonding can be a fast way to feelings of camaraderie, but it can also cause resentment to fester.

Lots of issues running docker and other strange segfaults in VM.

- uBlock Origin - tabmanager.io - React Developer Tools

I'm using tabmanager.io for this purpose, i.e. syncing windows as group of tabs. But I know similar features to this extension for tab-groups are currently being added.

Browser compatibility issues can be resolved with Babel and as such fulfills the need of jQuery and allows me to just write javascript.

be careful of cycle-collection problems.

Regardless of the discussion, Electron browsers are very insecure and is not a stable foundation to build a browser on. Electron even recommend that you do not try and build a browser using it.

This. Brave famously migrated away from Electron because of the security implications of that approach.

Also, it kind of makes sense: You'd effectively be implementing a browser (or the GUI thereof) in a browser.

if the underlying language were Lisp or Smalltalk then implementing it thus might be a rational shoo-in.

I don't know. Implementing a browser in a browser can make XSS potentially bad, and I think it even lead to full on RCE in the earlier days of Brave/Electron. Still happens, I think (though to a lesser extent these days).

There's also the difference in time between committed patch and end user having a new release in the case of a critical vulnerability, for instance.

Using an embedded browser framework introduces many intermediate parties, some (many?) of which might not have being up to date with the upstream as a priority – which leads to a weakened state of security in the "browsers" downstream.

Sounds like a Big ball of Mud. If it solves a real problem then it can be re-invented; by the same people or by someone else. Otherwise it will slowly come to a crawl and eventually be forgotten.