LittlePeter

Hmm what would happen if I sit down, eat some Taco's and when it is time to pay, I claim I have cash only? Aren't they a creditor in that case?

Garfield maybe

this guy bashes

Not sure why you are down-voted...

Instagram and Dropbox, both used Python.

That is a nice insight.

If Ukrainians are shooting themselves in the foot by doing memes about bombings, how would you describe Russia's invasion? How will that be judged?

snap is the new systemd

I dunno, I am only slightly inconvenienced by it, not enough to run apt uninstall snap though.

It was transformative _because_ it was a downgrade.

On a side note, has anyone ever negotiated an effective raise by asking for 100% salary for an 80% employment?

- "We're sorry but your salary range is above what we are willing to offer."

- "I am prepared to accept your upper range salary for 80% employment."

- "Deal!"

You are right, I probably misunderstood. But now I am curious, what is the use case for formatting just a range of lines and not the entire file?

Barely two weeks after Stable Diffusion release, we use SD as its acronym? That's fast.

Off-topic: in the order book updates example, the top of the book is updated using one field per message:

echo '{ "symbol": "AAPL", "bidPrice": 174.1 }' | rpk topic produce book-updates echo '{ "symbol": "AAPL", "bidVolume": 1000 }' | rpk topic produce book-updates echo '{ "symbol": "AAPL", "askPrice": 174.2 }' | rpk topic produce book-updates echo '{ "symbol": "AAPL", "askVolume": 2000 }' | rpk topic produce book-updates echo '{ "symbol": "AAPL", "bidPrice": 174.0 }' | rpk topic produce book-updates

However some top of the book update can result in an entire level disappearing. In that case, both price and volume changed actually at the same time, yet according to this example it will be broken down into two messages? This will lead to inconsistent state of the book when I read it between two messages. Or did the example just happen to show one field per message, and multiple fields per message are possible too?

Back in the day `aws ec2 get-console-output --instance-id $ID` used to contain the public key that can be extracted using regex. Not sure if this still works.