If it’s in the minified front end code it’s already client side, of course you don’t show it to the user but they could find out if they wanted to. Server side errors are where you really have to watch out not to give out any details, but then logging them is also easier since it’s already on the server.

Well, I think for a 9 year old it’s fine. I think the stage where you would run into issues is when trying to get into “actual” software development, where the flexibility in scoping and typing afforded by Python can lead to some bad habits (e.g. overusing global/shared variables, declaring them from within functions, catching errors late instead of validating data first, …)

I don’t have a ton of experience with it but I think C# strikes a pretty good balance between strictness and beginner-friendliness. Modern Java isn’t all that bad either, though it doesn’t have very good options for fun things to build. But again, I don’t think this necessarily applies to a child; I’m an educator at a university so both my target audience and point of reference are freshman compsci students.

I was brought up on Python and also do not like it for a variety of reasons, both practical and by personal preference. I also have the opinion that if you are trying to learn software engineering it is not a good language to start out with, despite it being so easy to pick up at first.

Some people try to use Python’s popularity as a counterpoint, and while it does show that my view is a minority opinion, it’s not a very convincing argument for the language itself.

It’s not code anyone is supposed to read or work with, this is the result of minifying it to be as short as possible. And from a quick glance what’s happening is that a variable is set to correspond with whether the cursor is currently over a certain element. Not sure what’s funny about this?

deleted by creator

A lot of compound words are actually multiple tokens so there’s nothing stopping the LLM from generating the tokens in a new order thereby creating a new word.

At least for Kotlin it’s literally just syntactic sugar for getter and setter methods. I really like them, don’t get me wrong, but it’s just the bottom approach masquerading as the top approach

I mean that’s literally what it is from a psychological perspective. Your brain doesn’t reward you for the mere act of finishing a task, so it’s basically impossible to find motivation for it unless it ticks at least one box in your reward center.

isn’t that OP?

Ah yeah, I see that too now. Maybe it was just a temporary issue…