This makes sense. I think I haven’t run into the more advanced cases in my career. NATS (plus or minus jetstream) seems cool–I would like to get an opportunity to work with it at some point.

score 1 · canonical

Quick caveats: this is a post on AI safety, written by a cryptography professor. If that troubles you, you should read something else. I try hard not to work on AI (except when the topic occasionally tosses itself in my path), so in this post I’m mostly trying to referee arguments made by others.

Sad that this needs to be said. The Internet seems to becoming more ignorant by the year.

score 1 · canonical

What’s the issue with database as queue? Is it poor implementations? Too much traffic?

My general opinion is to use the existing database to avoid having to stand up a new system, but maybe I’m missing something.

score 1 · canonical

The paper mentions a relationship between RTP and BitTorrent, but it doesn’t seem like RTP is a p2p protocol? Is it just the magnet links stuff? And I’m confused about the benefit of the magnet links content hashing stuff. Could you elaborate?

score 2 · canonical

Yes, I agree that this is a vulnerability that doesn’t exist in most other languages (although it does in at least some popular Python test runners like Pytest), I’m just pushing back a bit on the idea that Go is unique for using file suffixes. That said, there is no technical difference between an extension and a suffix except maybe on Windows. On *nix platforms (as far as I know) there’s nothing special about the . character).

EDIT: I asked ChatGPT which other languages have test runners that use naming conventions to identify test code and it turns out there are quite a few of them:

Many programming languages rely on file naming conventions to identify test files. Here are some popular examples:

1. JavaScript / TypeScript: Test runners like Jest, Mocha, and Jasmine look for files with names like *.test.js, *.spec.js, *.test.ts, or *.spec.ts by default.
2. Python: unittest, pytest, and nose recognize files with names prefixed or suffixed with test (e.g., test_*.py or *_test.py).
3. Go: The Go testing tool identifies test files by their _test.go suffix.
4. Ruby: The RSpec framework usually looks for files ending in spec.rb, while minitest may use files named with test*.rb.
5. Java: Testing frameworks like JUnit don’t require file naming conventions by default, but Maven and Gradle projects often organize tests in src/test/java with file names matching *Test.java or *Tests.java.
6. PHP: PHPUnit often follows naming conventions like *Test.php to distinguish test files, though this can be customized.
7. Elixir: ExUnit identifies test files by their _test.exs suffix.

Many of these test runners allow customization but often follow these conventions as a default to simplify configuration.

score 0 · canonical

What are some programming languages that don’t impose semantics on filename suffixes? I guess C and C++ don’t insofar as they just punt on build tooling altogether?

score 1 · canonical

Do you have to pay for an iCloud plan then? And if so, what happens when you run out of capacity in iCloud? Or is this syncing feature independent of the iCloud storage plans?

score 1 · canonical

We’re already at the 200GB limit and I don’t think it would take long to hit the 2TB limit if we upgraded. I really just wish they would let me bring my own storage because otherwise my experiences with iCloud have been very positive.

score 3 · canonical

How does this work? Does it have to go through iCloud to get to your MBP? And if so, are you constrained on iCloud capacity (we’re paying for 200GB and we’re already hitting that cap). If not, do you have to plug in a USB, or does it work automatically via the network?

score 2 · canonical