arccy

depending on the org, maybe closer to $100,000 https://www.dotfurry.org/#why-furry

Google Registry / Charleston Road Registry Inc. operates the .dev TLD

What they sold to squarespace was Google Domains, the user facing registrar from which you can buy domains from most TLDs. It doesn't get any special treatment wrt to .dev

https://www.youtube.com/watch?v=HTIltI0NuNg

I think it's less that protobuf is a moving target, and more that gogo tried to add in all the features that google didn't want to maintain, and learned that maintaining a massive feature matrix was impossible.

not everyone has the time to trawl through thousands of bands to find music they like

it is documented by saying it calls ReadFrom or WriteTo

they should make a .cve tld to make keeping track of these easier.

auto add is nice for universal undo for changes made outside your editor...

instead of adding changes to a new commit, i split/squash them into the previous one so the current commit remains dirty

i too work with worktrees (jj workspaces) and prs (requires branches). it's easier if you give up choosing the name of your branch, and instead rely on finding things by description or your workspace name.

for prs, I usually start with a single commit, so `jj git push -c` will auto create a named branch based on the change id. And i have template like the following to push to the same branch if i decided to stack commits rather than rewrite:

    branch-push   = ["util", "exec", "--", "sh", "-c", """
    name="$(jj log --no-graph --no-pager --color=never -r 'fork_point(@ | trunk())+ & fork_point(@ | trunk())..@' -T '"push-" ++ change_id.short()')"
    jj bookmark set -r @- "${name}"
    jj git push -b "${name}"
    """]

and descriptions are slightly nicer than branch names, since they can be longer.

perhaps the oncall is better if you write your own services, but as an SRE / ops person who has to run other people's services, rust ones just generally seem to be worse: logs that are so verbose but seem to tell you nothing, statsd seems to be the only choice for metrics, contextless errors everywhere, memory "leaks" (more like runaway memory use) that the developers swear are impossible because it's rust, overall just less mature across services written by both in house and oss teams

nobody should support MicroSlop

most countries actually let you apply for permanent residency once you've hit a set number of years, usually around 5 or 10, on work visas

you only run them for your own project, not the generate directives of your dependencies though

probably Google Doc Apps Script, those create so many Google cloud projects

the problem is these "creators" want to get paid by generic advertisers, so they have to conform to the clean standard.

if they just wanted to express themselves, they could.

still use new, and then squash your changes in. that way you can actually see what changes you made

The only reasonable way to use signing in jj is with the sign-on-push config https://docs.jj-vcs.dev/latest/config/#automatically-signing... rather than as commits are made

from part 2:

Worse, early prototypes already pulled in nearly a thousand third-party Rust crates, many of which were transitive dependencies and largely unvetted, posing potential supply-chain risks.

Rust really going for the node ecosystem's crown in package number bloat

how you type is also part of the signal

Sony actually listened and made the cups foldable again though

Or: your buggy code is no longer buggy.

Sounds just like a "helpless" dev that shifts blame to anyone but themselves.

with neovim as the pager for man, it does find ~?

though you have to be aware of the escapes for regex, so \~?

maybe the OP is trying but failing to drum up support for his unergonomic api proposal

you could also stick this in ssh config, generally makes terminals work with ancient systems...:

    SetEnv TERM=xterm-256color

but think of all your battery life gains

not really, they paid import duty

If you don't want to bother with directories or want to use https instead of ssh, you can do remote url based dispatch in your gitconfig:

    [credential "https://github.com/org1"]
      useHttpPath = true
      helper =
      helper = /path/to/auth.sh user1
    [includeIf "hasconfig:remote.*.url:https//github.com/org1/**"]
      path = user1.gitconfig
      ; set name / email in user1.gitconfig

    #!/bin/bash
    echo "username=$1"
    echo "password=$(gh auth token --user $1)"

if you're using gerrit then you have the Change-Id trailer you can match against?

Note that you can delegate the _acme-challenge subdomain to a validation-specific server or zone, so a different server that supports automation if you can't / don't want to change your main DNS provider.

https://letsencrypt.org/docs/challenge-types/#:~:text=This%2...

They even have the gall to call it an improved UI for reviewing large pull requests. They must have let UI designers who've never written code before design it.