IMO the best way to start in a new language is to rewrite some of your previous projects in that language.

I generally start out by rewriting a couple simple 1-3 function console apps, basic leet code stuff like; palindrome, fizzbuzz, reverse an array in place, etc, and some simple unit tests for them. Then I go ahead and rewrite some of my previous projects or uni assignments in that language.

At that point I generally have a good understanding of basics and have an idea of how to approach a new project. When I got to this point in rust I then started on threading, async, why it’s easy to return a String and an ordeal to return &str, etc.

I think I understand this;

cancel -> submit the POST request and cancel -> undo this thing. maybe they shoulda just used submit & cancel or cancel & exit instead.

Mojo is a Python superset, Python is written in C therefore mojo is written in C.

I don’t know what that rust library they benchmarked against is but given that they claim to have performed 50% better I would be sceptical. Given that most sources benchmark rust, C and C++ at about the same level.

Either I come up with a new project or I rewrite an old project in the new language.

I used to do those old school language tutorials where we start with how to write a variable, then how to write a function, etc. but I think that’s better for complete beginners just starting out.

Would it be better to use A’s and B’s? We could half the necessary length of a symbol by assigning a certain combination of A’s and B’s to a symbol. And if characters take up too much space we could use 1’s and 0’s instead!

I didn’t know we even had dynamic compiled languages but a quick google search tells me Lisp counts. Wonder if Musk actually knew that or if this screenshot is taken mid dunning-kruger.

My most loved and hated feature in PHP is associated arrays. I’ve seen an associated array that uses 16gb of memory before, it was as beautiful as it was horrifying.

If you think this is more structured than traditional SQL, I really disagree. Is this a select * query, it’s ambiguous. Also what table is being queried here there’s no from or other table identifier.

Ahh yes, the privacy company which required you to give them your email in order to download the browser.

My brain goblin is a big fan of performance. Recently I reviewed a teammate’s code. It was a small 100ish line PR and he calls the same function twice in a row with a tiny variation. My brain goblin went “you could consolidate these into one call”, “since it’s only one call you could inline it”.

A couple hours later when he came to ask me what I’m smoking I realised my proposed solution had more LoC and was more complex to read. If we needed better performance, step 1 should’ve been to offload this task to an API that wasn’t made with python. Not to mention the next thing this API does is string manipulation and then write to file.

Well if you can’t break out of anything then I guess you will just have to return instead. I’m sure this will result in code that is much easier to read.

When I went rooting around to find it. I figured it was some QA process that starts 5 seconds after the video loads (the timer seems to be async and the code sends a promise off while it waits). Of course, it’s all minified JS so it’s a huge pain to read.