• 12 Posts
  • 100 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle
  • Post title is misleading as he’s not really the one causing the drama.

    it’s simply false to say he’s continuing to cause the drama and problems when all he did was ask to get his commit access back …

    No. When he realised he wasn’t immediately given access as he was asking for it he also made a post on the unmoderated reddit board with “Drama” in the title.

    He inflamed drama during what should have been an otherwise fairly dull bureaucratic process, tried to hide his earlier posts, was called out on it with a timeline, then eventually half-admitted to creating drama.

    … and tell his haters they’re being assholes

    Engaging with haters is creating more drama, which makes more disruption, which makes more haters, repeat ad infinitum.

    He just needed to ignore them and let the mods do their job, not make their job harder than it already was.

    The drama comes from people who just hate the guy and are screaming about letting him back. His response to that was then very cordial and just calling out them for being to aggressive.

    It definitely appeared cordial on his part, but the timelines of events comment showed he was cherrypicking and trying to change things after the fact. He was being deceitful and manipulative which of course made everything worse than it needed to be. He drove away more of the community.


    All he needed to do was not be disruptive himself, let the mods sort out the initial haters, and let the boring topic of a commit bit be addressed.






  • The reason I recommend it is because you can’t rely on the CLI itself. Git commands can do weirdly counter-intuitive things depending on the version and settings of your git install. A command that works for one person may not work for another. Or worse, appear to work and fail silently. Or even worse, cause a problem that you won’t find out about until later (if you can even determine the root cause at all).

    That’s why I recommended Fork.

    Also, it’s not $60, it essentially has an unlimited evaluation period (a la sublime text) so you can try it out for free for as long as you want, and pay if you want too (I have).

    The linux port is in progress.

    EDIT: just a sidenote, if you really want to force youself to go CLI only, you’ll want to look into how git behaves differently depending on config. I recommend starting with this talk at NDC to get a good enough git config, then move onto Julia Evans blog as she’s currently going on a public journey of untangling how the same commands can do different things in modern git.













  • The windows 11 teams runs better, but if you’re using a school or work account, you need to use the old AngularJS+Electron version, or the new React+Webview2 version.

    So for the time being, the Windows 11 teams is more catered for personal use only. It’s kind of like a modern reboot of Microsoft’s old MSN Messenger. It was included in Windows 11 (rebranded as “Chat”) but it’s been unbundled from Windows 11 installs and I think rebranded again. But not having the school/work account support means not a lot of people use it.

    The transition between the AngularJS+Electron version and the React+Webview2 versions is happening now. At some point soon, anyone who is running an OS too old to run the new teams will be forced to use the browser version.

    So after their transition, we’ll have to wait and see if they add the school/work account support to the native version because everyone using teams right now only uses those accounts.


  • There’s a reason Teams is/was shit.

    The first teams was written in AngularJS (which is a slow to run resource hog, but fast to develop) wrapped in Electron. It was kind of a minimum viable product, just to build something quickly to get some feedback and stats on what people needed.

    The plan was to build a new native version of teams and build it into the next windows while having an web fallback (built on react) for everyone else.

    They stopped working on the original teams and started working on the new versions.

    They got half-way through working on the native and react versions when suddenly, covid happened.

    They couldn’t keep working on the new versions because they wouldn’t be ready for a while, so they had to go back and resume development on the old one, introducing patch after patch to quickly get more features in there (like more than 2 webcam streams per call).

    Eventually covid subsided and they were able to resume development on the new teams versions.

    Windows 11 launched with a native teams version (which has less features but runs super quick), and the new react based teams (which can now be downloaded in a webview2 wrapper) has been in open beta since late last year (if you’ve seen the “Try the new Teams” toggle, then you’ve seen this). The React+Webview2 teams will replace the AngularJS+Electron version as the default on July 7th.