HackerLangs
トップ新着トレンドコメント過去質問紹介求人

arccy

2,023 カルマ登録 8 年前

投稿

Anthropic's "Claude for Open Source" program still charged $200

twitter.com
9 ポイント·投稿者 arccy·4 か月前·0 コメント

コメント

arccy
·一昨日·議論
not everyone has the time to trawl through thousands of bands to find music they like
arccy
·5 日前·議論
it is documented by saying it calls ReadFrom or WriteTo
arccy
·先月·議論
they should make a .cve tld to make keeping track of these easier.
arccy
·2 か月前·議論
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
arccy
·2 か月前·議論
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}"
    """]
you could probably write a similar alias that used your workspace name as the branch name to push to.

and descriptions are slightly nicer than branch names, since they can be longer.
arccy
·2 か月前·議論
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
arccy
·2 か月前·議論
nobody should support MicroSlop
arccy
·2 か月前·議論
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
arccy
·2 か月前·議論
you only run them for your own project, not the generate directives of your dependencies though
arccy
·2 か月前·議論
probably Google Doc Apps Script, those create so many Google cloud projects
arccy
·3 か月前·議論
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.
arccy
·3 か月前·議論
still use new, and then squash your changes in. that way you can actually see what changes you made
arccy
·3 か月前·議論
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
arccy
·3 か月前·議論
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
arccy
·3 か月前·議論
how you type is also part of the signal
arccy
·4 か月前·議論
Sony actually listened and made the cups foldable again though
arccy
·4 か月前·議論
Or: your buggy code is no longer buggy.
arccy
·4 か月前·議論
Sounds just like a "helpless" dev that shifts blame to anyone but themselves.
arccy
·4 か月前·議論
with neovim as the pager for man, it does find ~?

though you have to be aware of the escapes for regex, so \~?
arccy
·4 か月前·議論
maybe the OP is trying but failing to drum up support for his unergonomic api proposal