neartalk
shady
Our great sponsors
| neartalk | shady | |
|---|---|---|
| 1 | 6 | |
| 22 | 136 | |
| - | - | |
| 3.0 | 3.0 | |
| 4 months ago | 9 months ago | |
| Go | Nim | |
| GNU Affero General Public License v3.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
neartalk
-
Building a simple room-based chat application in Nim (using HTMX)
I wrote something similar with Go and HTMX. It's a powerful combo, and HTMX is really great for someone like me who is not interested in writing JavaScript. I had to write ~10 lines for this project, but that's much less than doing the whole thing in it.
https://neartalk.makeworld.space/
https://github.com/makeworld-the-better-one/neartalk
shady
- How can I add graphics to my nim program?
-
I learned 7 programming languages so you don't have to
I have used Nim for personal projects for 6 years now and it continues to surprise me on how well versed it is for many problem domains. I am fond of it's SPA framework, karax https://github.com/karaxnim/karax for which I wrote a translation utility https://github.com/nim-lang-cn/html2karax Latest Nimv2 release candidate has improved in the ergonomics and syntax that affect compilation to js, so I was able to cleanup my webapp's code to be less verbose. On GPU programming there has been a few projects that touch GPU programming, most notably https://github.com/treeform/shady
-
Why I enjoy using the Nim programming language at Reddit.
This includes the GPU! Yep, that’s right. You can write shaders in Nim. This makes shader code much easier to write because you can debug it on the CPU and run it on the GPU. Being able to run the shader on CPU means print statements and unit tests are totally doable.
-
Compile time evaluation in Nim, Zig, Rust and C++
You can do a lot with Nim at compile time, check out my talk on Nim Metaprogramming not just for FizzBuzz, but real world applications: https://fosdem.org/2022/schedule/event/nim_metaprogramming/
I am working an a macro to compile Nim code into GLSL. So not only can you write Nim to C or Nim to JS, it can also (in limited way) do Nim to GLSL GPU Shaders. See here: https://github.com/treeform/shady
I am also working on a macro system similar to SWIG, where using a some macros one can write a Nim library and generate wrappers for your NIM library for many languages like C, Python, JS, Ruby. See here: https://github.com/treeform/genny
-
Building a simple room-based chat application in Nim (using HTMX)
See this as one of the examples: https://github.com/treeform/shady
It makes debugging shaders much easier as you can use print statements and unit tests. You can also share code between CPU and GPU side.
What are some alternatives?
flask_example - Simple examples of the power of flask
karax - Karax. Single page applications for Nim.
RFCs - A repository for your Nim proposals.
pixie - Full-featured 2d graphics library for Nim.
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
nim_emscripten_tutorial - Nim emscripten tutorial.
htmx - </> htmx - high power tools for HTML
vulkan - Vulkan C bindings for Nim
supersnappy - Dependency-free and performant Nim Snappy implementation.
glfm - Wrapper of GLFM (OpenGL ES and input for iOS and Android) library for Nim.
Snappy - A fast compressor/decompressor