levkk

Not a bad time for the secondary market to be created. We keep buying everything new, when the old stuff works just as well. There is a ton of e-waste. The enthusiast market can benefit, while the ent…

That's why courts don't take hypothetical cases. Someone has to be injured to demonstrate actual harm. Are there any examples of Oracle using their JavaScript trademark to sue anyone? If the…

Several issues: 1. Reducing dependencies is a wrong success metric. You just end up doing more work yourself, except you can't be an expert in everything, so your code is often strictly worse. 2.…

Please show me where. It only works for tabs that have a running process.

The only thing I want from WezTerm is a warning when I'm about to close a tab. The tabs are too small and the x is easy to hit by accident... thousand lines of bash history and temp env vars gone…

The Postgres query parameters one is funny. 65k parameters is not enough for you?!

Yeah, no way. As soon as you hit swap, _most_ apps are going to have a bad, bad time. This is well known, so much so that all EC2 instances in AWS disable it by default. Sure, they want to sell you mo…

Switched to email notifications and disabled them in GitHub, mainly because of this. Huge quality of life improvement.

That's awesome. With macros, you can go far and most modern web frameworks use whatever complex tools their language allows (like metaprogramming in Rails). Mad props for building this. It's…

Definitely not. Arc is for immutable (or sync, e.g. atomics, mutexes) data, while borrow checker protects against concurrent mutations. I think you meant Arc<Mutex<T>> everywhere, but that…

Sure except Wayland doesn't work with nvidia so...

Yup, same, using X, everything mostly works. Wayland - not so much.

It's good to have some guarantee that a write is atomic and won't be left in a half-written state. I think that's strictly worse even if it's only "eventually" consistent…

That can easily be perceived as violating the ToS and get you kicked off the marketplace. Big risk to take if that's where you're making most of your $.

Does that work with S3, etc.? I don't remember them allowing partial file uploads.

No. Postgres data files are 1Gb each. When you change just one byte in a table, a whole 1Gb file gets updated (just 1 byte change, effectively). Your file-based backup tool now has to upload 1Gb of da…

Gotta love these are zero-indexed. Written by an engineer for engineers.

Finally! Been looking for this a long time. File-based backups for large Pg databases are not very scalable (even incremental), having this in my toolkit would be amazing.

Competition. Go build a better product.