Re: How I feel about Nim

2019-04-02 Thread Libman
> Sure, IDEs can go a long way toward helping with this problem, but if I'm > reading code on GitHub I often have no idea where a proc is coming from. This > makes it extremely difficult to trace how the code functions without cloning > it locally to open in VSCode. Well, that's a trade-off, an

Re: How I feel about Nim

2019-04-02 Thread Libman
> What is it specifically about Nim that you find hard to read, compared to > which mainstream languages? Nim should not be compared with "mainstream languages". Looking at the [top of the TIOBE Index](https://archive.fo/aISH1) \- the first 17 are either VM, scripting, or unsafe systems languag

Re: How I feel about Nim

2019-04-02 Thread miran
> Tuples are defined like an object, but with square brackets on the same line You can define them exactly the same as the objects (so there you go, another example for your "more than should be necessary" syntax list :)) type Person = tuple name: string age: i

Re: How I feel about Nim

2019-04-02 Thread matthias
Not OP, but in my brief few months using Nim it's 1\. Non-explicit imports Sure, IDEs can go a long way toward helping with this problem, but if I'm reading code on GitHub I often have no idea where a proc is coming from. This makes it extremely difficult to trace how the code functions without

Re: How I feel about Nim

2019-04-01 Thread bpr
What is it specifically about Nim that you find hard to read, compared to which mainstream languages? I find Nim very readable, but I admit that the metaprogramming features (Nim's most important differentiating features IMO) require me to focus more. That's not that different from other langua

Re: How I feel about Nim

2019-04-01 Thread juancarlospaco
If you find the most libs from the most prominent members of Nim community too complex and sophisticated to use, then report a Bug. Believe it or not Developers cant read minds, so User feedback is very appreciated. (at least for my projects)

Re: How I feel about Nim

2019-04-01 Thread Arrrrrrrrr
Definitely we need some articles on multithreading. Specially now with the additions of owned refs, destructors, etc.

Re: How I feel about Nim

2019-04-01 Thread zulu
I have to use whatever the team uses :-)

Re: How I feel about Nim

2019-03-31 Thread Araq
> Nim is easy to write but hard to read. I often have troubles coming back to > my projects and trying to understand the little differences of nim compared > to my other projects in more mainstream languages. Why do you have other projects in languages other than Nim? That's your problem right

Re: How I feel about Nim

2019-03-30 Thread Libman
IMHO, the Nim development and code reading experience would benefit greatly from advanced IDE features, which as of yet don't exist. (VScode is the best supported editor at present.) Nim doesn't force you to explicitly repeat the module prefix where something comes from - if the compiler can fi

How I feel about Nim

2019-03-30 Thread zulu
Nim is easy to write but hard to read. I often have troubles coming back to my projects and trying to understand the little differences of nim compared to my other projects in more mainstream languages. Due to the very few medium to advanced projects out there I often struggle to follow somethi