hanwenn

Yes. The links are to isolated threads on a rail (model) forums (apparently, this publisher markets books/magazines related to railway models).

It's hard to see if the individual complaints really support a general problem, or if this simply the only result that talks about "scam + business-name". Probably, the latter.

The same problem happens on google search, if you look "<obscure false fact>", you'll get pages mentioning that false fact. If you fall into the trap of confirmation bias, it leads you to think the false fact is in true.

Curiously, if you look for "geramond verlag betrugsmasche", or "verlagshaus24 betrugsmasche", it will now tell you that

     there are no indications it is a scam, but "significant organizational problems and extremely bad customer support lead to (list of bad experiences)". 

I got tired of the permission prompts and wrote a filesystem/network sandbox so I could skip all permission checks. It works on the same principle as bubblewrap, but has some niceties to separate Claude from its credentials. See https://github.com/hanwen/runclaude

AWS graviton, Google Axion? ARM has better performance per watt, which translates to better performance per $.

interesting article, but now I'm left wondering how the glucose gets to the retina. Why is this easier than supplying oxygen?

That is not quite the right word. For Python, the headcount was moved from the Bay Area (the most expensive place in the world to hire software engineers) to Munich (the most expensive place in Germany to hire SWEs.), for cost saving reasons.

Is anyone from GitButler reading this?

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?

blaze/bazel was a big improvement over its predecessor (a set of python scripts that generated huge makefiles), but that did not make it free of accidental engineering. The google infrastructure teams were very tightly staffed, so for a long time, it was held together with proverbial duct tape and heroism.

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.

Rob left Google a couple of years ago.

"WarpBuild are still the better option."

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.

more background: https://sourcegraph.com/blog/zoekt-creating-internal-tools-a...

IIUC, on EC2, the disk (EBS)is one service, and snapshots are in another service (S3). Taking a snapshot involves copying the entire disk to S3, while restoring a snapshot pages blocks in from S3 as the VM accesses the disk.

Also: did you consider using LVM snapshots?

Thanks for writing the blog post; it was a fascinating read!

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?

IIRC it already uses content defined chunking for finding object deltas.

Hi!

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.

don't forget Android.

Both David Chang and his staff are ridiculous.

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.

Developer infrastructure at google reported into cloud from 2013 to 2019, and we (i was there) tried to do exactly that: building products for gcp customers based on our experience with building interval developer tools. It was largely a disaster. The one product I was involved with (git hosting and code review) had to build an MVP product to attract entry level GCP customers, but also keep our service running for large existing internal customers, who were servicing billion+ users and continuously growing their load. When Thomas Kurian took over GCP, he put all the dev products on ice and moved the internal tooling group out of cloud.

Haskell is another oddball. It was for a hardware project that used the to-be-auctioned analog TV RF spectrum for a new WAN standard.

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).

Hi,

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.

github uses something called babeld (just telnet to github.com port 22; the version string is printed immediately.)

In the Bazel build system, you would mark the test data blob as testonly=1. Then the build system guarantees that the blob can only be used in tests.

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

intra EU bank transfers cost much less than 1-3%.

This story appears quite similar to the scandal at the Texas fruitcake bakery https://collinstreet.com/blog/the-sandy-jenkins-embezzlement...

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.

Does that work? The canal goes across a mountain range; you'd have to pump a lot of water uphill. It's probably cheaper to ship the goods by train instead.

See https://www.youtube.com/watch?v=bx_LGilOuE4. I think the plan is to replace to it with something based off JJ.

Not in use that I know

At the time that I started Zoekt (2016), Google's internal codesearch used suffix arrays for the string matching, which the team wasn't happy with, presumably because of the algorithmic complexity and indexing slowness. The Codesearch team was exploring alternatives, one of them the technique described in https://link.springer.com/article/10.1007/s11390-016-1618-6. The positional trigrams were a simplification of this, that they didn't mind me open sourcing.

so, in terms of algorithms, Zoekt wasn't actually inspired by Google's internal code search.

The precise query syntax of zoekt is mostly copied from google's internal syntax, though.

Russ Cox' trigram approach uses document IDs for the posting list, which makes the index much smaller, but gives less precise (ie. slower) matching. This is mentioned in the design doc at https://github.com/sourcegraph/zoekt/blob/main/doc/design.md....