So far, as expected, lots of onboarding, learning about processes and other bullshit.

Really boring to be honest.

But they let me roam in the repos, which I do in my own time, and that has been really enlightening.

@retoor

Well, I mean, I know what was to be expected.

It's prospectively exciting, but so far still lost mostly in bureaucracy.

If you have any specific questions, (and I'm allowed to answer them), I will gladly do.

@sandeepbalan

Annoyed cuz I have to do bureaucracy for taxes and such.

I will listen and dance to 80/90's eurobeat, but if you ever say it in public, I'll deny it and make a necklace with your teeth.

You can maybe also use Kafka, which can do what you want, but that depends on your other requirements.

If you want your readers to split the workload, instead of fan-out exchange, set a round robin or similar exchange that also copies to another exchange which has your redis-saving queue, so any message you publish to the main exchange gets copied to the redis exchange and queue, and thus saved, and will go to one of your connected queues, which will split the work.

@BordedDev

You can actually do that combining amqp with redis. Have a fan-out exchange with one permanent queue.

This permanent queue is consumed by a service or lambda that stores the message in redis with your desired expire time.

Whenever a new instance of your reader is spun up, you do the following:

- Create a new, non permanent queue in your exchange for the reader to consume using the rabbit API.

- Scan your redis for the last X time messages.

- new messages will arrive to your reader when published until you stop consuming.

There's probably a way to do it directly in rabbit, but I don't know it.

For communication I'd consider an amqp broker such as rabbitmq before redis.

They will do perfectly for my paella.

(Yes, they are food)

@D-4got10-01

Hahaha, whenever I see AI fingers I can't help but think of facehuggers from Alien. XD

@D-4got10-01

A Venus flytrap?

@D-4got10-01
@retoor

The second image is more upsetting IMO. Not just the fact of having 2 opposable thumbs, but I'd expect AI nowadays to at least know which side thumbs are supposed to go on XD

@rjscratton

This a fucking thousand times.

Gradle is fucking AIDS cancer.

Tho moreso than Gradle itself (which suffers from horrendous back compatibility due to being horrendously immature), it's the android Gradle *plugin*, which suffers from that *and* its own immaturity.

Indeed it's 10, in base 38 xd

@Lensflare

My man, he snorts chaos emeralds and gets such an high that he actually turns super Saiyan and flies!

You could also simply not have kiddo and do whatever the fuck you want XD.

Good thing I don't really care if a potential partner has kids, because at my age that would severely limit the pool, but then again, I still live like I'm 20, even if my body doesn't like it.

I dare say the description fits sonic more than Mario XD

Also Mario is secretly communist.

Haven't you realized his goal is actually overthrowing the rightful king and proudly rising the red star flag onto his castle over and over?

But will you blend?

@Lensflare

You can indeed disambiguate by fully qualifying, yeah.

Using using in an implementation file is not so bad, but doing so in a header file deserves the gallows, because you'll pollute the global namespace of whichever file includes it.

@Demolishun

But surely they can have a std:: future?

@donkulator

Global using namespace are evil.

(And defeat the whole point of namespaces)

But that's only if Json got a 201 on
POST /stress
{"disorder": "traumatic"}

I'll see myself out

Could simply be growth.

This week, I had to dust off lots of C arcane knowledge that I barely remembered.

They didn't come into use for my line of work in decades, so naturally, other knowledge takes its place in the forefront, and, the more you diversify, you end up with a broader perspective of the whole process, and naturally end in architecture/DevOps/sysadmin, etc, at the price that low level details give way.

In my experience, the problem always comes from salesmen wanting to parrot shit about being "cloud native", "high availability", "scalable", "state of the art", and other bullshit.

And they end paying absurd amounts of money and man hours for something they could easily run in a couple computers gathering dust in the corner.

@antigermanist

Not saying otherwise, but "sidra" is not exactly English, or gaelic.

@cprn

Well, I'd rather express it the other way around. Duck typing is the polymorphism of non statically typed languages.

But yeah, in the end both aim to solve the same problem, just that in one the contract (interface) is explicit, and in the other it is by convention.

Historically, non static typed languages have been interpreted, and those, by the very definition, could only have runtime dispatch anyway.

Another undercover spaniard or latinoamerican, it seems. Cheers.

45 min ago. Feliç passagem do ano para tudos!

For me, and mind you, my family ain't perfect by any means but it certainly is *big*, we have an unspoken rule that didn't really apply to me but does now, which is, "don't burden the children with the sins of the parents".

Our parents could hate each other's guts, but would always be there for the nephews/nieces, no matter what.

That's how I see family. Don't really watch TV so can't speak about portrayals, but still. Family is who you choose it to be. If the biological ones are worthy, do cherish them, otherwise, nah

@retoor

I know UUID is just a format, hence why I said "safely generated".

@kiki

urandom itself does fall back to known PRNG algorithms such as Mersenne when there's not enough entropy, but yeah, so long as entropy ain't a big fat 0, you should be set.

Also, last I checked, servers without physical sources of entropy could fall back to algorithms run on a concat of request bodies and timestamps to substitute /dev/u random.

While that certainly has more of an attack surface, it is still a decent source of entropy.