Unlike Steam keys, there are no ways to distribute Playstation keys outside of Playstation platform. By removing retailers and second hand markets, what exactly would make Sony or any other publishers to continue offering any deep discounts on their products on a closed platform, especially when their biggest competitor Xbox has dropped the ball heavily.
Homebrew 6.0.0 seems to be the first major version of brew that is heavily written using AI. There’s new document at https://docs.brew.sh/Responsible-AI-Usage that was added 11 hours ago. Do you think that these guidelines have been followed consistently since 5.0.0?
With it’s current AI setup GitLab still couldn’t make anything that could be called great in UX so I can’t wait to see what they can do by eliminating the remaining human factor. Can’t personally wait seeing tickets like these [0] open for months with bots telling you that everything will be alright.
The Wallet Pass[0] and PassKit[1] documentations are some of the sparsest and cryptic documentations around filled with absolutely archaic flows that _need_ to be supported for proper integration. If this solves the need of ever having to deal with those features ever again.
Luckily we have had the perfect paradigm for this kind of mindset for decades: proprietary software. The spirit of open source is already essentially dead due to it being co-opted by companies and individuals working only for their own gain, and for it to rise again we probably need a total reset.
Fugazi released almost 900 shows on CD in the early 2000’s, costing 5 bucks a piece. Some of them are available on their Bandcamp page these days too https://fugazi.bandcamp.com/.
> This does not mean that Slack’s engineering investment was wasted, because Slack also built enterprise sales infrastructure, compliance capabilities, data security practices, and organizational resilience that a fourteen-day prototype does not include.
The LLM-agent team argument also misses the core point that the engineering investment (which actually encompasses business decisions, design and much more than just programming) is what actually got Slack (or any other software product) to the point where is it is now and where it's going in the future and creating a snapshot of the current status is, while maybe not absolutely trivial, still just a tiny fraction of the progress made over the years.
Kino Regina, the movie theater mentioned, is owned and operated by the Finnish Arts and Culture Agency and does not only show classics, but also a lot of contemporary movies of note, right up until recent releases. It has modern hi-grade digifilm equipment but is also equiped to show film from eg. 70mm and cinemascope formats. They also host concerts and seminars.
Personally I’d like to thank you for raising the point, it seems that tsc members are willing to ram the PR through regardless as per jasnell’s LLM analysis that honestly seems like a hostile gish galloping attempt than an actual honest analysis.
I guarantee you that I would endlessly rather read your streams of thought about amateur boat building than read another AI-generated Hacker News comment ever again. Don't sell yourself short.
Every other minute some bots is creating an issue that a bot is trying to solve via a pull request which is reviewed by multiple bots. Future is now, good luck and have fun.
That’s the conclusion you get when you sit in the board of 20 companies where all the CEOs are telling you the same thing but you don’t understand that you are all just selling the same golden shovel to each other. Obviously this can also be backed by their own experiences too: 100% of code is written by AI, because last time they actually wrote code was in 2010.
I agree with the general statement, if you didn’t spend time on writing it, I am not going to spend time reading it. That includes situations where the writer decides to strip all personality by letting AI format the end product. There’s irony in not wanting to read AI content, but still using it for code and especially documentation though, where the same principle should apply.
GitHub has had customer visible incidents large enough to warrant status page updates almost every day this year (https://www.githubstatus.com/history).
This should not be normal for any service, even at GitHub's size. There's a joke that your workday usually stops around 4pm, because that's when GitHub Actions goes down every day.
I wish someone inside the house cared to comment why the services barely stay up and what kinds of actions are they planning to do to fix this issue that's been going on years, but has definitely accelerated in the past year or so.