wocram

There's something ironic with having project specific variants in a style guide.

Didn't sunny receive harsher sentencing than Holmes for extremely comparable crimes?

How does leaving a monorepo help? It implies you aren't testing dependents on every change?

These are 1 onion contracts? Outrageous!

This is not limited to non technical users. Plenty of people don't care to switch between models and just pick the latest model.

What does this say about humans?

Most people have only a handful of job experiences to think through how things work or should work, so articles like this help broaden one's perspective.

Like secret lairs, they are trying to make products that some people will adore more than products everyone will like.

PRs very frequently contain more than 1 logical change.

https://github.com/jj-vcs/jj/discussions/3549 let's you change this behavior.

I think the idea is that branches/bookmarks aren't as necessary as they are with git.

jujutsu presents the same amount of power with fewer ideas, eg. There is no staging area. It adds new features, like jj undo.

The un-learning curve is steep if you already know git very well.

https://github.com/jj-vcs/jj/discussions/3549 lets you enable automatically advancing bookmarks.

Tcgplayer is mostly a marketplace, I don't think physical presence does anything for them.

Shouldn't you be able to answer that?

Being visible is useful, this is probably better suited for an ide than a hook or a daemon.

It depends on what you're publishing to, but works with most other tools by using a bookmark for each publish target.

There are numerous other ways to publish games. Is it really rent-seeking to own and maintain the most popular game publishing platform?

Level 1 is using nix to install packages, which you can do by writing a flake like.

The arguments probably come from the fact that flakes are 'experimental', but de facto widely used.

&& is not a pointer to a pointer, it's a temporary value. There is a huge amount of cognitive overhead in normal cpp usage because over time we have found that many of the default behaviors are wrong.

This is a lot of words to say eat a plant-based/vegan diet.

Why is 90% enough?

I think jj is great, godspeed!

In git remote branches have no notion of an upstream branch either, it's a fully local construct you end up responsible for annotating.

https://github.com/jj-vcs/jj/discussions/3549 exists to simplify the tug workflow somewhat.

What is the replacement for `git branch --set-upstream-to`?

This was part of our Systems Engineering class, something like this: https://web.mit.edu/6.033/2014/wwwdocs/assignments/therac25....

Carbon is just trying to bring a rust-like edition to cpp, there's no reason for non cpp users to Carbon.

I also have very few always on segments, and many conditional segments that only show up when useful. Host shows when I'm not on the usual, user when I'm not me, and stuff like that.

I hope to not age out of trying out new tools other people like!

This and command duration if the command ran longer than 10 seconds are the most useful things to add.

Choosing which segments to show is the main the to configure. It's even one of the preset example to hide versions: https://starship.rs/presets/no-runtimes

I agree there's a lot of noise that seems to be there by default.