jmiserez

Joined 10 years ago

Karma
1,416
Submissions
702
Member since
Jan 20
Software engineer by day. I’m subscribed to hnreplies.com (no affiliation), so I’ll get an email if you reply to one of my comments.
View on Hacker News

Recent submissions

Comment · 3 years ago
Comment · 3 years ago
Give hstr a try: https://github.com/dvorka/hstr

It's saved me countless hours over the years as it's just so much better than regular CTRL-R. I also find it to work better than fzf.

Comment · 3 years ago
No that's not the same thing, in fact that'll just do a git rebase, changing the commit itself and all commits after that one. Pretty much the polar opposite of what you want!

IntelliJ products try to provide a common interface and common naming for all "VCS" operations, whether it's Git/Mercurial/etc. In practice this obscures the actual Git operations though and requires learning yet another set of "abstract" IntelliJ-specific names for the same thing. I wish they'd stop doing that, it's really confusing and inaccurate.

Comment · 3 years ago
Comment · 4 years ago
I don't often hack my own tools either, but it's great to have the possibility to do so.

When you really need that bug fixed for your edge case or platform, it's much easier to submit a patch rather than wait around for someone else to fix it.

Comment · 4 years ago
Ventura even drops support for the 2016 (Touchbar) Macbook Pros which is frustrating. The machines are certainly powerful enough. But support for Intel Macs will probably be dropped sooner rather than later.
Comment · 4 years ago
Usually the whole row is copied, updated, and then appended to a different file on disk. After some time a job runs that removes the unused rows by deleting them for good, thus rewriting files and compacting the database. This has lots of advantages, on a small scale resilience against power outages (journaling), and on a large scale you can e.g sync a second DB / backup by just streaming appends.

Simplifiying a lot here of course. E.g if your DB uses MVCC (multiversion concurrency control) old values cannot be removed until the last transaction is done seeing them.

Of course if you write your own storage engine you can do whatever you want. I wrote one for MariaDB a few years ago and you basically just have to implement the minimally required interfaces for it to work.

DBs traditionally have these technical details figured out pretty well, and the line between what is part of the DB and what is done by the OS can be blurry at times.

Comment · 4 years ago
The version with MX Silent switches is considerably quieter than the standard MX Red version. I'm hoping the Kinesis 360 coming out this year will be even quieter.
Comment · 4 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton