Viewing profile — haxscramper

As someone who has been writing nim for many years now, using grep, rg, and various other search tools I can say that I've never had any issues with finding things I wanted. This i…

This is not really true, most of the times the discussion goes like this Q: "Why haven't you implemented feature X -- python has it, so nim should too" A: "Nim is not python, it is…

Somehow I missed this (very noticeable actually) non-algorithmic toggle button until I saw your comment, so many thanks for mentioning this.

Right now we are not forking "the language" as a collection of ideas etc. as you seem to think. Instead we are doing a much simpler thing - we are forking "the code". Of course for…

On how: The "method" is to just respect the future contributors from the start, instead of waiting for ten years until someone tells you to write better messages. Why can't it be a…

That does not magically rewrite all previous commit messages, although apparently the improvement is present https://github.com/nim-lang/Nim/commits?author=Araq - most of the total…

Commits message guidelines are a part of the contribution guidelines and are available in the documentation (linked in the GitHub page). Concrete application of said guidelines can…

There is no singular "story" here, mostly several former contributors decided for one reason or another (of course there are a lot of small "stories" behind this, but writing them …

We are certainly not opposed to this, although some of the more fundamental structural changes in the codebase might temporarily hurt the stability - this was one of the friction p…

That is a correct interpretation, we decided some humor won't hurt at the start, and it certainly wasn't as venomous (aka "death to nim") as parent comments suggested

!: this is mostly a personal note although I am one of the nimskull contributors For now the aim of this project is first and foremost refactoring and making it easier to contribut…

I think better phrasing would indeed be something like "several former core developers" - of course we can't really measure up to the size of the original community, and don't yet …

Actually the phrasing in the readme is not correct - I will change it later, but now I want to say that the objective is not deleting "much" of it, but rather cleaning up old and d…

No, never. Actually the most problem I've ever had with this feature is seemingly unending discussions that come up in almost every single HN discussion ever, like https://news.yco…

I can't remember exact place where I've seen this discussion (I think it was on the nim IRC), but if I recall correctly, the original line of thought with nim was to take C (becaus…

Adjacent comment already has a list of concrete libraries/frameworks for large number of areas, so I just want to mention that nim has a very good metaprogramming capabilities, and…

This way you can write json literals in the code, and it will look just like regular json. For serialization and deserialization stdlib uses `to/load/store` proc names. import std/…

It does affect identifiers, built-in keywords and type names in the same manner, though it is completely beyond me why anyone would write 'tY_PE Position = tUPLE[x, y: iNt]'. If we…

Another nim & python thread that has not been mentioned yet here https://news.ycombinator.com/item?id=28506531 - project allows creating pythonic bindings for your nim libraries pr…

> Do you enjoy the tabs vs spaces debate? How about single quote Vs double quotes? Ugly inconsistently styled code? Nim solved tabs/spaces debate by allowing only spaces. Single/do…

While I don't claim to have a comprehensive numbers, I did a quick `rg` on a full clone of nimble package list, and found that macros constitute approximately 0.4% of all definitio…

Using nim pattern matching library to implement simple dataflow programming DSL.