alt Hacker NewsI'm a long time Unity developer that in the past year picked up Godot. The speed at which Godot loads compared to Unity is staggering, it's just so much faster. When I returned to Unity I raised that my flow state was constantly being broken in a way that it wasn't when using Godot.
Entering flow is one of the beautiful things I love about programming. And being knocked out of it often feels like a physical jolt.
Lobster seems to take the idea of optimisation and speed to new levels. Entering and remaining in flow must be even easier. First though, I'll need to put the time into learning enough to be able to do it!
Replies
Yeah,
I'm working on an indie game project and just got frustrated with Unity, I'm porting everything over to Godot.
I even learned about using Kotlin with Godot today [0] and I am really hopeful this is stable (it seems so), because I favor a more functional style of programming and C# ends up making everything 5 times more verbose than Kotlin.
Thanks for mentioning Lobster. This guy seems to have learned many lessons of language simplification and design. Looks like a promising language and I wish it success.
Ref: https://aardappel.github.io/lobster/language_reference.html
So true.
Recent changes to Xcode have meant that on device debugging now launches WAY slower for me every time.
Once it’s going it’s fine. But an extra 20 seconds every time you start the app just kills things for me. It was never instant but now it’s trash.
I get taken out of flow every time I submit my prompt to Claude. How’d you work around that?
Lobster doesn’t seem that different from Lua in that regard? I won’t say it isn’t impressive, but I’m having a hard time believing the hard part of this thing was calling from an interpreted to a static language.
Edit: I was mistaken about what Lobster is (potentially compiled instead of jit), but the main point stands.