It's interesting that LLMs emotionally saved them, allowing them to bounce back from a destructive to a constructive mindset.
Reading another post of theirs, they seem to really love AI. Albeit in that post, it feels to me like they took AI responses too literally, with too much meaning (as if sentient, or ignoring potential training bias, etc).
However, we believe that by concentrating our resources, we can provide users with more professional, stable, and comprehensive commercial-grade services and support."
I found this formulation a bit funny. When you suddenly have to pay, it becomes “commercial-grade” by definition.
When you add a dot after the number it becomes a numbered lists and you don't have use a paragraph for each line.
Alternatively, you can use a backslash (\) or two spaces () at the end of a line to use a line-break so you can but one line after the other instead of requiring paragraphs.
Discuss with your team management how to handle this.
Guard and test against breakage of the interfacing (it's an investment, but necessary without other solutions)
Define requirements and actions you can stand by and reject for and and revert by
Whether they want to tackle it on their management level (talking to the other teams or up etc); agree on timelines, requirements, milestones, and failure conditions regarding this
For this discussion collecting the impacts, in terms of labor cost, labor motivation, short and long term cost, repeated helping-out cost to your teams tasks, etc can underline significance.
Funny how three comments that follow, by other people, do not get such a comment by the bot.
It also seems like the comment addresses a commenter, not the PR creator, so saying "you may resubmit after fixing" makes no sense. Post the comment again?
Forgejo will now transform fediverse handles (ex. @forgejo@floss.social and !forgejo@programming.dev) into links to https://fedirect.toolforge.org/, a website hosted by Wikimedia, to redirect fediverse handles to their respective URLs via Webfinger. Forgejo is working on implementing proper federated mentions that will also notify users on other federated services, which the redirection does not do.
Vulkan is a newer API standard. It is newer and was designed with a lot of new hardware and hardware capabilities in mind, and significantly reduced what the job of the API is supposed to do compared to OpenGL. Essentially giving API users many more opportunities to control graphics pipeline behavior for better efficiency and performance. Libraries and frameworks exist that provide more convenience and prepared setup or opinionated usage patterns on top of Vulkan.
DirectX had a similar shift with DirectX version 12, which also implemented closer-to-hardware APIs similar to Vulkan vs OpenGL.
/edit: Noteworthy are also OpenGL and Vulkan extensions. They extend the core API with additional APIs. An app can check if they are supported, and if the driver supports it, can use them.
I value choosing between two styles by feel for improving readability and conciseness.
For example, allowing one-liner early-returns if they are concise enough. If they are not, they must be multi-line with a block with curly braces. There's no linter rule that defines what "simple enough" is, and most linters don't do rules with condition either.
If they never deleted any data of close accounts, wouldn't that be a lot of wasted storage space? Wouldn't it be way too much data?