home.social

#nimlang — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nimlang, aggregated by home.social.

  1. If had been around a bit earlier, it would have solved quite a few of my problems. It looks really nice!

  2. If #nimlang had been around a bit earlier, it would have solved quite a few of my problems. It looks really nice!

  3. If #nimlang had been around a bit earlier, it would have solved quite a few of my problems. It looks really nice!

  4. If #nimlang had been around a bit earlier, it would have solved quite a few of my problems. It looks really nice!

  5. If #nimlang had been around a bit earlier, it would have solved quite a few of my problems. It looks really nice!

  6. I gotta say the nim language docs are rather pleasant :blobcatcoffee:

    Example nim-lang.org/docs/tut1.html

    But then the whole docs page has multiple interesting things to go through:

    nim-lang.org/documentation.html

    A nice experience on the site overall, clear, clean, simple

    Gotchas I've seen so far is that nimble.directory page linked in many places just gives a 502. And yesterday I saw the lsp crashing in gram. Also some editors try to use another lsp binary.

    #programming #nim #nimlang

  7. I gotta say the nim language docs are rather pleasant :blobcatcoffee:

    Example nim-lang.org/docs/tut1.html

    But then the whole docs page has multiple interesting things to go through:

    nim-lang.org/documentation.html

    A nice experience on the site overall, clear, clean, simple

    Gotchas I've seen so far is that nimble.directory page linked in many places just gives a 502. And yesterday I saw the lsp crashing in gram. Also some editors try to use another lsp binary.

    #programming #nim #nimlang

  8. I gotta say the nim language docs are rather pleasant :blobcatcoffee:

    Example nim-lang.org/docs/tut1.html

    But then the whole docs page has multiple interesting things to go through:

    nim-lang.org/documentation.html

    A nice experience on the site overall, clear, clean, simple

    Gotchas I've seen so far is that nimble.directory page linked in many places just gives a 502. And yesterday I saw the lsp crashing in gram. Also some editors try to use another lsp binary.

    #programming #nim #nimlang

  9. I gotta say the nim language docs are rather pleasant :blobcatcoffee:

    Example nim-lang.org/docs/tut1.html

    But then the whole docs page has multiple interesting things to go through:

    nim-lang.org/documentation.html

    A nice experience on the site overall, clear, clean, simple

    Gotchas I've seen so far is that nimble.directory page linked in many places just gives a 502. And yesterday I saw the lsp crashing in gram. Also some editors try to use another lsp binary.

    #programming #nim #nimlang

  10. I gotta say the nim language docs are rather pleasant :blobcatcoffee:

    Example nim-lang.org/docs/tut1.html

    But then the whole docs page has multiple interesting things to go through:

    nim-lang.org/documentation.html

    A nice experience on the site overall, clear, clean, simple

    Gotchas I've seen so far is that nimble.directory page linked in many places just gives a 502. And yesterday I saw the lsp crashing in gram. Also some editors try to use another lsp binary.

    #programming #nim #nimlang

  11. Maybe one way to change the rules is to stop writing code that needs big hardware. The old options were C or C++ for speed and efficiency (which are difficult and dangerous) or Python, Ruby, NodeJS, Perl, PHP for quick and easy coding (but which are fat and slow). But we have better options now, better compromises... #RustLang, #NimLang, #GoLang, #CrystalLang ... the legacy languages have become the tools of the oppressor

  12. Maybe one way to change the rules is to stop writing code that needs big hardware. The old options were C or C++ for speed and efficiency (which are difficult and dangerous) or Python, Ruby, NodeJS, Perl, PHP for quick and easy coding (but which are fat and slow). But we have better options now, better compromises... #RustLang, #NimLang, #GoLang, #CrystalLang ... the legacy languages have become the tools of the oppressor

  13. Maybe one way to change the rules is to stop writing code that needs big hardware. The old options were C or C++ for speed and efficiency (which are difficult and dangerous) or Python, Ruby, NodeJS, Perl, PHP for quick and easy coding (but which are fat and slow). But we have better options now, better compromises... #RustLang, #NimLang, #GoLang, #CrystalLang ... the legacy languages have become the tools of the oppressor

  14. Maybe one way to change the rules is to stop writing code that needs big hardware. The old options were C or C++ for speed and efficiency (which are difficult and dangerous) or Python, Ruby, NodeJS, Perl, PHP for quick and easy coding (but which are fat and slow). But we have better options now, better compromises... #RustLang, #NimLang, #GoLang, #CrystalLang ... the legacy languages have become the tools of the oppressor

  15. Maybe one way to change the rules is to stop writing code that needs big hardware. The old options were C or C++ for speed and efficiency (which are difficult and dangerous) or Python, Ruby, NodeJS, Perl, PHP for quick and easy coding (but which are fat and slow). But we have better options now, better compromises... #RustLang, #NimLang, #GoLang, #CrystalLang ... the legacy languages have become the tools of the oppressor

  16. Added a new learning sample to the #kirpi framework today. This shows that small-scale platformers don’t need heavy physics engines — the collision code is just 20 lines. Enjoy. 🍻

    github.com/erayzesen/kirpi?tab

    #madewithkirpi #gamedev #nim #nimlang #platformer #programming

  17. Added a new learning sample to the #kirpi framework today. This shows that small-scale platformers don’t need heavy physics engines — the collision code is just 20 lines. Enjoy. 🍻

    github.com/erayzesen/kirpi?tab

    #madewithkirpi #gamedev #nim #nimlang #platformer #programming

  18. Added a new learning sample to the #kirpi framework today. This shows that small-scale platformers don’t need heavy physics engines — the collision code is just 20 lines. Enjoy. 🍻

    github.com/erayzesen/kirpi?tab

    #madewithkirpi #gamedev #nim #nimlang #platformer #programming

  19. Added a new learning sample to the #kirpi framework today. This shows that small-scale platformers don’t need heavy physics engines — the collision code is just 20 lines. Enjoy. 🍻

    github.com/erayzesen/kirpi?tab

    #madewithkirpi #gamedev #nim #nimlang #platformer #programming

  20. Added a new learning sample to the #kirpi framework today. This shows that small-scale platformers don’t need heavy physics engines — the collision code is just 20 lines. Enjoy. 🍻

    github.com/erayzesen/kirpi?tab

    #madewithkirpi #gamedev #nim #nimlang #platformer #programming

  21. Advent of Code 2025 - Day 08

    Okay, this one was tough.

    Tried a dozen data structures before settling on circuit IDs + HashTable.

    Accidentally mutated object fields while using them as hash table keys.

    Still have no idea why the puzzle counts already-connected junction boxes, had to look it up on reddit.

    Time to solve:

    Part 1: almost 2 hours
    Part 2: 4 minutes

    Runtime: 364 ms.

    Full solution at Codeberg: codeberg.org/janAkali/aoc25-ni

    #adventofcode #adventofnim #nim #nimlang

  22. AoC 2025 - 07 bonus #2

    I'm blind, because I don't know how I didn't see this 50 minutes ago, but here's even smaller version that runs even faster. 13% faster (95 µs -> 86 µs)

    #adventofcode #adventofnim #nim #nimlang

  23. AoC 2025 - 07 bonus

    I've figured out a faster version of algorithm, that doesn't need a second array to add up splitted particles.

    It results in a whopping 22% performance increase! (116 µs -> 95 µs)

    #adventofcode #adventofnim #nim #nimlang

  24. Advent of Code 2025 - Day 07

    Another simple one today.

    The trick here is to keep count of how many particles are in each column, instead of tracking each beam/particle. Even a simple 1d array is enough.

    Runtime: 116 μs

    Full solutions at Codeberg: codeberg.org/janAkali/aoc25-ni

    #adventofcode #adventofnim #nim #nimlang

  25. Advent of Code 2025 - Day 06

    I literally looked at part 2 for minutes trying to understand where the numbers come from and how they're related to the example input. I love #AdventOfReadingComprehension

    The next roadblock was the trailing whitespace, that I hate and remove from all my code with Neovim plugin. Here removing it was creating subtle bugs and took me time to find out what was the problem.

    Full solution at Codeberg: codeberg.org/janAkali/aoc25-ni

    #adventofcode #adventofnim #nim #nimlang

  26. Advent of Code 2025 - Day 05

    Today we got another easy puzzle. Very straightforward and almost too short.

    #adventofcode #adventofnim #nim #nimlang #aoc #programming

  27. Advent of Code 2025 - Day 05

    Today we got another easy puzzle. Very straightforward and almost too short.

    Full solutions at Codeberg: codeberg.org/janAkali/aoc25-nim

    #adventofcode #adventofnim #nim #nimlang #aoc #programming

  28. Advent of Code 2025 - Day 05

    Today we got another easy puzzle. Very straightforward and almost too short.

    #adventofcode #adventofnim #nim #nimlang #aoc #programming