Absolutely. This game had so much more potential than was realized.

On “the actual environment/background is not made of Lego” complaint: while Bricktales looks neat, its “environment/background” is tiny.
For anyone interested in a more Minecraft+LEGO experience, with an actual world made entirely of LEGO that you can interact with, check out LEGO Worlds. (currently 80% off on steam)

That’s quite interesting.

Although it would need access to an already configured and fully functional environment to actually run this.
I don’t think we’re quite at the point yet where it’s able to find the correct script, pass it to the appropriate environment and report the correct answer back to the user.
And I would expect that when integration with external systems like compilers/interpreters is added, extra care would be taken to limit the allocated resources.

Also, when it does become capable of running code itself, how do you know, for a particular prompt, what it ran or if it ran anything at all, and whether it reported the correct answer?

Thanks for responding, that makes a lot of sense.
I think generally what one gets used to has a big impact on preferences.

I’ll say, an easily accessible, reliable gesture for side menu sounds nice. It feels like this was either abandoned on Android or left up to developers who mostly abandoned it. I remember struggling to get the side menu to trigger instead of back navigation and it not working near reliably enough. So I’ve been trained to always use the hamburger buttons that, ironically, are hard to reach in the top left corner in most apps. To be fair, I feel like I hardly use one menu interaction for every 100 back actions, so the latter being ergonomic is a lot more important to me.
On that point, swipe from left to go back seems quite annoying. I go back all the time, and having to move my thumb across the entire screen is a pain. I almost never need to go forward, so having that be the more accessible gesture seems weird. I’ll concede that having a gesture for it at all is useful and Android should add the option.

I never felt like the swipe to go back is too sensitive, and if you accidentally trigger it, you can simply move your finger back towards the edge before letting go to cancel the action. You can also configure the sensitivity in the settings. The feedback that you’re about to trigger the action is probably not as obvious as on iOS though, and likely less elegant.

I think both Android and iOS would do well to let users customize these interactions more to their own needs.

Could you elaborate on the gestures part?
I remember the opposite, having hated navigating my iPhone for work. I specifically remember swipe to go back not working reliably at all (many apps seemed to just ignore it, others I think configured other actions on that gesture - WTF), so I got into the habit of using that stupid little hard to reach, hard to hit, tiny back arrow that at least worked consistently when you managed to hit it.
I’ve been enjoying Android navigation gestures pretty much ever since I found out they existed.

It might have been a user issue in my case with iOS since I didn’t use it as much, and therefore maybe was simply using it wrong/was unaware of better ways. But I don’t see anything wrong/missing with gestures on Android.

Congrats, you’ve just discovered internet memes.

Love this comment.
Absurd, mysterious, unapologetic.