As others alluded, JJ already exists and is a credible successor to Git for the client side.

Technical desides aside though: how is this supposed to make money for the investors?

Source: I was on part of the team that did the open sourcing, and had to clean lots of cruft in the code base that had accreted over 8 years.

what makes you think they won't hike the control plane price again? They can turn this knob arbitrarily to put you out of business.

I was curious about a couple of things:

* Have you considered future extensions where you can start the VM before you completed the FS copy?

* You picked XFS over ZFS and BTRFS. Any reason why XFS in particular?

* You casually mention that you wrote 'otterlink', your own hypervisor. Isn't that by itself a complicated effort worthy of a blog post? Or is it just mixing and matching existing libraries from the Rust ecosystem?

Comments URL: https://news.ycombinator.com/item?id=41721283

Points: 2

# Comments: 0

sorry for not responding to your email, I was swamped.

I looked through the sourcecode, but I can only find UI (ie. browser) code. Does this do anything beyond delivering a more functional and prettier UI on top of an existing zoekt deployment? If no, everybody would be better served if you tried to improve the UI inside Zoekt, which currently is a live demonstration of (my lack of) web app programming skills.

Have you thought of how you will achieve your further goals (eg. semantic search)? That will require server-side changes, but you currently have no Go code at all.

Different parts of the bird take different times to cook, so for food quality, cooking a bird as a whole makes no sense: either the breasts are overcooked, or the thighs are undercooked. There is just one reason, which is that cooking the animal whole makes for an arresting presentation. Then, you'd carve the animal tableside (like is done for Peking duck, see one of the other comments).

This requires having waitstaff that can carve a bird or having cooks that are presentable to the guests, and extra space in the dining room.

Clearly, David Chang is taking a shortcut already by carving the chicken in the kitchen.

It was canceled when it became clear the spectrum wasn´t going to be available. The Haskell rules then stuck around for another ~7 years before I deleted them as part of the cleanup for the Bazel release. They then promptly reemerged as one of the first language rules to be expressed in Bazel's newfangled Starlark language (then still called Skylark).

I wrote zoekt. From what I understand valtown does, I would try to use brute force first (ie. something equivalent to ripgrep). Once that starts breaking down, you could use last-updated-timestamps to reduce the brute force:

* make a trigram index using Zoekt or Hound for JS snippets older than X * do brute force on snippets newer than X * advance X as you're indexing newer data.

If the snippets are small, you can probably use a (trigram => snippets) index for space savings relative to a (trigram => offset) index.

This incident shows that killing the autoconf goop is long overdue.

In both cases there was a single person that both managed the books and executed transactions. They gained enough trust of their peers so nobody second guessed their lavish lifestyle.