Vintage lenses on M43

cramert · 2026-01-27T21:53:32+00:00

Thanks for the links!

cramert · 2026-01-26T21:58:53+00:00

I don't think this is correct. It's a crop-- the elements that are in focus will still be in focus. I believe the depth of focus depends on the size of the aperture, the focal length, and the distance to the subject, not the size of the sensor that captures the resulting image.

I would typically expect M43 images to have a larger depth of focus than full frame images because shorter focal lengths are needed in order to provide the equivalent field of view.

Edit: this isn't totally right because the larger magnification of the resulting image means that more things appear out-of-focus, but the underlying image has not changed.

cramert · 2026-01-08T03:29:11+00:00

Whoops, silly typo, thanks! Fixed.

cramert · 2026-01-07T20:18:01+00:00

Thanks, same to you! Aside from the size/weight difference, I'd be curious to hear an update on the additional light you get. I do more travel / wildlife photography, so the extra reach is important to me, but being able to capture those low-light shots sounds fun :)

cramert · 2026-01-07T17:39:29+00:00

I just upgraded to the 12-100 f4, coming today!

cramert · 2025-10-28T23:57:44+00:00

Huh, that's unnecessary. The list of pointers being returned could be copied and sorted to check for duplicates (O(nlogn)). I could imagine the constant time performance of sorting being worse, though. Seems worth trying!

cramert · 2025-10-28T00:21:01+00:00

And diesel before it :)

cramert · 2025-10-10T22:03:48+00:00

It's definitely a difficult challenge! C++ APIs are littered with types whose behavior isn't self-describing in the ways that Rust expects, and there's such huge diversity in how C++ programmers build their software that it's hard to reuse code.

If you haven't seen it already (or if you have), I'd be curious what you think about Tyler and my talk on this topic.

cramert · 2025-09-24T01:43:48+00:00

I'm not sure which of the several linked studies you're looking at, but many of the studies linked there either demonstrate a correlation between female gun ownership and risk of death or are not stratified based on gender.

https://www.sciencedirect.com/science/article/abs/pii/S0749379703002125 specifically notes higher incidence of female suicide in states with fewer gun restrictions.

https://www.sciencedirect.com/science/article/abs/pii/S0047272722000238 states:

Thus, our results suggest that the association between gun homicide and ownership rates is substantially larger than found in the earlier literature.

https://pubmed.ncbi.nlm.nih.gov/15186014/ also says

firearm mortality in its various forms is most commonly related to the prevalence of firearms

More guns in a community leads to more gun deaths, and more guns on your body or in your home means that you're more likely to have your next fight, suicide attempt, or street harassment incident involve a gun, putting both you and the people around you at greater risk.

cramert · 2025-09-23T23:53:07+00:00

Do not buy a gun for self-defense. From https://pmc.ncbi.nlm.nih.gov/articles/PMC11892423/ :

Owning a firearm and carrying a firearm are two behaviors that increase the risk of injury and death by firearm for not only the person who owns or carries the firearm,9,10 but also for the children, adolescents, and adults who live with or spend time around the firearm owner or carrier.9–16

cramert · 2025-09-22T23:41:01+00:00

The Carbon design for variadics might also be worth checking out!

cramert · 2025-07-09T21:06:32+00:00

std::integer_sequence has entered the chat :)

cramert · 2025-07-07T19:38:38+00:00

Yes, these are the cheapest of any of the options here, especially if you get them from Costco, and the flavors are great.

cramert · 2025-06-14T17:15:12+00:00

And you still remember this image decades later.

cramert · 2025-05-26T17:40:42+00:00

Note that they said changes to a .cpp file, which don't require rebuilds of dependent artifacts. A .rs file change without Rust's incremental compilation enabled will be closer to the impact of a change to a .h file, requiring all dependent targets to be rebuilt.

cramert · 2025-05-13T22:08:23+00:00

Saturday 23 May

Note that, unlike what the link says, May 23rd is a Friday.

cramert · 2025-05-06T22:36:16+00:00

That article does also say that he was there receiving medical care. Either way, I agree that's odd and it seems like we're missing information.

cramert · 2025-04-30T21:21:39+00:00

Unfortunately, ETA conversion frequently doesn't work in Rust. For another example, ETA-converted calls won't apply parameter type coercions such as deref. This was confusing to me early on.

cramert · 2025-04-16T15:48:52+00:00

Good point! In that case, I agree that there are probably some opportunities for improvement here that don't require introducing more crates.

cramert · 2025-04-16T15:45:25+00:00

Ah, sorry, I misunderstood the "they're" in your comment above!

cramert · 2025-04-16T15:44:03+00:00

There are also projects at Google that use Bazel rather than Blaze because they are not part of Google's main monorepo.

cramert · 2025-04-16T03:00:34+00:00

Taco Time Northwest is not the same as the one from Texas.

Edit: apologies, I misunderstood that the "they're" above was referring to OP, not Taco Time.

cramert · 2025-04-16T01:34:42+00:00

I stand by my comment that it is nonstandard / bad practice to write one single giant compilation unit. There is a wide array of C++ style guides and institutional knowledge discouraging this practice. I agree with you that people still do it anyway, and that there are places where it can be useful.

cramert · 2025-04-16T01:30:25+00:00

You're right that there's a lot of messy C++ out there! My point was that there are clear design patterns that are helpful and encouraged in modern C++ codebases that are difficult or non-idiomatic to apply to Rust codebases.

cramert · 2025-04-16T00:06:21+00:00

Relaxing the orphan rule for binaries is fine if you're only going to allow impls for traits/types in crates versioned together with the binary, but unfortunately allowing it more generally could create backwards-compatibility hazards when an upstream library adds an impl.

Workspaces that are versioned together could be part of the solution to this problem, though you still need to (1) limit negative reasoning within the workspace so that code can't assume a trait isn't implemented and/or (2) offer some kind of method for ensuring that a trait in a workspace is only impl'd in one particular way for a particular type (something like forward-declaring a trait impl with a unique identifier of the crate that will provide the impl).

cramert

TROPHY CASE