Earlier quoted context omitted.
What the heck man? This doesn't match my experience at all. And I can't find your username on neither matrix nor discord. Did you just found a chance for a sucker punch and took it? I bet Zig is the wonder land.
It does fit my experience and you'll find me as a lurker in the discord. Though I'm not surprised you haven't noticed this. The mod in question is a master in gaslighting. I'm not sure I would have noticed if I didn't have personal experience with this level of manipulation. It's not a coincidence you see the same name pop up, every time someone gets bullied out of the discord.
Nim Version 1.6.6 Released
91–100 of 116 posts
Re: Nim Version 1.6.6 Released
#92I started programming in Nim around 2015 and still write code in it from time to time. At this point I would have a tough time suggesting the language to anyone for much. While you can certainly accomplish almost any programming task with Nim, how much frustration you will encounter fighting the compiler and broken / under-specified language features and semantics might be a turn-off. There are other major warts with…
its true that leadership does nothing and development is stuck, but even in this state nim is probably enough for most people. > how much frustration you will encounter fighting the compiler and broken / under-specified language features and semantics might be a turn-off. unless you limittest generics, most people wont even encounter this. > My advice would be to look elsewhere. that would imply that there is a bette…
I don't think my totally normal usage of generics for type safety could be called "stretching the limits." My usage of generics includes using a parameter [V] for OpenGL meshes to introduce type safety with the vertex type. I'm pretty sure that's perfectly normal?
Recently one of my friends tried compiling my project - pan[1] on Windows, and for whatever reason - it doesn't work! stating that it "cannot instantiate 'V'", whatever that means. I've had this error annoy me many times before, but I have no clue what triggers it or how to reproduce it reliably. Call this a 'stable implementation.'
[1]: https://github.com/liquidev/pan [2]: https://github.com/liquidev/aglet
Re: Nim Version 1.6.6 Released
#93Earlier quoted context omitted.
It does fit my experience and you'll find me as a lurker in the discord. Though I'm not surprised you haven't noticed this. The mod in question is a master in gaslighting. I'm not sure I would have noticed if I didn't have personal experience with this level of manipulation. It's not a coincidence you see the same name pop up, every time someone gets bullied out of the discord.
But those who got banned didn't they ignored the warnings, continued flaming and insulted other users? Will you pretend that people who behave themselves get banned?
Have you ever dealt with someone that constantly lies and misrepresents your opinions to make you look like a villain? Have ever gotten frustrated, because the person you're arguing with is constantly shifting the goalpost to their benefit? Have you ever said something needlessly rude out of frustration? How would YOU react, if after dealing with all this disingenuous bs, YOU get told to watch your tone or you get banned for being toxic?
The justifications after a ban always make logical sense, true. But if you read through the logs with even a little bit of empathy, it becomes clear very quickly who the toxic person in those interactions is.
Edit: I'm not talking about a specific person getting banned. This happened numerous times, including newcomers.
Re: Nim Version 1.6.6 Released
#94Earlier quoted context omitted.
You're proving my point. Any criticism must be an attack (e.g. suckerpunch in this case) and must be met with heckling and banning. Zig is no wonderland, but I haven't experienced things like the creator of the language personally engaging in almost every drama and banning community members.
Why am I not allowed to be suspicious, with a new account doing advertising for Zig while creating controversy? How about you provide more details, instead of throwing accusations?
This is the type of insecurity and paranoia one can expect to find when hanging out in Nim discord.
Re: Nim Version 1.6.6 Released
#95Earlier quoted context omitted.
But those who got banned didn't they ignored the warnings, continued flaming and insulted other users? Will you pretend that people who behave themselves get banned?
Oh, they absolutely ignored warnings and used rude insults. And if you were in their situation, you would have too. Have you ever dealt with someone that constantly lies and misrepresents your opinions to make you look like a villain? Have ever gotten frustrated, because the person you're arguing with is constantly shifting the goalpost to their benefit? Have you ever said something needlessly rude out of frustration…
Re: Nim Version 1.6.6 Released
#96Earlier quoted context omitted.
Why am I not allowed to be suspicious, with a new account doing advertising for Zig while creating controversy? How about you provide more details, instead of throwing accusations?
> advertising for Zig This is the type of insecurity and paranoia one can expect to find when hanging out in Nim discord.
Re: Nim Version 1.6.6 Released
#97A bit off-topic, but I'd like to see a language à la rust+gc, with pattern matching, traits, and the functional stuff rust got right, but without all the worries of lifetimes, and maybe some easier trait management (function signatures become very ugly imo). I've heard the claim that lean is going in this direction.
You might enjoy Cone, which is basically Rust with GC (and RC, and any other strategy).
Re: Nim Version 1.6.6 Released
#98Earlier quoted context omitted.
Why am I not allowed to be suspicious, with a new account doing advertising for Zig while creating controversy? How about you provide more details, instead of throwing accusations?
> advertising for Zig This is the type of insecurity and paranoia one can expect to find when hanging out in Nim discord.
Re: Nim Version 1.6.6 Released
#99Earlier quoted context omitted.
> many of the more senior community members or those who have been around for a bit have migrated there It's true that compiler developers like krux, Clyybber, saem migrated to nimskull, I don't disagree. > but there are only a handful of folks remaining that have been around for more than a year or two But I totally disagree with your false statements about "senior" community members (those who don't do compiler dev…
Most of the "senior" community members who have migrated to NimSkull are those who liked to work on the compiler. The ones who remains using Nim are those who like to write libraries and projects. I've yet to see anyone create a library or project with NimSkull, although that might be because I'm not too exposed to it. I would love to be proven wrong, but for the time being NimSkull looks like a good idea if they can…
Re: Nim Version 1.6.6 Released
#100I started programming in Nim around 2015 and still write code in it from time to time. At this point I would have a tough time suggesting the language to anyone for much. While you can certainly accomplish almost any programming task with Nim, how much frustration you will encounter fighting the compiler and broken / under-specified language features and semantics might be a turn-off. There are other major warts with…
> many of the more senior community members or those who have been around for a bit have migrated there It's true that compiler developers like krux, Clyybber, saem migrated to nimskull, I don't disagree. > but there are only a handful of folks remaining that have been around for more than a year or two But I totally disagree with your false statements about "senior" community members (those who don't do compiler dev…
Are there experienced programmers in the Nim community, sure? Are they able to fix Nim with Nim's leadership in place? Doubtful in my mind based on history.
Also, I apologize if it seemed like I was evangelizing Nimskull or suggesting folks switch to it. I agree it is in no shape to serve a replacement for Nim presently, and may not ever be.