Yes broad consensus had developed in the ten minutes between announcement and you asking if consensus had developed, and I'm excited to report that it consensed in the affirmative -- it IS Space Bunny Alpha!
I tried and as a individual (single/one at a time) image editor is it fantastic, beats Lightroom by a mile and the node editor gives me the ability to "emulate" panels from CaptureOne (and OFX plugin support means I can just LLM my own if I need).
Library management is where Lightroom (and honestly CaptureOne) still wins, I couldn't find a good way to manage a 100k photo library.
I created one project and tried importing the whole library, but it took more than 8 hours and didn't make meaningful progress (~10%?) so I stopped (compared to 15hr for the whole thing in Lightroom).
I also did a project for about 1K photos and while the import worked, the library management itself was lacking. I could not find ways to do image stacks for bursts, group by metadata, etc. The obvious filters are there, but I think it needs more work.
That’s what I was afraid of. Thank you for the answer! Seems like I’ll be stuck with C1 for a little longer. Their sessions and culling tools I’ve found quite helpful for the occasional event shoots I do, and I don’t think I’d be ready to give it up-even if it would save me a little on the subscription.
I also shoot on a Fuji X-T5, and find C1 to be noticeably better than LR. Would be interesting to see how DaVinci stacks up since this release includes support for their sensors.
Are there benchmarks for how this performs on charts, or maybe more accurately, plots? I've yet to find a model that can digitize a plot into X,Y points with some accuracy in my use case of digitizing old datasheets.
Is there improved guidance on migrating from tmux to zellij?
I've attempted to move over a few times, and while this is certainly user skill, it just felt too different from screen/tmux. Perhaps I should bite the bullet and force myself to get used to a new paradigm...
I was confused by its plugins. Despite reading docs over a few days I still have no idea what does runtime for plugins look like, does zellij download them once? on each server start? on each plugin call? and since some features like a switching to a session from another session without spawning child zellij process is available only as plugin, that adds up the confusion, like am I hitting github every time when I switch sessions?
I didn't manage to find a way to update existing session layout when the layout config changed, only to recreate it, which is super boresome when you tinkering with plugin config that is embedded in layout config.
Resurrected sessions needs to be restored manually via somewhat lagging session manager, there's no cli api for that, in general when you need something to be done in another session, you can't.
The only good built-in feature I found is stacking layout showing running command in pane, but I delegate it to tabs in niri now.
Overall I would say if you're long time tmux user, switching to zellij isn't worth it. If you're new to concept of terminal emulators, zellij is much more friendlier, and I'm sure plugins would mature, docs would improve.
For something as simple as a terminal multiplexer, if you aren't seeing immediate value in a switch maybe its fine if you stick with what you have. You don't always need to be on the newest thing. I prefer zellij over tmux, but it is evolutionary not revolutionary. Instead of forcing yourself, save the effort and focus on something more valuable.
Piece of UX feedback for the product team behind Updog: company logos are not searchable. It should be easy to Ctrl-F and find a relevant cloud on that detector, instead of scrolling alphabetically.
You all should add EC2 - extra bonus if you have some way of tracking performance in addition to errors (right now we're seeing EC2 instances in us-east-1c not transition out of Pending status).
I've run a business in this space since 2021, I am yet to meet a business that lets their marketing team own their status page.
You'll find most engineering teams will start owning a status page to centralise updates to their stakeholders, before eventually growing into the customer success/support org owning it to minimise support tickets during incidents.
I'd posit this is more knowing your user. Lots of photo editors/multimedia types use Macs, so it would only help GIMP if they offered Mac keybinds out of the box, or even mimicked the keybinds Adobe Photoshop has.
Loki by Grafana Labs is nice (https://grafana.com/oss/loki/). There was a time (3+ years ago) where the product was changing pretty rapidly and much of the documentation was on git, so we had a few headaches doing minor version bumps, but I believe its much more mature now.
- It is non-trivial to setup and operate. It requires properly configuring and orchestrating numerous components - distributor, ingestor, querier, query frontend, compactor, consul, ruler, memcache, index service, etc. - see https://grafana.com/docs/loki/latest/get-started/architectur...
- Its' configs tend to break with every new release, since some configs become obsolete and some configs change names and/or structure.
- It is very slow on "needle in the haystack" queries such as "search for logs containing some rarely seen trace_id", since it needs to read, unpack and scan all the logs at object storage. This may be also very expensive if the object storage service charges for read IO.
- It doesn't support log fields with big number of unique values (aka high-cardinality log fields). It you'll try storing logs with high-cardinality fields into Loki, then it will quickly explode with enormous RAM usage. Recent Loki releases provide half-baked solution for this problem - "structured metadata" ( https://grafana.com/docs/loki/latest/get-started/labels/stru... ), but it is still experimental and requires non-trivial configs (aka it doesn't work).
reply