97
Immich vs Ente ? (lemmy.world)
submitted 4 months ago by to c/selfhosted@lemmy.world
64 comments fedilink hide all child comments
 

Chosing the right photo app for my family

So, Immich vs Ente, this is my last piece of the selfhosted puzzle. Please help me make an informed decision:

Immich

on the plus side, it seems to have more features and it has a gazillion integrations with other selfhosted software. Downside: breaking changes are fairly common AFAIK.

Ente

looks like the opposite, more mature, scoped and less integrated.

Am I reading this right? Am I missing something?

Edit: Thanks everyone, I'm going with immich!

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 4 months ago (3 children)

V3 is stable. It is the new version after V2. V1 was where the majoriry of the breaking changes happened.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 4 months ago (2 children)

    No, v3 is a release with breaking changes:

    This release includes several breaking changes; read the full migration guide here. It's worth mentioning that many of the breaking changes are updates to API endpoints and only affect third-party tools that integrate with Immich's API. For the vast majority of users, updating works exactly as it always has.

    https://immich.app/blog/v3.0.0-release

    That's why the major version was increased, it implies breaking changes in semantic versioning, which Immich is doing since v2 apparently:

    Given a version number MAJOR.MINOR.PATCH, increment the:

    1. MAJOR version when you make incompatible API changes
    2. MINOR version when you add functionality in a backward compatible manner
    3. PATCH version when you make backward compatible bug fixes

    https://semver.org/

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 4 months ago (1 child)

    Yes, between major releases there can be breaking changes. But within there wont be, which is what I was referring to. In "V1" we didn't have such a guarantee.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 4 months ago

    Oh I see. You mean like v3.0.1 will be stable, and v3.1.0 will be stable. Yeah that's true. But v3 (as in v3.0.0) is breaking. At least that's how I have always seen the terms used.

  • permalink
  • fedilink
  • source
  • parent