Yes, either @IfBuildProfile/@DefaultBean if your logic depends on build profile, or @LookupIfProperty/@LookupUnlessProperty if it depends on property value

Can you elaborate on its issues? I've never used it on production myself, but it looks like a simplified k8n, which is something I feel a lot of people desire

Last used it years ago, networking would just die randomly, requiring container restarts when using multiple nodes

I have heard (though haven't tried) that V2 of Compose/Swarm is significantly better.

Anything can and will break. Symptomatically similar thing happened to me with K8s with (IIRC) Calico. And I’ve had issues with Swarm too, although of a different kind (it quietly refused to run a data channel for me over an IPv6-only network, while control channel worked just fine).

It was all quite a while (3-4 years) ago, so I don’t remember much details, except that Swarm was then not exactly capable of working in IPv6-only environments. It was significantly easier to navigate Docker’s codebase than Kubernetes’.

(Ultimately, my solution was that I understood that I didn’t need any kind of orchestration there, just HA/failover. But that’s another story.)

I haven’t used it for many years but in short it just didn’t work reliably. I mostly encountered network iptables issues from memory.

I've been very happy with until now, though i must admit i'm using one node swarms. But i'd rather use that (1) than sticking together a custom solution using docker compose as i see it mentioned sometimes.

(1) https://dockerswarm.rocks/traefik/

Infinite issues with overlay networking once you scale past 30 nodes in a swarm. Weave aside, network drivers for anything not CNI are basically deprecated/dead.

Annoying notifications are a thing for most of the MS stack. Outlook, Teams, Word. Recently I had to dig into some cryptic Registry options to disable some stupid balloon notifications in outlook that pop up every time I open the app. I don't care about your tips and your new interface, I just want to be able to search for a specific email and go back to work quickly.

“New Outlook,” which forgot to remind me to be in a meeting once, and doesn’t support contact groups still because there’s no simple server-side notion of that.

> Annoying notifications are a thing for most of the MS stack.

This. The whole notification mechanism is just awful and not actually very useful. I disable all of it, from any application. I don't want notifications, period.

Care to share that one?

Yes, I mean - https://learn.microsoft.com/en-us/answers/questions/186354/o...

First comment about modifying - `HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\TeachingCallouts`

Care to explain? Keeping private keys inside the repo sounds fine for me as long as these keys are only used for local development, they are rotated regularly and are only valid for localhost (in case of TLS certs).

Not GP: If you make it normal to check in credentials and keys, then the risk of accidentally checking in prod secrets increases. It's basically making it comfortable for devs to deal with keys in repos and I think that's inherently dangerous.

You should be using automated checks to keep credentials out of your repo, not relying on individual developers. And those checks can have explicit exceptions for known safe/public/test keys, just like you might explicitly allow testing or fake credit card numbers.

To reduce the impact of foreign intelligence agencies? Especially important in the EU nowadays.

Basically any foreign intelligence agency can produce perfect fake passports (except for the chip, but you don't need a functional chip).

Even regular criminals manage to produce good enough documents to travel with, and those guys don't have access to Heidelberg printing presses.

Pretty sure any half-competent intelligence agency should be able to make the chip too, if only by infiltrating the company that makes the passports.

Sure, I can't imagine it being too difficult to compromise the keys for some first world country.

But there's no need to bother, you won't get busted at an airport because the chip of your passport failed. If they were suspicious, they'd just go through a document verification checklist and see if your passport has the correct physical features. Check out the PRADO glossary for example https://www.consilium.europa.eu/prado/en/prado-glossary/prad...

A bunch of EU countries still issue non-biometric passports, even if with limited validity periods.

Huh? As if an FSB agent couldn't get a passport..

Absolutely fantastic year, even though I got laid off for the first time in my life! Merry Christmas everyone.

Control + two finger swipe/mouse wheel to smoothly zoom in and out.

One thing I love about macOS terminal is the distinction between Command-C and Control-C in the Terminal. One copies a text under cursor and the other sends a SIGINT. I absolutely hate using Control-Shift-C to copy a text in Linux terminal and Control-C anywhere else.

100% the best thing that Mac does with respect to keyboard shortcuts is the fact that the `Meta` key is the de-facto shortcut key. That makes so many shortcuts consistent across the command line and the OS

While I like that distinction too, I wonder why Linux terminals can’t tell whether something is currently selected or not, and have Control-C do the right thing depending on it?

I’ve been double-mapping Control-C on WSL for a few months (using ConEmu as a terminal) and it works surprisingly well for me.

Some terminals can, kitty for instance.

You should try 1password-linux from snap. It's essentially an Electron app but it works fine for me.

I think it's meant to depend on the fuse-python (https://pypi.org/project/fuse-python/). fuse is something else