Readit Newsjj undo is great but it's a one time thing. You can't do jj this, jj that, jj other, jj undo, jj undo, jj undo AFIACT. You have to look into the op log and jj op restore for that. It's nice you can get back to where you were though.
The biggest issue for me is it requires active change management (or feels like it). In git I do `git checkout foo` then I start editing. If I want to see what may changes are since foo then `git diff` tells me. With jj though, `jj edit foo` is the to git, state of the repo ALL changes to foo. So any new edits are invisible. So, instead of `jj edit` I have to do `jj edit` `jj new`, then later squash those into foo
I know there are similar cases in git but I guess I'm just used to git so I wasn't using those cases.
that said, I'm mostly enjoying jj. Though quite often i get a conflict I don't understand. Today I got 2 and it told me choose A or B. I did `jj diff -r A -r B` and it said no diffs. If no diffs aren't there no conflicts? I'm sure someone gets it but it was annoying to just have to pick one to abandon
> jj undo is great but it's a one time thing.
For what it's worth, this changed in v0.33.0:
> jj undo is now sequential: invoking it multiple times in sequence repeatedly undoes actions in the operation log.
(release notes: https://github.com/jj-vcs/jj/releases/tag/v0.33.0)
mkeeter commented on Creating a VGA Signal in Hubris lasernoises.com/blog/hubr... · Posted by u/lasernoises
There's probably a well documented backstory on why Oxide choose stm32xx nucleo. I'm guessing VGA signals were not a top priority for hubris
(I work at Oxide, though I wasn't around for the initial chip selection process)
It's at least partially a matter of timing: Oxide was picking its initial hardware in roughly 2020, and the RP2040 wasn't released until 2021.
A handful of people have done ports, e.g. https://github.com/oxidecomputer/hubris/pull/2210, but I expect to stick with STM32s for the foreseeable future – we've got a lot to do, and they're working well enough!
I don't get it. They're a hardware integrator with a secret sauce management layer on top. I like anything on-prem but this seems a bit hyped. Slick website and appears to have a very good team though.
The server and switch hardware is designed in-house (from the PCBs on up), though we do source DRAM / SSDs / CPUs / ASICs from the usual vendors.
The "secret sauce management layer" is available at https://github.com/oxidecomputer/omicron, released under the MPLv2 license.
(I work at Oxide)
I would really love to run their control plane in my homelab.
I'm not aware of folks outside the company running the whole control plane, but people have definitely gotten parts of the system running at home:
https://artemis.sh/2022/03/14/propolis-oxide-at-home-pt1.htm...
(The author of this blog post now works for Oxide!)
Is there any reason to believe this isn’t an AI-assisted crank publication?