Sure, but how many people truly know this? I love knowing about people who are key contributors to the industry. I run into a lot of walls when trying to talk to 99% of my coworkers about any of them.
I feel that if you are in the target audience for this article (deep dive into the behavior and design decisions of the .net GC) then you probably know who Maoni is.
I'm just a sometime mid-level .net dev, and I immediately recognized her name.
That's fair, I usually read these .NET articles that crop up here on HN, though I don't always recognize the names, and I am easily the target audience, but I know industry architects who probably do not know who the author is offhand.
I currently somewhat wish CSharpier could also install (or modify, if we are wishing for ponies) an .editorconfig that matches its settings enough that someone with a habit of existing `dotnet format` or who hasn't yet installed CSharpier's own IDE extensions doesn't have a "bad time" or accidentally create a lot of commit churn.
Prettier was relatively easy to adopt because most styles at the time were just eslint configurations and auto-formatters were scarce before Prettier. .NET has a long history of auto-formatters and most of them speak .editorconfig, so some interop would be handy, even if the goal isn't "perfect" interop. Just enough to build a pit of success for someone's first or second PR in a project before they get to that part of the Readme that says "install this thing in VS or Rider" or actually start to pay attention to the Workspace-recommended extensions in VS Code.
I hope access to Code Review in GitHub will be available to paid users soon! It's going to be a game changer as a first level of code review before real people get involved with the PR.
We're both offering managed GitHub Actions runners - some of the differences include:
- Depot runners are hosted in AWS us-east-1, which has implications for network speed, cache speed, access to internet services, etc. (BuildJet is hosted in Europe - maybe Hetzner?)
- Also thanks to AWS: each runner has a dedicated public IP address, so you're not sharing any third-party rate limits (e.g. Docker Hub) with other users
- We have an option to deploy the runners in your own AWS account or VPC-peer with your VPC
- We're integrating Actions runners with the acceleration tech we've built for container builds, starting with distributed caching
Does anyone know of any books or resources that focus on the concept of a back-end application that allows you to stream video from A to Z in a performant way like Google Meet or Jitsi?
I find it exciting to have a tool that allows up to 100 participants at once right in the browser.
I don't think there is comprehensive information about that. We all do pretty much the same, implement the Selective Forwarding Unit (SFU) model.
The idea is the SFU will receive a number of streams for each user (usually up to 3, in low, mid and high resolutions) and then it will forward one of them to each other participant depending on things like available bandwidth, requested video size, etc.
There are a number of Open Source implementations available, in case you want to study it deeper:
Jitsi was (is?) based on WebRTC. Usual challenges about conferencing is, beyond 2 members, having n*m bandwidth is bad, and a solution is to centralize the streams.
That said, there are some images I wish I'd never seen.
If I could be sure it was only being used for good (by my definition of the word), that would make me eager to install a magical perfect opaque filter algorithm.
But it won't be perfect, and it won't only be used for what I consider to be good.
reply