Half the cs world does…
What's the basis for this claim? I'm doubtful, but don't have wide data for this.
Half the cs world does…
What's the basis for this claim? I'm doubtful, but don't have wide data for this.
They're bash/shell- and bin-dependent commands rather than Git commands. I use Nushell.
Transformed to Nushell commands:
git log --format=format: --name-only --since="1 year ago" | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20git shortlog -sn --no-mergesgit shortlog -sn --no-merges --since="6 months ago"git log -i -E --grep="fix|bug|broken" --name-only --format='' | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20git log --format='%ad' --date=format:'%Y-%m' | lines | str trim | where (is-not-empty) | uniq --countgit log --oneline --since="1 year ago" | find --ignore-case --regex 'revert|hotfix|emergency|rollback'/edit: Looks like the lines have whitespace or sth. Replaced lines --skip-empty with lines | str trim | where (is-not-empty).
command aliases
def "gits most-changed-files" [] { git log --format=format: --name-only --since="1 year ago" | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20 }
def "gits who" [] { git shortlog -sn --no-merges }
def "gits who6m" [] { git shortlog -sn --no-merges --since="6 months ago" }
def "gits fixes" [] { git log -i -E --grep="fix|bug|broken" --name-only --format='' | lines | str trim | where (is-not-empty) | uniq --count | sort-by count --reverse | take 20 }
def "gits aliveness" [] { git log --format='%ad' --date=format:'%Y-%m' | lines | str trim | where (is-not-empty) | uniq --count }
def "gits firefighting" [] { git log --oneline --since="1 year ago" | find --ignore-case --regex 'revert|hotfix|emergency|rollback' }
Given the nature of Steam and previous executed data extraction, I'm scared installing and running niche/indie games now. Windows lacks
A unified GUI framework hasn't happened yet, not between OSes, nor really within each OS ecosystem. I'm not hopeful about leaps in native interoperability in that regard.
Web tech interoperability is so established and widely used, packaging and running those natively seems much more viable than any hope for supposed native long term efforts.
Not everything will be covered by web tech. But for many things, it's already viable, and exploring native integration of these web technologies is interesting.
Will they ever fix the text contrast on that website/blog? :( Bad accessibility, bad readability.
I don't find it super easy to read. Even white on white is somewhat readable, but the black tree part on the left is particularly hard to read. Certainly not scan-readable / fast, like I would be able to read normal text.

Seems you don’t know how anything on Linux
What makes you think that is what they think? They referenced other people. They didn't make any claims themselves or made any indications that they agree with those "flipping out" (who misunderstand).
I read it as the opposite. They know and criticize those who don't and flip out because of that.
Git push to Forgejo -> automated build, package, and deploy pipeline -> use secured credentials to upload via scp or ssh or sftp
Alternatives to copy-upload or upload-package and then extract via command is stuff like rsync (reduce redundant, unchanged file uploads) or a simple receiver service (for example REST endpoint that receives a package with an identifier key and secret key, that it extracts to a configured target folder).
What solutions are simplest or easiest depend on the target environment, and how much of it you control. If you host the website on Forgejo itself it's as simple as pushing the static files into the corresponding pages branch.
It falls back exactly the way I think.
This article talks about flashes, and proceeds to say fallbacks should be defined. It explains how fallbacks work, but fails to describe what actually leads to the flashes, how fallbacks get replaced, and fails to say anything about solving that flashing issue they talk about.
Defining a more similar fallback font may reduce the issue visually, which is not mentioned either, and either way is not a solution for the flashing.
Dunno why one would expect lower precedence CSS rules be integrated into more specific CSS rules without explicit "inherit". That's not how CSS works. Dunno if that's a common enough misunderstanding to warrant a "not the way you think it is" title.
There's a tool for that too - I don't have the link or name at hand though
Possibly AI company crawlers. When they came up there was a lot of bad publicity and reports of actively malicious and toxic crawling behavior, including ban evasion.
You can think about locking some url paths behind valid login sessions, or use a proof of work proxy guard.
Anubis is the popular tool for that. I've seen maybe three alternatives, one of which from Cloudflare.
See also related Codeberg ticket (Forgejo instance) https://codeberg.org/forgejo/discussions/issues/319
If you search, you can find various blog posts about these issues. Not just when Forgejo.
I assume this is from https://devblogs.microsoft.com/dotnet/ten-months-with-cca-in-dotnet-runtime/?