I'll probably drive it into the ground because I drive like a maniac. A new car is wasted on me.

Con: I pay my ass of in taxes because its a diesel. Pro: I imported it for free.

You can no longer do that since 1st of Jan 2025. The BPM discount for company cars was removed.

I love that it barely has any styling. Just enough to make it work. The fact that it doesn't use any design patterns is actually one of the reasons I visit HN.

The only thing I would change is the font sizes on mobile. I find it hard to tap the `Comments` link or the upvote buttons. I sometimes end up fat fingering those. Maybe a little bigger or a bit more padding?

All the risky moves that I made so far in life ended up being ok. Stressful, terrifying, but I always came out ok somehow.

Couple of examples:

- Moved to a lesser developed country at 19 to be with a girl.

- Bought two homes at the same time, was broke for a while.

- Moved back to my home country & bought a house in a crazy market.

- Joined a startup as the third employee.

I have 1 GBit up+down at home, I cabled the whole house with CAT7 cables and set up the best access points money can buy for mobile devices. Everything else is wired. It's an amazing experience and internet everywhere sucks compared to home.

When I lived in Romania this costed me €10, now that I am back in the Netherlands it's a bit more pricey at €52, but it's 100% worth it.

Keycloak 17 made offline sessions lazily loaded by default.

[0] https://www.keycloak.org/docs/16.1/server_admin/#offline-ses...

As long as we wouldn't do any restarts, it would sort of work. Problems would pop up when due to high load, one or more nodes would become unresponsive and liveness probes would restart nodes. That would often cause the kind of cascading failure described above.

Most of these problems are also the result of running it in Kubernetes. We very quickly learned to remove the liveness probes and to massively increase the grace period. This helped, but only so much. We still had rather frequent failures similar to the one I just described.

Maybe if we wouldn't have run it in Kubernetes and we would be more knowledgeable about Infinispan, we could've gotten a stable set up. For us, as a small team without that specialized knowledge, we struggled to get a stable set up.

At work, I ran 9 Keycloak clusters in production, handling tens of millions of sessions where the cost of losing sessions was high. The amount of time we wasted on getting it to work reliably with its default configuration of storing the sessions in its distributed, in-memory cache (Infinispan) is insane. It just isn't designed to handle such a work load reliably. Unless you're willing to spent months tuning it for every possible scenario, you WILL lose sessions.

If you are in this situation, shoot me an email. I have been through this pain and it took a lot of painstaking work to get to a highly reliable set up at scale.

9€/month, 1 Gbit down, 450 Mbit up.

It's all fiber. You can't really get non-fiber around here. It's blazing fast and pretty stable. There are no real restrictions. They have a fair use policy, but I never heard of anyone being slapped on the wrist for using too much.

[1] https://www.cloudamqp.com/

It would've been much better for Redis's long term health to have the logo and name trademarks transferred to a non-profit steering organisation managed by the steering council so that not a single entity controls it.

This will make it more difficult for competition to enter the market. People will assume that "Redis" is somehow the same as Redis the software.

It's impossible with a kid. I tried for the first few months. I don't have time to wait for the bus for 10 minutes with a screaming baby, neither do I want to stress that the entire bus or train needs to listen to my crying baby for the ride. Taking the kid to the doctor halfway across town is just a nightmare with any of the alternative modes of transport.

Give me a good alternative for taking a screaming baby to the doctor without pissing off everyone and I'll happily get rid of the car.

[0] https://en.wikipedia.org/wiki/Cluj-Napoca

As for your example with --disable-features=Windows10CustomTitleBar, you can view the motivation for the relevant change here: https://source.chromium.org/chromium/chromium/src/+/549aa8ae...

It wasn't removed, it just changed. It's not a feature flag anymore, just a normal flag: --disable-windows10-custom-titlebar.

This appears to be a purely technical decision. I am not even sure a PM was involved.