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

Points: 1

# Comments: 0

Specifically you should compare and contrast to tools like SOPS, Ansible Vault, pass, etc.

For the author's purposes, any benefit is just placebo.

There absolutely are times where /dev/shm is what you want, but it requires understanding nuances and tradeoffs (e.g. you are already thinking a lot about the memory management going on, including potentially swap).

Don't use -funroll-loops either.

I encourage anyone who gets value from this to donate to support it if they can. It is a passion project but nonetheless comes with real costs.

Another thing about the architecture is we inherently bias it with the way we structure the data. For instance, take a dataset of (car) traffic patterns. If you only track the date as a feature, you miss that some events follow not just the day-of-year pattern but also holiday patterns. You could learn this with deep learning with enough data, but if we bake it into the dataset, you can build a model on it _much_ simpler and faster.

So, architecture matters. Data/feature representation matters.

For this broader problem, there are other more complete solutions that are more robust and flexible. Personally I like dotbot (https://github.com/anishathalye/dotbot) as a balance between power and simplicity, particularly when managing files across multiple OS homedirs (e.g. linux server, macos laptop).

Absolutely no indication of improper adult behavior.

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

Points: 15

# Comments: 9

https://github.com/chipturner/pxhist

The former is easy(ish); the latter is trickier since I didn't want to provide a hosted service but there aren't easily usable APIs like s3 that are "bring your own wallet" that could be used. So I punted and made it directory based and compatible with Dropbox and similar shared storage.

Being able to quickly search history, including tricks like 'show me the last 50 commands I ran in this directory that contained `git`' has been quite useful for my own workflows, and performance is quite fine on my ~400k history across multiple machines starting around 2011. (pxhist is able to import your history file so you can maintain that continuity)

https://github.com/chipturner/pxhist

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

Points: 2

# Comments: 0

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

Points: 6

# Comments: 0

These days it generally is better to prefer Zstandard to zlib/gzip for many reasons. And if you need seekable format, consider squashfs as a reasonable choice. These stand on the shoulders of the giants of zlib and zip but do indeed stand much higher in the modern world.

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

Points: 5

# Comments: 0

Which isn’t surprising as even today there is demand for tape. The question is how long the demand will remain vaguely mainstream vs when it will become more niche. The 2028 estimate of storage being dominated by SSDs seems vaguely reasonable to me.

Pure’s bravado of staying zero hard drives will be sold after 2028 seems silly but inline with what a flash storage company would say. But from a directional standpoint it probably is right that many use cases will get further eroded by SSDs. One big challenge with hard drives is access speed (throughout and latency) compared to nvme, and hard drives being used more as cold and near line storage is definitely going to continue. Write once access never in many cases.

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

Points: 1

# Comments: 0