okigan

Readme is mostly install and usage information but not much above the use case.

OP - could you fill in why/when one would use it?

that's a very broken metaphor - it might be "similar" to try-finally block if you only have one variable/object following RAII. But try-finally block(s) become complete mess when multiple variables are involved, and again requires way more typing/duplication than RIAA. And "similar" in terms of results, NOT similar in terms of performance as try {} block requires additional instructions to set it up, whereas RIAA is runtime free.

And regarding sibling post about finalizers -- another broken concept as you cant use finalizers with limited resources (ex. graphic contexts, db connections, handles, locks, etc) and then these languages that use finalizers become complete mess if you need to manage such resources.

it's mesmerizing that the fantastic ergonomics of RAII have not propagated to other languages.

It's way easier to use, much clear, less typing, more predictable runtime behavior.

RAII... terrible name, great concept!

Or creating repos that will merge their PR(s).

With all respect to FreeBSD.

It seems weird in 2025/2026 we are still discussing the baseline of getting a storage working.

Feels we’re spending too much time discussing the trees and not enough time getting the forest going: * we need reliable local storage * integrated backup * apps installation / management * remote access and account management * app isolation, reliable updates

Would love to see a snapshot of the GUI as part of the README.md.

Also docker link seems to be broken.

Most are overpaying in taxes for what they are getting.

Not to mention single/families without kids and seniors that still pay for school districts.

It’s unclear from your description is this Z3 problem or this is the nature of such problems (and it’s a wish).

Are there other tools that do it better or proposal how Z3 would do it?

Ugreen

It is so seductive that people don’t read the footnotes that explain that active-active does not do what they think it does.

It took 20 years to acknowledge that pushing eventual consistency to application layer is not worth it for most applications.

Seems the same is playing out out in Postgres with this extension, maybe will take it another 20 years

What’s a better syntax then?

Fantastic article.

I don’t use numpy often enough - but this explains the many WTF moments why it’s so annoying to get numpy pieces to work together.

Don’t you need to apply filtering to the frame selection based on scene score?

Otherwise you’d select frames with 0.3, 0.7, 1.0, 0.7, 0.3 - selecting 5 frames instead of 1?

Two pass with sobel filter comes to mind.

Could we have a concise and specific explanation how DSPy works?

All I've seen are vague definitions of new terms (ex. signatures) and "trust me this very powerful and will optimize it all for you".

Also, what would a good way to reason between DSPy and TextGrad?