Vortex VS lobster

Hey everyone, I'd like to reintroduce my language Vortex after refactoring it from a tree walking interpreter to a Bytecode VM.

Vortex 2.0 repo can be found here: https://github.com/dibsonthis/Vortex/tree/v2

The static type checking changes are in a new branch until they're tested out some more. If you're interested in taking a look, here's the github repo: https://github.com/dibsonthis/Vortex

My language Vortex was built with side effects like this in mind via hooks: https://github.com/dibsonthis/Vortex

So this is a pretty decent milestone for Vortex. It now has enough features (mostly via libraries I've been creating for it) to be used on a somewhat complex project. I wanted a project to put the language to the test and decided it would be fun to try and create a simple web framework.

Vortex Repo: Repo

Vortex docs (with Getting Started guide, if you want to try it out): Vortex Documentation Vortex Repo: Vortex on Github

Repo: Vortex source code

Docs: Type extension in Vortex Repo: Vortex repo on github

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/

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.

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.

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

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.

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.

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?

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.

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.