NimForUE
lobster
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
NimForUE
-
Nim Versions 2.0.4 and 1.6.20 released
Glad to see that the windows executables are working again.
I had tried a little while ago to test things out on my windows machine after seeing the NimForUE project (https://github.com/jmgomez/NimForUE) and was sad to see that my computer would auto-mark any nim binaries as malware and delete them. I wasn't too invested so I just shrugged rather than looking for too many workarounds.
-
Unity plan pricing and packaging updates
For people scared off by C++ and who want faster recompile times, check out the Nim bindings [0]. Check out his Twitter/X account [1] for plenty of cool things it brings to the table.
[0]: https://github.com/jmgomez/NimForUE
[1]: https://twitter.com/_jmgomez_
- Nim Lang for Unreal Engine
-
Ask HN: Why did Nim not catch-on like wild fire as Rust did?
I started using Nim because i wanted to port some of machine learning models written in python with the idea of making them more portable. It was a lot of work as community is relatively small and a new user would end up writing a lot of code.
But Nim has a pretty solid standard library with clearly written code and an awesome community to help with problems. I generally read a lot of standard library code to expand my knowledge of language and discover common patterns which repeat themselves in a lot of real world problems.
C inter-op is really first class, and as far as i know it has one of best C++ inter-op as well, you can take a look at: https://github.com/jmgomez/NimForUE for a real world example.
I use Nim for my work in both professional and personal capacity and also have written about some of it at https://ramanlabs.in/static/blog/index.html
-
Anybody still trying to make Godot 4.X bindings?
I've switched over to Unreal and helped out with NimForUE early on. If you have any interest in Unreal, you should check it out since it's in a really good state. It does assume knowledge of Nim, Unreal, and C++ to really get the most out of it.
-
Purpose of NimScript vs nim
In NimForUE, we ran into issues with nimble early on, so we resorted to using nim for the build scripts because we needed to do code generation gymnastics to work with Unreal's build system and Nim's C++ codegen. The Nim compiler has had some patches since we first worked on the build system, so maybe if we had to do things over again we could go back to NimScript.
- Nim 2.0.0 RC2
-
Epic’s Verse Programming Language Reference
They would be better off just paying the guy developing NimForUE some money and making it first-party.
-
The Icculus Microgrant is giving out 250 dollar grants to open source projects, please brag about your project(s) in this thread so I can see them!
NimForUE is an Unreal Engine plugin that aims to replace the verbose and tedious C++ with the concise and clean Nim language, supporting blueprints too and giving hot reloading and native speed performance. https://github.com/jmgomez/NimForUE
-
The Verse Calculus: a Core Calculus for Functional Logic Programming (more details on Epic's new language)
(https://github.com/jmgomez/NimForUE)
lobster
- The Lobster Programming Language
-
The Neat Programming Language
I think lobster does this.
"Compile time reference counting / lifetime analysis / borrow checker."[1]
"Reference Counting with cycle detection at exit, 95% of reference count ops removed at compile time thanks to lifetime analysis."[1]
[1] https://strlen.com/lobster/
-
Why does Rust need humans to tell it how long a variable’s lifetime is?
There is another language, Lobster, that uses lifetime analysis like Rust, but IIUC infers lifetimes completely automatically. It looks like the idea is still experimental - I'm interested to see how it goes.
-
What are some must have built-in modules in your opinion/experience?
I think the ability to open a window and do graphical stuff is actually pretty underrated in core language functionality. There's a few game-oriented programming languages like Lobster that put windowing and graphics in the core language functionality, and I think it's pretty neat. The biggest downside is that it's a lot to bite off, because you'll probably want to have standardized API functionality for a whole host of things like font rendering, image loading, etc.
-
Minetest: An open source voxel game engine
The actual game itself, yes. Based on this open source project though which provides the language its written in and core engine tech: https://github.com/aardappel/lobster
-
Plane - FOSS and self-hosted JIRA replacement. This new project has been useful for many folks, sharing it here too.
I'm keeping an eye on Lobster though. It fixes most of Python's problems. It's way faster, has proper static typing, the import system is sane, etc.
-
Using a borrow checker to track mutable refs in a GCed FP language?
Lobster (https://strlen.com/lobster/) appears to at least do lifetime analysis to reduce refcounting. I'm not sure about automatic interior mutability. I feel like there's a keyword here that can help find other compilers with similar features.
-
What would make you try a new language?
Also, can I introduce you to https://strlen.com/lobster/, a garbage collected language made for game development by (and primarily for) the one and only Wouter "aardappel" van Oortmerssen?
-
In a custom typed imperative programming language, what should the compiler do next, after resolving variable references?
I would like to make it work to some degree like Rust with a borrow checker, and have optional static typing (with type inference wherever it can). Other sources of inspiration, lobster lang, and dart. It is going to (eventually...) compile to several places like dart (browser, iOS, android, linux, etc.). After I've created the AST, I've gone straight to code generation, because that's the easy part IME. But now have to insert the "middle" and do typechecking/borrowchecking/inference/other checking. This is for an imperative-style language.
-
Features you've removed from your lang? Why did you put them in, why did you take them out?
Over the ~12 years of Lobster (https://strlen.com/lobster/) 's existence, features that were removed (in this order): * Lexical scoping. * Icon style backtracking. * Small-talk like syntax. * Dynamic Typing. * Multimethods. * Frame based state (like FRP). * Co-routines.
What are some alternatives?
Gwion - :musical_note: strongly-timed musical programming language
cakelisp - Metaprogrammable, hot-reloadable, no-GC language for high perf programs (especially games), with seamless C/C++ interop
neverengine
treesheets - TreeSheets : Free Form Data Organizer (see strlen.com/treesheets)
bu - B)asic|But-For U)tility Code/Programs (in Nim & Often Unix/POSIX/Linux Context)
language-ext - C# functional language extensions - a base class library for functional programming
nimrodot - Nim Godot 4.x GDExtension wrapper (Proof of Concept)
mun - Source code for the Mun language and runtime.
axiom - A 64-bit kernel implemented in Nim
swift - The Swift Programming Language
vos - Vinix is an effort to write a modern, fast, and useful operating system in the V programming language
cligen - Nim library to infer/generate command-line-interfaces / option / argument parsing; Docs at