My guess is nothing you can see right now, since it likely takes a lot longer for any substantial external-facing changes to roll out broadly. Internally I'm sure several features have moved faster. I've noticed this at Salesforce where it certainly seems like things that would have taken a few weeks take a few days now. This doesn't translate directly to more money, just more potential to make money.
> Monthly API costs per engineer ranged from $500 to $2,000 as adoption skyrocketed across the company.
That's...not exactly a lot per engineer. It sounds like they just didn't budget correctly. Especially if the net of that work is more features that would have otherwise required hiring more engineers, which would cost a lot more than $500 to $2000 a month.
No, it's really not a lot at all, especially if you've got a mandate to maximize your AI usage, which many engineering orgs have right now. I burned $216 USD using Claude Code in March just doing some casual development on the side and certainly not as a part of any professional workplace mandate.
Claude Code is very capable of making a terminal emulator with exactly (and only) the features you want. I did that for myself and it's now my daily driver. Has a few goodies I care about but nothing much else, and I have no intention of adding features for other people: https://github.com/cartermp/term
Sure it does. Users who continually push for the right features, stress test things (under normal circumstances), demonstrate uses of the platform that could be baked in by default, etc. are all highly valuable to everyone. And the social aspect matters too, even if GitHub really isn't a "social coding" site anymore. If great people doing OSS stuff are all on various GitHub projects, that encourages more good people to do good OSS stuff.
This doesn't apply to current Github issues, where rather than a lack of the "right" new features, it's just an escalating degradation of existing services that is the complaint.
The attitude of "stay to support the product" can prevent a better replacement. When Digg torpedoed themselves back in 2012 or whenever, that exodus was a big part of Reddit growing from niche to dominant.
The only users who can push for features now are those who can somehow directly influence people working on GitHub (a small number of users) or those with massive purchasing accounts that can shake Microsoft itself to its core (governments, fortune 100 companies).
I suppose us "normals" can push by making it easy to replace GitHub with something else, so that they start risking losing it all.
> Users who continually push for the right features, stress test things (under normal circumstances), demonstrate uses of the platform that could be baked in by default, etc. are all highly valuable to everyone
That's the job of GitHub's product and engineering teams, not the users.
To add on, GitHub has made it explicitly clear that they are both not working on features to focus on their Azure adoption and many core projects are in stasis even from community contributions.
No. Products don't magically get good because people conjured up features from thin air or just copied a competitor. It is very much a two-way street, especially when the product acts as a platform that tries to support heterogeneous use cases.
Isn't it the case that OpenAI and Anthropic regularly just swap for whoever is at the top of the latest benchmarks? They're also so close in scores that it's effectively a wash anyways.
What OP is referring to is Anthropic aligning with corporate terms and conditions early, positioning themselves to be effectively resold by AWS rather than requiring orgs to procure them directly. This is huge in the enterprise world because the processes to get broad approval are generally far smaller and shorter for "just another AWS service" compared to a whole new vendor.
Isn't it an open secret that benchmarks are largly irrelevant at this point? Why else we do all have a personalized test battery for new models? That said i've stopped testing chatgpt entierly. Its still ok but is beaten by local models and it gets thrashed by non oai frontier providers. I get the history, but holding up oai outputs as equivallent is lile comparing yahoo to google post yahoo's collapse in search domains.
Oai language models are largly irrelevant at this point imo.
> Salesforce said it won’t hire more software engineers in 2025.
Some headline somewhere reported this, but Salesforce plenty of engineers (in the US at least) in 2025. One of them is a junior engineer on one of my scrum teams.
I think the best db schema I had the displeasure of working with was one where it was a requirement that every table and column name NOT have vowels, except for the few that could, and "the few that could" were governed entirely by a spreadsheet owned by the DB admin.
And so you got tables like LANDMRK and columns like RCR_RCRDR.
I work with an Oracle database like this. In the old days, there was a 30 character limit on column names, so you end up with conventions like no vowels. The limit no longer exists today, but the DBA continues to enforce the limit on new columns.
I never got an answer when I asked. This same government agency also got extremely mad when our dev manager upgraded the ASP.NET version for one project because it had some really useful features we were developing with. They deleted his permissions to deploy to production from there until the end of time, requiring us to email someone each time we wanted to update the application. It was great.
reply