Lobster VS QB64

Lobster mentions (21)

• 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/. - Source: Hacker News / 4 months ago

• 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... Source: about 1 year ago

• 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. Source: about 1 year ago

• 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. Source: about 1 year ago

• 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. Source: about 1 year ago

QB64 mentions (0)