I haven’t used latex in 20+ years, so it’s not real fresh for me but this looks like a great alternative.

35 snaps installed and the only real pain is with the 2 web browsers.

The only places I’ve felt the pain were firefox, chrome, and eclipse. I’ll check later to see what snaps are installed but the sandbox is mostly not noticed. The main issue is that the app with this biggest attack surface (Firefox) is also the one I explicitly want to access my whole system.

Chrome I only installed because ff didn’t work, but it was no better.

It’s so easy to use openjdk. I think the lesson is stop using oracle

We just point a backend developer at it and hope.

I love that differences with gnu are bugs. I know it will lead to slower, less maintainable code, but it makes adoption worlds easier

Any ides have support for this? I feel like I’ve been waiting forever.

I have a 12-15 minute commute and it made a huge difference to me.

I have an extra 90 minutes each day because at lunch time I’m already where I want to be.

What do you want to know?

I’ve been lightly pressured in multiple circles to get an iPhone.

I don’t know .net and sometimes quite some janky code, but I think in this case I would preload everything I definitely needed, locking the records I’m modifying. Then use ConcurrentDictionary.GetOrAdd(Tkey,Func<…>) to load values I might need only when they’re needed.

What language are you using? Is a good idea to limit db calls, but maybe we can help with specific techniques idiomatic to your language

Regardless of what pattern it is, you have a clear performance need and a testable implementation. That’s a win.

Beyond looking for a pattern, I’d look at what your doing to make sure you’re not loading a ton of extra dependencies of your know you won’t use them.

Also, you generally want a database transacting to be one logical unit of work, that all commits or all rolls back together, if you’re combining multiple transactions is likely what you want, but be aware that you might be holding locks for longer, so you might be introducing contention.

By the same token, make sure you’ve got records locked if you need them locked. If you had atomic updates before, or your first update locked the records you needed, you may need to lock records explicitly to keep your database consistent.

Yeah, and the answer is quite a bit for some cases.

How much could performance even improve?