Search
537 results for “nurkiewicz”
-
So I'm watching this premium #Go tutorial. The expert shows how fetching 3 URLs sequentially takes 2.1s, whereas running concurrently takes only... 400ms. Both "tests" in the same process. I'm pretty sure connection pooling, DNS caching, HTTP caching and so on contributed much more than #goroutines... And I thought using float32 for money, a few chapters back, was bad
-
So I'm watching this premium #Go tutorial. The expert shows how fetching 3 URLs sequentially takes 2.1s, whereas running concurrently takes only... 400ms. Both "tests" in the same process. I'm pretty sure connection pooling, DNS caching, HTTP caching and so on contributed much more than #goroutines... And I thought using float32 for money, a few chapters back, was bad
-
So I'm watching this premium #Go tutorial. The expert shows how fetching 3 URLs sequentially takes 2.1s, whereas running concurrently takes only... 400ms. Both "tests" in the same process. I'm pretty sure connection pooling, DNS caching, HTTP caching and so on contributed much more than #goroutines... And I thought using float32 for money, a few chapters back, was bad
-
So I'm watching this premium #Go tutorial. The expert shows how fetching 3 URLs sequentially takes 2.1s, whereas running concurrently takes only... 400ms. Both "tests" in the same process. I'm pretty sure connection pooling, DNS caching, HTTP caching and so on contributed much more than #goroutines... And I thought using float32 for money, a few chapters back, was bad
-
So I'm watching this premium #Go tutorial. The expert shows how fetching 3 URLs sequentially takes 2.1s, whereas running concurrently takes only... 400ms. Both "tests" in the same process. I'm pretty sure connection pooling, DNS caching, HTTP caching and so on contributed much more than #goroutines... And I thought using float32 for money, a few chapters back, was bad
-
Top 10 Tools for Kafka Engineers:
1. #kcat
2. #Debezium
3. Kafka Streams
4. #Grafana
5. Kafka UIs
6. #Redpanda
7. Cruise Control
8. Kafka Security Manager
9. #MirrorMaker
10. Kafka ProxyFrom: https://thenewstack.io/top-10-tools-for-kafka-engineers/
-
#Jetbrains released #Writerside IDE for writing... documentation! I'm just surprised it doesn't seem to support #Asciidoc out-of-the-box https://www.jetbrains.com/writerside/
-
#Jetbrains released #Writerside IDE for writing... documentation! I'm just surprised it doesn't seem to support #Asciidoc out-of-the-box https://www.jetbrains.com/writerside/
-
@sos Well, it seems like they simply put #ffmpeg in the cloud through API. It can actually be a reasonable business model: they run heavy ffmpeg workloads in serverless fashion. ffmpeg is mentioned once in their blog. They also explain their stack: #AWS API GW, AWS #Lambda, AWS #dynamoDB, AWS #SQS, AWS #EC2, AWS #ECS. You pay for the infrastructure you use + profit margin. Many companies simply take open source software and host it in the cloud
-
So far, #Raycast replaced at least two apps in my MacOS setup: #Pastebot and #Rectangle
-
So far, #Raycast replaced at least two apps in my MacOS setup: #Pastebot and #Rectangle
-
So far, #Raycast replaced at least two apps in my MacOS setup: #Pastebot and #Rectangle
-
So far, #Raycast replaced at least two apps in my MacOS setup: #Pastebot and #Rectangle
-
So far, #Raycast replaced at least two apps in my MacOS setup: #Pastebot and #Rectangle
-
So I'm using #powerlevel10k on top of #ohmyzsh on top of #zsh (with plugins) on top of #iTerm2. At this point I have no idea which terminal features come from which software. And if I really need all of these installed
-
Am I the only one still preferring #curl, #httpie and #jq over desktop tools like #Postman? Findings like that aren't helpful: https://www.leeholmes.com/security-risks-of-postman/