• 0 Posts
  • 44 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle


  • Except the entire use case for teams in our organization (and I’m sure many others) is basically just to chat and make calls. None of the extra stuff is useful to us.
    Also you can look at slack which would also be a communications/collaboration platform, and weirdly enough the UX is fine and usable without training. Just admit MS shat the bed and made some Frankenstein abomination that no one knows how to use correctly. It’s pretty typical of Microsoft (and apple too) to just deflect that the user is doing it wrong instead of admitting they could improve the experience.
    To add to your RV analogy, Microsoft is selling an RV to moms and dads that just want to drop their kids to school. Sure sometimes they go on vacation and the RV is nice, but it’s not what the user needs. It’s also exactly why users hate it, they are given a monster truck just to go to the shop. (Plus in the case of software, they could have it transform as needed. The communication part could look like a regular sedan, but instead you are forced into the RV format at all times)





  • Go had the same behavior until recently. Closures captures the variable from the for loop and it was a reference to the value.
    They changed it because it’s “common” in Go to loop over something and run a goroutine that uses the variable defined in the loop. Workaround was to either shadow the variable with itself before the loop, or to pass the value as an argument.
    It’s been a long time since I wrote c# so idk if the same is expected from the avg dev, but in Go it’s really not explicit that the variable will be a reference instead of a plain value





  • From the incident report it seems the impact was limited to VMs in one DC in one region to be stopped, as the power was lost. And some service degradation in the region.
    So not that much impact. Of course resources in this DC would stop working, but the rest of the region was still working properly. If you built your infra in this region in a resilient manner, your services should not have been impacted that much



  • Wow, I didn’t know that being a Linux/open source contributor meant you don’t have to follow your country’s laws.

    It’s developed internationally but devs still reside somewhere and have to abide by the rules at that place. Linux in this case being represented by an US entity means they have to follow the gov’s sanctions. If you want more or less of those, that’s where (the government) you act.