Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nim core developer wanted

forum.nim-lang.org

Post reply on HN
Print view View original

11–20 of 21 posts

Re: Nim core developer wanted

#11

Post by emsy »

crux wrote: post #7
meddlepal wrote: post #6

Earlier quoted context omitted.

I'm interested in hearing about your experience! Pitfalls? Major positives? Have you considered writing about it?

I have! And I will... I just haven't gotten around to it yet. The main takeaway is specific to my use-case: writing a dynamic library that can be called from within Python code. The main positive and negative are two sides of the same coin: since Nim compiles to C, you get to use all the existing tools designed for doing C FFI in Python, and don't have to write any C wrappers. And since Nim isn't C, there's still a l…

Have you encountered any major compiler bugs? Nim looks great, but the list of open issues on GitHub would scare me from using it in production. Or isn't it as severe in real-world use?

Re: Nim core developer wanted

#12

Post by [deleted] »

crux wrote: post #7
meddlepal wrote: post #6

Earlier quoted context omitted.

I'm interested in hearing about your experience! Pitfalls? Major positives? Have you considered writing about it?

I have! And I will... I just haven't gotten around to it yet. The main takeaway is specific to my use-case: writing a dynamic library that can be called from within Python code. The main positive and negative are two sides of the same coin: since Nim compiles to C, you get to use all the existing tools designed for doing C FFI in Python, and don't have to write any C wrappers. And since Nim isn't C, there's still a l…

[deleted]

Re: Nim core developer wanted

#13

Post by audunw »

emsy wrote: post #11
crux wrote: post #7

Earlier quoted context omitted.

I have! And I will... I just haven't gotten around to it yet. The main takeaway is specific to my use-case: writing a dynamic library that can be called from within Python code. The main positive and negative are two sides of the same coin: since Nim compiles to C, you get to use all the existing tools designed for doing C FFI in Python, and don't have to write any C wrappers. And since Nim isn't C, there's still a l…

Have you encountered any major compiler bugs? Nim looks great, but the list of open issues on GitHub would scare me from using it in production. Or isn't it as severe in real-world use?

emsy: I'm not OP, but I encountered quite a few compiler bugs when I was using Nim a couple of years ago, but that was only because I tried to push the macro system really hard.

Generally most bugs are related to newer features. I never experienced any bugs with the core features/library.

Re: Nim core developer wanted

#14

Post by Meegul »

hubert123 wrote: post #10
jestar_jokin wrote: post #9

Earlier quoted context omitted.

Games, or soft real-time systems (like audio tools; synths, DAWs, or editors). Potentially, cross-platform mobile apps. Thanks to its approach to GC, you can impose a limit on the time to spend on GC between ticks, so no unpredictable performance stuttering. I see it as having nice "functional-ish" syntax like Python, but with static types.

A limit on GC time might then obviously lead to high or too high memory use, potentially?

Not OP or aware of Nim's specific implementation, but in some cases, yes. However in a fps-sensitive situation like a game, it just takes ~16ms of GC before you've missed at least one refresh. By limiting the time to something lower, we can distribute this time such that the user doesn't notice any stuttering, provided the GC events were spaced out enough.

Re: Nim core developer wanted

#15

Post by zielmicha »

emsy wrote: post #11
crux wrote: post #7

Earlier quoted context omitted.

I have! And I will... I just haven't gotten around to it yet. The main takeaway is specific to my use-case: writing a dynamic library that can be called from within Python code. The main positive and negative are two sides of the same coin: since Nim compiles to C, you get to use all the existing tools designed for doing C FFI in Python, and don't have to write any C wrappers. And since Nim isn't C, there's still a l…

Have you encountered any major compiler bugs? Nim looks great, but the list of open issues on GitHub would scare me from using it in production. Or isn't it as severe in real-world use?

There are compiler bugs, but almost all of them are related to advanced metaprogramming. If you stick to "normal" metaprogramming (generics, templates, sane macros), compiler works well.

Re: Nim core developer wanted

#16

Post by Sir_Substance »

jbpetersen wrote: post #8

Nim is one of those things that seems very well put together yet I can't currently see what role it fills in the wider market for programming languages and different types of communities around them. What kind of stuff is particularly popular among Nim users compared to communities for other languages? What kind of stuff do the people working on Nim want to use it / see it used for?

>I can't currently see what role it fills in the wider market for programming languages

"As friendly as python or ruby, but compiles to binary for ease of deployment and speed" is currently an under-served market niche.

Rust, Go and Swift are all candidates for the space (with the current defacto standard of friendliness in compiled languages being c++), but I find none is quite a match for me.

Re: Nim core developer wanted

#19

Post by nimmer »

Sir_Substance wrote: post #16
jbpetersen wrote: post #8

Nim is one of those things that seems very well put together yet I can't currently see what role it fills in the wider market for programming languages and different types of communities around them. What kind of stuff is particularly popular among Nim users compared to communities for other languages? What kind of stuff do the people working on Nim want to use it / see it used for?

>I can't currently see what role it fills in the wider market for programming languages "As friendly as python or ruby, but compiles to binary for ease of deployment and speed" is currently an under-served market niche. Rust, Go and Swift are all candidates for the space (with the current defacto standard of friendliness in compiled languages being c++), but I find none is quite a match for me.

Nim is very good for small-to-medium sized services, but competing with Go is difficult for a grass-root language.

Yet, Nim has a tiny memory and storage footprint and runs on microcontrollers thanks to GCC, which makes it ideal for IoT stuff.

Re: Nim core developer wanted

#20

Post by Sir_Substance »

nimmer wrote: post #19
Sir_Substance wrote: post #16

Earlier quoted context omitted.

>I can't currently see what role it fills in the wider market for programming languages "As friendly as python or ruby, but compiles to binary for ease of deployment and speed" is currently an under-served market niche. Rust, Go and Swift are all candidates for the space (with the current defacto standard of friendliness in compiled languages being c++), but I find none is quite a match for me.

Nim is very good for small-to-medium sized services, but competing with Go is difficult for a grass-root language. Yet, Nim has a tiny memory and storage footprint and runs on microcontrollers thanks to GCC, which makes it ideal for IoT stuff.

>but competing with Go is difficult for a grass-root language.

Yeah, I don't have any sound technical reasons for not using Go, I just find it to be somewhat claustrophobic to use. To paraphrase someone else, when I code in Go I feel like Rob Pike is standing over my shoulder muttering "why would you want to do that?" every 10 minutes or so.

Post reply on HN