"easily" solve it.

FTFY

And we're about to enter the fourth rainbow dimension in the next comment...

We're in the third rainbow, keep building more stripes lol

Zig > Rust because actually writing safe Rust code

Start thinking more functional, I rarely have issues with the borrow-checker, or even have to write unsafe. But it obviously depends on the context, when the issue at hand really requires a lot of interior mutability or unsafe can be pain.

I'm also super fast nowadays with Rust, probably faster than with any other language (thanks to great tooling?).

This.

If I'm writing something slightly more complex, ChatGPT(4) is mostly failing.

If I'm writing complex code, I don't even get the idea of using ChatGPT, because I'm only getting disappointed, and in the end waste more time trying to "engineer" the prompt, only to get disappointed again.

I currently cannot imagine using ChatGPT for coding, I was excited in the beginning, and it's sometimes useful, but mostly not really for coding...

Yes

So cancer + a different form of cancer = ...?

I really don't get why you want an editor to be based on DOM, it feels just like sluggish ... cancer...

Or deeply cascaded generic code with a lot of trait-bounds...

yeah mostly (apart from big corporate and all the related issues), most of the stuff feels a little bit bulky/sluggy because of the overuse of web-technology (say Teams or VS Code (while being a great editor there are much faster ones)).

But Github itself is quite convenient for me to use for open source (and for work at that)...

.copy()?

I don't know I really hate when jumping to definitions in libraries, I often just land in the "typings" file. I also think that the type-system is often incoherent, has some weird side-effects and often leads to overengineering your typings... I just generally avoid Javascript based languages (which unfortunately is not really possible in frontend...)

Haha very accurate representation of me xD