home.social

Search

1000 results for “ku1ik”

  1. @ku1ik would you to ? We could make a interactive learn video like

  2. Here’s the opening slide for my tomorrow’s talk at ElixirConf EU 🤘

    #elixirconf #elixirconfeu #elixirlang

  3. Here’s the opening slide for my tomorrow’s talk at ElixirConf EU 🤘

    #elixirconf #elixirconfeu #elixirlang

  4. Here’s the opening slide for my tomorrow’s talk at ElixirConf EU 🤘

  5. Here’s the opening slide for my tomorrow’s talk at ElixirConf EU 🤘

    #elixirconf #elixirconfeu #elixirlang

  6. Here’s the opening slide for my tomorrow’s talk at ElixirConf EU 🤘

    #elixirconf #elixirconfeu #elixirlang

  7. Anyone here has deployed #crowdsec and can share some tips? Their website is so incomprehensible to me…

  8. On the hardware side of my dev setup I made 2 changes:

    Switched from #Realforce TKL keyboard to #HHKB Pro Hybrid Type-S. Those #topre switches are endgame, and while I had the same ones in the Realforce, the overall feel of HHKB, its layout, size, weight, feels great. It forced me to start using ctrl in caps-lock position due to its layout, which is something I wanted to try in the past but never had enough will. Should have done this earlier, because it feels great.

  9. I started new year with major changes to both my dev setup and my home media setup. In both cases it feels like great improvement!

    #neovim #hhkb #paperwm #ghostty #jellyfin #manet #infuse #gluetun

  10. I've switched from #9pfs to #virtiofs mount for a VM I run under my #proxmox host at home and did a few #fio benchmarks.

    9pfs (before):

    seq read (1M, 1 thread) - 1950 MiB/s
    rand read (4K, 4 threads) - 213 MiB/s
    seq write (1M, 1 thread) - 468 MiB/s
    rand write (4K, 4 threads) - 80 MiB/s

    virtiofs (after):

    seq read (1M, 1 thread) - 5258 MiB/s
    rand read (4K, 4 threads) - 291 MiB/s
    seq write (1M, 1 thread) - 1074 MiB/s
    rand write (4K, 4 threads) - 84 MiB/s

    2.7x sequential read, 2.3x sequential write, 1.3x random read, and 1.05x random write.

    Pretty good improvements!

    Especially that this is for my media (movies/tv) mount where mostly sequential I/O is typically performed.

    Note the underlying hardware is Samsung QVO SATA SSD, which is rather slow SSD, and likely a bottleneck in those random read/write tests. I expect there would be much bigger differences on a fast NVMe drive.

  11. Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

  12. The other change on the hardware side of my dev (but also gaming) setup was getting 40” Dell 5K super ultra wide (21:9) monitor (U4025QW). Extra screen estate is nice for productivity (I switched from 16:9 4K), it has lots of connectivity, the 120hz refresh rate makes #PaperWM buttery smooth, and the desktop looks super sharp at 125% scaling on #Wayland. The curved surface is sth I was worried about, but turned out it’s a subtle curve and not distracting at all. Some say it’s an endgame monitor…

  13. Last change on the software side of my dev setup was to start using #PaperWM. It’s so awesome! It’s fast, smooth, has exactly what I need from a window manager, and it’s rock solid. In the past I’ve been using #awesomewm, #xmonad, #i3wm and while I liked them all better than classic floating WMs, only PaperWM feels exactly like what I always needed. And, on a 120hz display its quick animations look fantastic.

  14. I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!

    chadaustin.me/2024/01/truecolo

    #terminal #softwarearcheology

  15. I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!

    chadaustin.me/2024/01/truecolo

    #terminal #softwarearcheology

  16. I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!

    chadaustin.me/2024/01/truecolo

  17. I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!

    chadaustin.me/2024/01/truecolo

    #terminal #softwarearcheology

  18. I really enjoyed this post by @chadaustin where he goes deep into the history (and related mistakes) of introducing 8-bit and 24-bit support in SGR sequences. Fantastic blast to the past!

    chadaustin.me/2024/01/truecolo

    #terminal #softwarearcheology

  19. Today I learned about #justcommandrunner

    This may be a good replacement for my usage of make/Makefiles, which is 100% for running project specific tasks. No more .PHONY targets!

    github.com/casey/just

  20. I'm looking for a remote Rust/Elixir role (EU-friendly timezones, US East is ok).

    I have 7 years of #rustlang, 9 years of #elixirlang, 20+ years of #linux.

    I have over 20 years of experience as a professional developer, and I've been working remotely for 12 years, during which I helped US and EU companies build reliable software.

    On the side, I've been developing #asciinema, the best tool to record and stream your terminal sessions. I talk about it in the context of Rust in this #RustaceanStation interview: rustacean-station.org/episode/

    My current contract ends soon, so this is a great time to talk! I'm open to both full-time roles and short term contracts.

    My linkedin profile: linkedin.com/in/marcinkulik/

    Boost please!

    #fedihire #getfedihired

  21. Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

  22. Aaand I’m back on . The mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

  23. Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

  24. Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

  25. I've switched from #9pfs to #virtiofs mount for a VM I run under my #proxmox host at home and did a few #fio benchmarks.

    9pfs (before):

    seq read (1M, 1 thread) - 1950 MiB/s
    rand read (4K, 4 threads) - 213 MiB/s
    seq write (1M, 1 thread) - 468 MiB/s
    rand write (4K, 4 threads) - 80 MiB/s

    virtiofs (after):

    seq read (1M, 1 thread) - 5258 MiB/s
    rand read (4K, 4 threads) - 291 MiB/s
    seq write (1M, 1 thread) - 1074 MiB/s
    rand write (4K, 4 threads) - 84 MiB/s

    2.7x sequential read, 2.3x sequential write, 1.3x random read, and 1.05x random write.

    Pretty good improvements!

    Especially that this is for my media (movies/tv) mount where mostly sequential I/O is typically performed.

    Note the underlying hardware is Samsung QVO SATA SSD, which is rather slow SSD, and likely a bottleneck in those random read/write tests. I expect there would be much bigger differences on a fast NVMe drive.