Trojan:Win32/Wacatac.B!ml

How about to organize av false positive contest. Competitors creates harmless programs. If your program got most false positives from AVs, you won! If people see many open source harmless programs are detected as virus by AVs, they might stop worrying about Nim's AV problem. Or AV vender might t

Matrix/vector operations in Nim

In 2D or 3D graphics/physics/geometry, you rarely use vectors longer than 4 or matrix larger than 4x4. In that case, following Nim libraries would be more suitable than Arraymancer. I don't know much about Arraymancer, bu

Trojan:Win32/Wacatac.B!ml

Please see my comment above. Microsoft has a process the devs need to follow to remove the false positive.

Update on compiling to asmjs or wasm through emscripten...

My problem with wasm32 is that the allocated memory is never deallocated and memory use grows past the maximum point, where with i386 it can be automatically deallocated by Nim's memory management. Yes, wasm32 is an accepted target, but beyond setting the flag, no further use is made of it, unl

Trojan:Win32/Wacatac.B!ml

There are already some blog posts about it. So, make that a youtube video and use it as marketing opportunity with a title something like "Why virus makers use Nim" or something. Dont forget to bash AV vendors too. Just saying :)

Trojan:Win32/Wacatac.B!ml

> I have no idea what can be done, unfortunately. The only thing I can think of unfortunately is to write a blog post calling out AV vendors for this. If it gets traction it might be read by somebody in the industry that can help us.

Discussion: Why Static Languages Suffer From Complexity

@bpr is right. Calling pre-run-time things "static" is an ancient tradition. (Just web search, for example: static analysis). I do think the less abbreviated "statically typed" is more clear in this context and using two words not much burden. Consistent use of that term might please @alexeypet

A love letter to SciNim

As a former bioinformatical scientist, I really do appreciate that you got this library into nim. I may no longer be your target audience, but none the less it is really nice to see. Cheers!

Unescape string

Finally, here's my solution:

Discussion: Why Static Languages Suffer From Complexity

> I dislike the "static" word, it's too vague. Would be better to call it > "typed vs untyped". That would be completely unhelpful. **static** means that type checks are performed before the program is run, **dynamic** means the checks are performed during execution. To make that clearer, in a

Discussion: Why Static Languages Suffer From Complexity

As for critique for "indentation based syntax". I think it will go away when Nim shows how its usage can make people and companies more money. Right now it's not obvious, and that's why people have nothing better to think about or discuss than "indentation".

Discussion: Why Static Languages Suffer From Complexity

I dislike the "static" word, it's too vague. Would be better to call it "typed vs untyped". They say using typed vs untyped language. Is like free shape sculpting vs using bricks. There are place for both. Each way has advantages and disadvantages. I like free shapeless way for small experimen

A love letter to SciNim

❤

Matrix/vector operations in Nim

There are many matrix/vector packages in Nim: * Arraymancer: (disclaimer I'm the author) * Neo, the first one: * Manu, which has no external dependencies: Or roll your o

usage of OpenMP parallel loop iterator for lazybones?

`-d:openmp` doesn't do anything by itself. if you saw that from Arraymancer it's because I have code like when defined(openmp): doSomething() Run Any variable that is shared among threads MUST deal with thread synchronization: * `total` is shared and if 2 thr

A love letter to SciNim

Wow, uhm, thanks a lot! It _really_ means a lot hearing that (and I'm sure the others agree)! > The only thing I'm not satisfied with is I'm not a data scientist or any > scientist and so there's little place for these awesome libs in my life. I > wish I could use them. Haha, while it doesn't

A love letter to SciNim

Just saw another great lib published by SciNim initiative, Measuremancer. Every time that happens, I can't contain my excitement. This is so damn good! Just reading the guides feels so pleasant! The only thing I'm not satisfied with is I'm not a data scientist or any scientist and so there's li

Update on compiling to asmjs or wasm through emscripten...

@sekao: > Don't use i386 as your cpu target, use wasm32. Are you saying i386 didn't work for you? I used i386 just as @yglukhov recommended and it as always worked for me; when I use wasm32 as a target for the Drag Race program, it compiles but I get some sort of memory allocation problem wher

Update on compiling to asmjs or wasm through emscripten...

Are you setting `--define:useMalloc`? I haven't experienced memory errors with or without useMalloc but maybe it will help. When using i386 an [alignment fault](https://github.com/nim-lang/Nim/issues/17026) was being thrown for me. What do you mean by unrecognized target? `wasm32` is a target i