Official Fediverse (e.g. Mastodon) account?

Lol, "unearthed bad behavior" vs "Various extremely sincere complaints". It's the other way round. ;-)

Official Fediverse (e.g. Mastodon) account?

Actually here, watch That should give you a picture of how a very prominent post-Elon program got rolled out.

Official Fediverse (e.g. Mastodon) account?

Twitter's gotten a substantially better UI in the form of , which you can run locally or from a private server, and which is written in Nim. It's good! None of the fediverse frontends are nearly as good. There's also a lot of drama that you could've had fun fo

A seasoned programmer's take on Nim's docs

> I just did not understood what you mean by : > > The code is too flat > > What do you suggest to change for the code exactly ? Sorry, I wasn't clear. The contrast of the code on the background is too low.

Official Fediverse (e.g. Mastodon) account?

What's wrong with Twitter? I haven't been using it for years. Did it become even worse somehow?

Official Fediverse (e.g. Mastodon) account?

Nah, I'm a Musk fan.

Official Fediverse (e.g. Mastodon) account?

With Twitter burning to flames, it would be nice to have a presence in federated social media. Currently, the only way to find nim-related posts is hashtag search.

Array concatenation

Makes one wonder why `toSeq` is called `toSeq` and not ``@``...

The state of GPU codegen with Nim (bonus: LLVM JIT codegen)

Thanks for the detailed reply! > Instead of hardcoding a libLLVM-15.so version, you can autodetect it with > {.passl: gorge("llvm-config --libs").} That's handy to know. > LLVM IR by necessity is very stable and hasn't been changed for years. The C > API is also fully-featured (compared to man

A seasoned programmer's take on Nim's docs

> Markdown has become nearly universal with a massive ecosystem around it Do you mean CommonMark, GitHub Markdown, Pandoc Markdown, Reddit Markdown, …?

A seasoned programmer's take on Nim's docs

> > Add a page navigation section with links to the headings on the page > > That is more difficult than you think to do it right with Nimib currently. Indeed it is not straightforward right now, but recently I more or less settled on an api, so it should not be too difficult to do (if someone w

A seasoned programmer's take on Nim's docs

Thanks for the feedback. No problem, I have exposed the material very roughly and was expecting that kind of reaction. I may change the style of the dark theme Nimib CSS, I have simply used the default one. I am personally more accustomed to dark theme and often toggle the CSS with my Firefox e

A seasoned programmer's take on Nim's docs

The doc generation actually supports [RST and markdown at the same time](http://nim-lang.github.io/Nim/markdown_rst.html).

A seasoned programmer's take on Nim's docs

> (Beware, I'm Dutch, thus direct in a way considered rude by many.) I only read the template section, that took some effort. The dark theme and the choice of colours and contrast levels make it very hard to read. The

A seasoned programmer's take on Nim's docs

Being more feature complete might be a good reason to to support it, but it shouldn't preclude supporting what people know. And it's easy to have different definitions of 'failed'; very few new projects use RST and Markdown has become nearly universal with a massive ecosystem around it that is

A seasoned programmer's take on Nim's docs

> Some really good stuff in there. When I was thinking about fixing the > problem, I was reminded that neither I, nor most people new to the community, > know RST at all. In most environments, when people are documenting code for > extraction, they're using markdown. I am not going to take the t

A seasoned programmer's take on Nim's docs

@dlesnoff Some really good stuff in there. When I was thinking about fixing the problem, I was reminded that neither I, nor most people new to the community, know RST at all. In most environments, when people are documenting code for extraction, they're using markdown. I am not going to take the

Trying to make a lexer, stops if it hits an operator.

Oh that's so funny. When your code had all the whitespace removed, I did my best guess to reformat it, and there was one ambiguity. I had added an extra tab to the else in the `of uk` block, and it worked for me, except for the bug where it requires the input text end with whitespace

Nim v2: what would you change?

You can use `using ...` to make proc declaration less verbose as well : type MyType = object using self : MyType proc doStuff*(self; arg0: int, arg1: string, arg3 : float) : string = discard Run

A seasoned programmer's take on Nim's docs

Indeed OpenSSL has a lot of sharp edges, that's why I use [libsodium](https://libsodium.gitbook.io/doc/) :)

A seasoned programmer's take on Nim's docs

This is never stupid to repeat basics : I thought I wanted to write a tutorial on macro and template programming, but ended up making a mix between the last three. Its not easy to find the correct tone when we don't k

A seasoned programmer's take on Nim's docs

> In short, as long as a modest bit of work is put into optimization, this will > never come close to being anybody's bottleneck. And it's worth doing to avoid > the MANY issues I've seen over the years where people didn't give it a second > thought, and ended up totally owned. This should be d

Trying to make a lexer, stops if it hits an operator.

You can add code blocks with triple backticks, and check that the formatting worked with the 'preview'