home.social

Search

66 results for “nurkiewicz”

  1. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  2. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  3. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  4. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  5. @nurkiewicz and merged. And the follow-up request to clean up now unused zig files was created. And closed by #AI. As ai #slop. Ironic.

  6. TIL you can run `ffmpeg` (compiled to ) directly in the browser (recording, converting, streaming) via github.com/ffmpegwasm/ffmpeg.w

  7. Jail-breaking Unitree Robot Dog by... injecting `curl` commands after random password... youtube.com/watch?v=lA8WuXDXfc

  8. A 1 million line PR rewriting from to just dropped... github.com/oven-sh/bun/pull/30

  9. Fascinating talk with and contributors Jean-Baptiste Kempf and Kieran Kunhya:

    > "And everything we’ve just said in the past couple of minutes, every sentence is someone’s lifetime’s work. There are books about- … every sentence"

    lexfridman.com/ffmpeg-transcri

  10. is simple! To copy ("yank"?) the entire buffer into clipboard, just hit [Esc] for Normal mode, followed by `ggyG`! ("go to the beginning of the buffer, yank selection, go to the end of buffer".) Of course you must first add this to use your OSes clipboard...:

    ```
    vim.opt.clipboard = "unnamedplus"
    ```

  11. I switched from #vscode to #Zed and I was blown away that the editor can still be responsive in 2020s. Now I moved further to #NeoVIM. It's obviously even more responsive. Downside: it responds very quickly to my random key presses and I have no idea what I'm doing

  12. I switched from to and I was blown away that the editor can still be responsive in 2020s. Now I moved further to . It's obviously even more responsive. Downside: it responds very quickly to my random key presses and I have no idea what I'm doing

  13. I switched from #vscode to #Zed and I was blown away that the editor can still be responsive in 2020s. Now I moved further to #NeoVIM. It's obviously even more responsive. Downside: it responds very quickly to my random key presses and I have no idea what I'm doing

  14. I switched from #vscode to #Zed and I was blown away that the editor can still be responsive in 2020s. Now I moved further to #NeoVIM. It's obviously even more responsive. Downside: it responds very quickly to my random key presses and I have no idea what I'm doing

  15. I switched from #vscode to #Zed and I was blown away that the editor can still be responsive in 2020s. Now I moved further to #NeoVIM. It's obviously even more responsive. Downside: it responds very quickly to my random key presses and I have no idea what I'm doing

  16. Colors in HTTP server access logs is something I had no idea is so useful! Good work, #Go #Gin framework

  17. Colors in HTTP server access logs is something I had no idea is so useful! Good work, framework

  18. Colors in HTTP server access logs is something I had no idea is so useful! Good work, #Go #Gin framework

  19. Colors in HTTP server access logs is something I had no idea is so useful! Good work, #Go #Gin framework

  20. Colors in HTTP server access logs is something I had no idea is so useful! Good work, #Go #Gin framework

  21. The podcast with Dave Plummer (most known for creating Windows Task Manager) was a joy to listen: lexfridman.com/dave-plummer/

  22. Great article about cascading failures, with #DynamoDB outage in us-east-1 taking down entire #AWS region as an example. I mean, the incident from 2015, not the recent one 😉 blog.mi.hdm-stuttgart.de/index

  23. Great article about cascading failures, with outage in us-east-1 taking down entire region as an example. I mean, the incident from 2015, not the recent one 😉 blog.mi.hdm-stuttgart.de/index

  24. Great article about cascading failures, with #DynamoDB outage in us-east-1 taking down entire #AWS region as an example. I mean, the incident from 2015, not the recent one 😉 blog.mi.hdm-stuttgart.de/index

  25. Great article about cascading failures, with #DynamoDB outage in us-east-1 taking down entire #AWS region as an example. I mean, the incident from 2015, not the recent one 😉 blog.mi.hdm-stuttgart.de/index

  26. Great article about cascading failures, with #DynamoDB outage in us-east-1 taking down entire #AWS region as an example. I mean, the incident from 2015, not the recent one 😉 blog.mi.hdm-stuttgart.de/index