How doeas NIM differ from Mojo programming language?

One of the main ideas behind mojos syntax is: Mojo aims to be compatible with Python, enabling an easier transition from Python to mojo. Similar to C++ to C, it is a superset of Python. In other words, you can copy and paste your existing Python code into a mojo file and it should run. If you w

Atlas shrugged...

Will atlas support custom build commands? Currently nimble does not allow you to override the build task. Or is it just recommended to use a custom task name for customized/advanced builds?

Mojo Language: Similarities/Differences with Nim, Potential Lessons for Adoption

> If you're looking for a REPL, there's inim which is pretty adequate. It's not > the same sort of REPL as you'd expect with a LISP lang where you can do > everything in it, but it's more like the Python or Node.js REPL where you can > write statements and evaluate them It's not the same as a P

Mojo Language: Similarities/Differences with Nim, Potential Lessons for Adoption

One benefit you get with a REPL, or specifically JIT, which Mojo apperas to exploit from their Keynote () is they can dynamically "autotune" functions to perform faster for the hardware the code is being executed on (i.e. search for an optimal choice for the tile_factor

Mojo Language: Similarities/Differences with Nim, Potential Lessons for Adoption

> for bad looking but perfectly working C auto wrapping you can try futhark My point is, this feature is not officially supported by the compiler team or the language itself. Futhark is not as easy to use as a zig @cImport or C++ #include > Nim is a compiled language and REPL is not really some

Mojo Language: Similarities/Differences with Nim, Potential Lessons for Adoption

I wanted to highlight the Mojo language, as I really think there is some impressive engineering work being done here. It could be a bit early to say, as I personally haven't tried the language yet, and the compiler is not open sourced (but is planned to be). Here is a link to a HN discussion:

Hot reload & Alternatives - Mac Support (ARM and x86)

This is for the development process, aiming to obtain an interactive experience. This would not be there for production. I may want to do something similar with a plugin system, if that's possible, though I'm not planning to implement that. At the moment the only way I can see how to do the abo

Hot reload & Alternatives - Mac Support (ARM and x86)

Thanks for your reply. I've tried out dynlib and hit a snag. I'm writing a game. Is it possible to link to a dependency/nim module dynamically? I'm trying to emulate Handmade Hero's setup. That is: * Call A the executable file (main) * Call B the dynamic library where my game-code exists *

Hot reload & Alternatives - Mac Support (ARM and x86)

Hot code reloading simply doesn't work on either of my Macbook Pros (ARM and x86). Does anyone know why? It seems there's quite a few issues discussing this. Since I'm not expecting hot reloading to be patched anytime soon. Can I just use std/dynlib on a dynamic library built with nim for the fu

Why is nimscript interpreted and why the limitations?

Genuinely interested about the design decision for nimscript. Why is it interpreted? Is it not possible to compile the nimscript to a local binary and then execute, or JIT compile it? Or is this too complex to implement for little benefit?