zippy
nim_emscripten_tutorial
| zippy | nim_emscripten_tutorial | |
|---|---|---|
| 2 | 2 | |
| 235 | 78 | |
| - | - | |
| 6.6 | 10.0 | |
| 17 days ago | over 1 year ago | |
| Nim | JavaScript | |
| MIT License | 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.
zippy
-
I enjoy using the Nim programming language at Reddit
Nothing is without the cons. I would say:
* Libraries: there is no NPM ecosystem to get anything you need.
* Stack-overflow: If you looking for a aswers there might not be anyone who encounters it before. You might have to dig really deep to find some thing.
* Some times you might run into a compiler bug usually related with performance of the generated code. Like it generates correct code bug it's slow for no reason and minor changes to the code make it fast again.
* Relying on OpenSSL especially v3 especially on windows is a big problem, but thats more on openSSL i think. I actually wrote a library around this that uses platforms HTTP/SSL instead: https://github.com/treeform/puppy
* Not having HTTP gzip support in standard library. You can always work around with zippy though: https://github.com/guzba/zippy
* async stack traces are really hard to read.
* not enough docs around the different ways to do threading. There is no one solution some times you want a quick thing, some times you are doing CPU tasks other times you are doing network tasks (where async is better). But many big languages struggle here, there is no one fits all threading solution.
It's definitely not style case insensitivity which everyone loves to bike-shed about.
-
Why I enjoy using the Nim programming language at Reddit.
One last example of Nim’s performance is taking a look at zlib. It has been around for so long and is used everywhere. It has to be as fast as possible, right? After all it uses SIMD and is very tight and battle test code. Well, then the Zippy library gets written in Nim and mostly beats or ties with zlib!
nim_emscripten_tutorial
-
Why I enjoy using the Nim programming language at Reddit.
Cross-platform usually gets you the standard Windows / Linux / macOS, however Nim does not stop there. Nim can even run on mobile iOS and Android and has two different modes for the web - plain JavaScript or WASM.
-
Bun v0.2.0
I believe cyclic imports are coming. And Nim does supports wasm...you can target it with `--cpu:wasm32`. You most likely want to pair that with emscripten as in https://github.com/treeform/nim_emscripten_tutorial
What are some alternatives?
Snappy - A fast compressor/decompressor
shady - Nim to GPU shader language compiler and supporting utilities.
supersnappy - Dependency-free and performant Nim Snappy implementation.
jsony - A loose, direct to object json parser with hooks.
glfm - Wrapper of GLFM (OpenGL ES and input for iOS and Android) library for Nim.
zig - The version of Zig used by Bun. Not a fork! Just a slightly older version.
rearchiver - Prepare your Reaper project for archiving, converting WAV to FLAC and changing the RPP file accordingly
bench - 📊 Comparing deno, node and bun HTTP frameworks
pixie - Full-featured 2d graphics library for Nim.
tamp - Tamp is a low-memory, DEFLATE-inspired lossless compression library.