Similar to black but faster, written in Rust, by the same team who created uv.

But, I agree, this is mostly a puff piece. Nothing necessarily wrong with that but not what I would have expected given the other blog posts that have shown up here on HN.

But we use 1Password for secrets and I have the need to mix and match environment profiles. So I built:

https://github.com/level12/env-config

> Potential data contamination: The SWE-bench dataset, comprising a collection of GitHub issues, has been publicly available since the end of 2023. As a result, models released after this date may have seen these exact issues or highly similar data during training. This raises the risk of inflated performance metrics and makes it harder to distinguish genuine generalization from memorization.

> AI helps Stanford scientists discover "natural Ozempic" without the usual side effects

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

Points: 4

# Comments: 1

- Project Status Update: https://github.com/indygreg/PyOxidizer/discussions/740

- https://gregoryszorc.com/blog/2024/03/17/my-shifting-open-so...

1: https://github.com/indygreg/PyOxidizer/

From that readme, it seems PyOxy has a few related uses:

- It can produce a single file executable representing a Python app including the interpreter

- It can ship self-contained Python interpreters and related to be embedded or used as a library in a larger application

- PyOxidizer can serve as a bridge between Rust and Python - "PyOxidizer can be used to easily add a Python interpreter to any Rust project. But the opposite is also true: PyOxidizer can also be used to add Rust to Python."

Edit: I once had someone apply for a job and their written communication was pretty caustic. After rejecting their application, I wrote and explained how unprofessional I found their interactions, encouraging them to step back and reconsider how their communication appears from the other side.

To my great surprise, they wrote back and said they had never had anyone give them such feedback and they agreed with my assessment of their interactions. They just had never seen it before. They thanked me for the feedback.

Such interactions are exceedingly rare. But I sometimes offer unsolicited advice on the off chance that said advice can make a difference.

In short, you seem to have a grievance against linters that goes way past reasonable. You assert this example you give is "perfect" below. You also complain linters waste time and commits despite able evidence in the field they do the opposite.

You seem willing to add drama, grievance, and personal bias to what could have been a rather straightforward technical discussion. The sum of which is: linters sometimes make changes to code that I don't like.

I'd encourage you to reconsider what's really important when it comes to team development and try listening more to those around you. You seem overly focused on asserting your opinion instead of having a discussion.

These types of exchanges are usually very unproductive and stressful in a team environment. They are evidence, IMO, of a dev having the wrong priorities. I'd encourage you to step back and really consider how you view craftsmanship in a team dynamic and whether or not you are fighting the right battles.

Having done both, I'd recommend just starting with pgbackrest.

Offers point-in-time recovery which is an improvement over a custom solution we used to have which gave us nightly backups.

We have it backing up to Backblaze B2 (S3 like). Was relatively easy to setup and no problems really.

Simple: it's like a password that I don't have to type in

Easy to use: because I use 1Password and just have it installed on everything. On Android, it can be set as the default passkey provider so, even on mobile, I am using passkeys shared across devices.

Is this "less secure" because I'm sharing the keys through 1Password. I suppose, at some level. But before that, I was simply sharing passwords through 1Password in the exact same way. So, I don't think my security posture has changed any.

What has changed is the UX and IMO for the better. Now I don't have to generate/fill/copy-paste text strings for user names or passwords. 1Password knows what site I'm on and usually responds automatically when I'm in a passkey context. If I have more than one passkey available, because I have multiple accounts (for something like Google Workspace), it shows me options and I pick the one I want.

Honestly, it's mostly a "just works" system and I like it a lot better than passwords.

YMMV, of course.

I started to use Hetzner's VM options in the Virginia, US datacenter. They had a great performance to cost ratio when I compared them to Linode/Akamai and Digital Ocean about a year ago. At that time, 4vcpu / 8GB server cost $24.99 per month.

Now, to get a VM like it, it's quoted $73.49 a month. Almost a 3x change.

I understand data center economics are changing due to LLM usage. But the Hetzner jump has not been mirrored by their competitors. I'm disappointed I made the switch from Linode. We still have some older VMs there and we'll likely continue to use them instead of Hetzner moving forward.