matthewisabel

Yes agreed it's been a huge problem, and we shipped changes last week to address some of the gnarly p99 interactions. It doesn't fix everything and large PRs have a lot of room to be faster. It's still good to know where some worst performance issues are to see if there's anything particularly problematic or if a future change will help.

Hey from the GitHub team. Outages like this are incredibly painful and we'll share a post-mortem once our investigation is complete.

It stings to have this happen as we're putting a lot of effort specifically into the core product, growing teams like Actions and increasing performance-focused initiatives on key areas like pull requests where we're already making solid progress[1]. Would love if you would reach out to me in DM around the perf issues you mentioned with diffs.

There's a lot of architecture, scaling, and performance work that we're prioritizing as we work to meet the growing code demand.

We're still investigating today's outage and we'll share a write up on our status page, and in our February Availability Report, with details on root cause and steps we're taking to mitigate moving forward.

[1] https://x.com/matthewisabel/status/2019811220598280410

We'll ship some initial changes here next week to provide maintainers the ability to configure PR access as discussed above.

After that ships we'll continue doing a lot of rapid exploration given there's still a lot of ways to improve here. We also just shipped some issues related features here like comment pinning and +1 comment steering [1] to help cut through some noise.

Interested though to see what else emerges like this in the community, I expect we'll see continued experimentation and that's good for OSS.

[1] https://github.blog/changelog/2026-02-05-pinned-comments-on-...

Hey I'm on the team at Retool and this is a place we're spending a lot of time right now. We're still working through the challenge of showing the depth of the IDE while balancing the goal of a lot of new users to maybe just get an admin panel or support dashboard that connects to their existing db or salesforce.

I'd love to hear from you (or anyone else reading this) on how your getting started experience went, particularly if you found yourself wanting to just eject into writing a script or app elsewhere. I love to pair on apps whether it's moving existing code into Retool or starting fresh to see the hurdles. My email is my HN username @retool.com

BTW just sent a twitter DM, thanks again for the feedback.

Hey I'm a Codespaces PM. It's 2 cores 4GB right now but there will be more configurations coming soon as get further along in the beta.

I work on the UX side and you can email me at firstname.lastname @ microsoft.com (it's my username and in my profile).

@thejosh I'm a PM on Azure Pipelines and I'm interested to hear the builds UI ordering and other wonkiness feedback if you want to share. You can email me at my firstname.lastname at microsoft.com and we can do whatever works from there.

Azure Pipelines PM here. Definitely hear you on the current YAML experience. We're working on updates to the editor now to allow you to quickly browse and insert task snippets. It's going to be a big improvement.

I created a visualization on a similar topic that looked at mortality rates state-by-state using the 2010 census data. It was on HN about six months ago.

http://www.matthewisabel.com/projects/deathrates/geographic....

According to the Harvard Injury Control Research Center, there is some risk, particularly when considering younger demographics.

"The preponderance of current evidence indicates that gun availability is a risk factor for youth suicide in the United States. The evidence that gun availability increases the suicide rates of adults is credible, but is currently less compelling." [1]

There's a lot of good additional data in the original report. According to the table on page 40 [2], self-harm by firearm represented 19,392 of 38,364 suicides. This dwarfed the number of gun-related homicides which was 11,078.

Page 83 explores death by intent. Interestingly, there's also a category for legal intervention/war which represented 344 of all firearm deaths.

[1] http://www.hsph.harvard.edu/hicrc/firearms-research/gun-owne...

[2] http://www.cdc.gov/nchs/data/nvsr/nvsr61/nvsr61_04.pdf

D3.js and a bit of jQuery. I really designed as I built. When I clean it up and add some other data it'll probably be a good place to use Backbone.

On page 110 of the CDC's PDF the formula for computing age-adjustment is discussed. You'll also find the original data there where you can look column-by-column and see the impact that adjustment has for various states and cases.

http://www.cdc.gov/nchs/data/nvsr/nvsr61/nvsr61_04.pdf

I didn't include DC data. It does exist if you reference the data PDF put out by the CDC.

I originally had included DC but it's a major outlier since it's almost entirely urban. It's also not a state and doesn't visualize well because of its size, so it's not in the csv I used.

It does seem like quite an outlier. I found another article that mentions it and splits it by county. http://socialcapitalreview.org/washington-tops-u-s-in-12-yea...

It looks like a problem in the western part of the state, but I don't see any suggestion of why that is.

*Correction: Meant county instead of country.

Once I get that data I'll be all over. I definitely think this data (and something more granular) is particularly fascinating when considered over time.

I would love to do some overlays to put it in the context of other data. Something more granular would of course be nice too.

Hopefully I'll find more data sets that I can plug in.

It should say influenza and pneumonia for that label. I just realized that error. That number sounds more appropriate that label. Adjusting now.

Update: Fixed.