7,824 karma · joined January 2, 2013
Also, not to be an apologist, but I trust you realize that "the way they handle US sanctions by blocking everybody from entire countries" is how US companies are required by law to act. Not all do act that way, of course, but almost any that have enough overseas customers to matter do, because they have enough overseas customers to need to be aware of those laws.
If the motivation for moving off GitHub was "GH is down too much", it might be worth tracking how many 9's of uptime is lost in the self-hosted case.
It's reasonable to expect stories the real local press finds discussion worthy (because they are both false and relevant to the local press) are an effective way of using the local press to throw more link strength at their own site.
Yeah, that explains a lot.
Or it could be that GitHub saw a 14x increase in commit volume last year[0], and we've concomitantly seen its reliability fall of a cliff in the last year or so. Given that Microsoft is leasing additional space on AWS(!)[1] to handle the additional commit volume, my personal money is on commit volume growth being a bigger issue than internal use of AI.
Internal use of AI may have been an issue. Commit volume growth may have been an issue. Unless one has direct knowledge of their infrastructure issues, claiming to know is quite literally making exactly the "they are vegan, their illness must be caused by their veganism" argument the GP commenter was talking about.
[0]https://daringfireball.net/linked/2026/05/04/commits-on-gith...
[1]https://www.businessinsider.com/microsoft-github-amazon-ai-c...
Coca-Cola has a much larger market cap than Disney, and the Coca-Cola brand is very intentionally a nostalgia-driven, golden age, remember the good times brand.
It's great that you have the data. I'm sure that took a lot of time to obtain. Spending a few more percent of your total time making the presentation of the data intuitive to others is almost certainly the highest ROI thing you can do at this point, if you want your site to be useful enough to get enough visitors to pay for the cost of acquiring the data.
Feel free to tell me that red is the lowest Pareto value and that's why you made the frontier red, or whatever. I'll still respond that the details of the presentation matters enormously to adoption, and the current presentation is very far from optimally intuitive to those of us who didn't personally develop the data.
What is yellow? What is green? What is blue? Are they relative to their CPU column? Relative to the pricing row? Absolute?
Agreed. I wish CF had something like Azure's new fast-starting Express containers.
Companies used to go from garage to IPO rapidly. Now a decade from founding to IPO is not uncommon. Unless the employee plans on committing their life to the startup that just hired them, they will most likely move on somewhere else before that decade-later liquidity event happens.
When they leave, they have to spend after-tax $ to buy non-liquid shares of a still-high-volitility pre-IPO company, because almost all options have a 90 day exercise clause. If they were early enough that their shares are 409a valued at pre-seed valuation, that might make sense. If they are a significant employee, the kind of employee the company most wants to retain, and their shares are valued at Series B or C, that tends to be a very big check they'd need to write to their former employer to turn those options into non-liquid shares that may well end up at zero valuation, all at a time when they no longer have any ability to help the company succeed.
The original motivation for offering options was to encourage employees to stay, but what happens is the precise moment the company most wants those options to do their thing and retain the key employee is the moment when the employee starts doing the above calculation, realizing the company is years from IPO, it's still risky even if it looks promising, and the options are actually worth zero unless the employee either (a) stays at the company for a decade or (b) pays back a non-trivial fraction of their takehome pay to buy a risky illiquid asset. The employee realizes neither of those scenarios are likely to happen, so boom the moment when the company wants the options to drive retention ends up being the moment when the employee realizes the options are not just worthless, they could actually have a negative EV if exercised. Suddenly those options aren't very effective at retaining the employee.
There was a time when options had value like the OP suggests, because the timescales were shorter. Today, not so much. Yes, outliers happen, but in general they don't.
When the model finds a vulnerability, it also finds a fix. Anthropic only shares the vulnerability with the Open Source maintainer, not the fix. Paying customers get fixes, confirming that the model does generate fixes for the vulnerabilities.
Sharing the vulnerabilities but not the fixes does sound like a shakedown operation.
I'd love to find and remove any apps from my devices that have this SDk active.
That's a lot of budget - would have been nice if they'd made an actual donation to the project, instead of pounding the project's servers and bandwidth when there are much better ways to interact with the data.
Yes, GitHub is temporarily breaking under the increased load, yes, it's likely to still be a thing in 2 months, and no, it's unlikely to still be a thing in 12 months.
It's very unlikely a cool new thing will peel enough developers off GitHub in the next six months to survive long term as GitHub inevitably gets its ability to handle the new normal scale back.
If you provided a human contractor with the specifications for the code you want, the courts have repeatedly made clear you have not provided the creative input from a copyright perspective, and the contractor needs to explicitly assign those rights to you if want to own the copyright on the code.
> Though the offence of eavesdropping still exists at common law, there is no modern instance of a prosecution or indictment.
Thanks for posting this resource, I've often wanted to share a link to this and other entries.
[0]https://britannica11.org/article/08-0867-eavesdrip/eavesdrip...