Nim devroom at FOSDEM this weekend

Usually, FOSDEM talks are available after some time. This year talks will be available to download here: And thank you everyone for the talks. It was a pleasure to watch them. :)

Nim devroom at FOSDEM this weekend

Hi! I missed it too. Would love to watch the talks. Are there any archived yet? @dsrw Thank you for making yours available :)

Passing iterators as arguments

is `Iterable[T]` implemented through concepts the correct way ?

Passing iterators as arguments

`iterable[T]` is a compiler supporting type that says "i want an iterator". It is not a concept.

Benchmarking

P.S. and `nim c -f -d:danger --gc:arc --clang.options.speed="-O4 -flto" --clang.options.linker="-flto" lru3.nim` gives 0.28s on my M1 or about 26% faster than the Rust one! Though to be fair, without LTO the Nim version clocks in about 0.43s about 13% slower than Rust. Finally Nim with no LTO us

Benchmarking

> OrderedTableRef instead of OrderedTable + var, method instead of proc, lcg > being a double-closure are some obvious things, but there is the real > bottleneck that Rust can do let Some(&v) = table.get(k) while Nim does if k > in table: let v = table.get(k). There is already withValue for this

Passing iterators as arguments

I would not call it a hack as much as ill thought out, it cannot be used with a typeclass and does not automatically use `pairs` or `items` so sequences/arrays require manual `.items`. It cannot be used as an inline iterator parameter, as you may know inline iterators are after all just fancy t

Passing iterators as arguments

Can you elaborate ? why is it a hack ? if it is a hack, why was it introduced ? what's the alternative ?

Benchmarking

The blog post is 7 years old obviously which could mean different things for both Nim and Rust, but Nim has changed a lot more since, notice there is a nil seq in there. So the results today might be different but not sure how much. For all I know LLVM could have been vectorizing conway's game o

Nim devroom at FOSDEM this weekend

The dev room was great! Thanks to the organizers. If anyone posts their videos elsewhere, could you link them here? I had to miss 4 of the videos today, and I'd really like to see them all. I put my video (Potato Zombies) up at .

Passing iterators as arguments

its a hack

Flutter and Nim

hmm... I have a thought for an experiment.

Flutter and Nim

It's great for those that prefer a server-driven UI. You can also use the output for a client-side UI if you like. It also greatly simplifies the use of Flutter, which is great for rapid development. The Flutter SDK itself can be very tricky to use correctly, however that approach also gives you

Flutter and Nim

Thank you. What are the benefits over the native dart way? better abstraction abilities?

Passing iterators as arguments

Hi, now that `iterable[T]` was introduced in 1.6, Why wasn't the standard library updated to work with it yet ? is it just a matter of time ?

Benchmarking

I've some problem with site rendering on Safari on my MacBook Pro (apparently the flags to filter results with / without parallelization do not work), but not with Android smartphone. It seems that a lots of Rust results are with parallelization, while Nim has just one for spectral-norm (much sl

Benchmarking

The first one, that I read could definitely be made faster. It uses tables without needing too, while rust versions don't.

Benchmarking

Hi! I decided to google it, and i found few sites, just want to share with you [side by side comparison of several programming languages](https://programming-language-benchmarks.vercel.app/nim-vs-rust) [blog post](http://arthurtw.github.io/2015/01/12/quick-comparison-nim-vs-rust.html#:~:text=Ru

Flutter and Nim

If you want to sign-up to be notified of the cross-platform UI kit, you can now sign-up: The initial back-end SDK is for Nim.