I love NixOS and nix-darwing too. Specially now that I can use it without having to learn a bunch of stuff before even getting started. My coding agent is great at it.
I experience the same. When I try to have a rational dialog about trade offs, there’s nothing there. Or the “only runs in Windows” classic 10+ years outdated stuff
I’ve been writing C# on a Mac deploying on Linux for a decade.
Avoiding allocations when a transaction isn’t sampled should be pretty trivial. Only gotcha is that you’d still trace id propagation to tie errors together regardless of transactions. But tracing and transactions got decoupled a while ago so shouldn’t be a big problem.
I’ll leave a comment on ticket pointing to this post
C# is still my favorite language and I haven't used Windows since 2017.
JetBrains Rider is my IDE of choice on a Mac. It was pretty rough during the early releases of it, but for years now it's working well enough.
Also .NET Core 1.0, 1.1 and 2.0 was a ride. project.json anyone?
Fastforward to .NET 5, 6, 7, 8.. it's just doing great x-plat life and innovation
The fork exists as a ‘buffer’ to get some changes (features or bug fixes) out without the need to couple with the npm release of rrweb itself. Sentry engineers have several PRs in upstream rrweb merged and the goal is to increase the upstream contributions and close the gap between our fork and upstream. We’re currently porting our changes from v1 to the v2 branch.
I believe Sentry has made financial contributions to rrweb but directly to a maintainer. I'll let others who know details to comment on this. I'm sure more contributions will be done, as this is very much in the interest of Sentry anyway.
Worth noting, Sentry has been making larger contributions to OSS every year, as the company grows:
Thanks for clarifying, no need to provide specifics - those blog posts demonstrate that that Sentry is indeed committed to giving back to FOSS. Apologies for my initial cynicism.
In addition to the network call data we already attached, that does go through data PII scrubbing on the edges as you mentioned, we're discussing capturing request/response body. We even talked about it today: https://github.com/getsentry/sentry-javascript/issues/7103
Avoiding any PII from getting into the system is always top of mind. And we're considering this as an opt-in regardless of scrubbing on the edge ingestion service.
Hi! I'm one of the authors and wanted to introduce NuGetTrends.
This is a website with historical total download count for NuGet packages on nuget.org.
There's data since 2013 but the UI so far has predefined filter for as far back as 2 years and result is grouped by week. Query string takes months as an integer though so URL hack to have some fun.
The NuGetTrends workers go through the nuget.org's catalog API so all the package's metadata are available in its database. That means there's the potential to build some new cool stats like:
- How many packages are signed.
- Are the DLLs in the packages strong named.
- Packages with unoptimized DLLs.
- Stats package adoption of source link.
- TFM adoption
reply