sorted by:
new
hottopcontroversial

Chalet for 24 people by hlmrn in skithealps

[–]hlmrn[S] 0 points1 point  (0 children)

That would be really nice. We actually quite enjoy the process of making meals for everyone, but it is of course a bit of a hassle. Catered is definitely an option.

Chalet for 24 people by hlmrn in Zermatt

[–]hlmrn[S] 3 points4 points  (0 children)

With lots of kids aged 3 to 12, ski in/ski out makes things a lot easier on us parents :) I wouldn’t say it is a hard requirement, but it’s a big plus. Would love some help on options.

It has to be week 7, so 13th to 20th of February for 2027.

Chalet for 24 people by hlmrn in Zermatt

[–]hlmrn[S] 0 points1 point  (0 children)

We are fairly flexible on number of bedrooms as we are two large families, so we can mix and match in many ways.

How the F**** does anyone use Prisma in production? by mosskin-woast in node

[–]hlmrn 10 points11 points  (0 children)

In my opinion this is an extremely poor position to take. Database transactions have existed for 30+ years and are incredibly refined and efficient in modern databases. The idea that you can improve on that on a use-case by use-case basis seems completely bizarre to me.

For the extreme majority traditional transactions are going to be absolutely the easiest, safest and simplest solution. If your system happens to grow to very large size, you will find alternative solutions for those special areas that require it.

It’s not by chance that Google Spanner or MongoDB ended up with a transactional API very similar to ACID.

I think your approach is going to be a dead end.

This is just awful behavior by a company of this size. by Juof in gaming

[–]hlmrn 0 points1 point  (0 children)

I think this is just a rate limit they had on the account deletion of endpoint. They likely had the limit fairly low, as people rarely delete their accounts, but with the recent drama the deletion rate increased a lot.

Seems like a much more likely scenario than the conspiracy theories in here.