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?).

Yes, and Rust with incremental compilation is pretty fast to iterate as well, as long as you don't use massive libraries/build-scripts etc.

Yeah the strict type-system of Rust is great at finding issues.

I think when understanding, that bash is basically only programs with parameters ([ is a program that takes all kinds of parameters and as last parameter ]) then bash is quite ok for stuff that doesn't need a lot of algorithms, i.e. passing the in and out from one program to another. But as soon as there's basic logic, You'll want to use a fully-fledged programming language.

Also the maintainability aspect: You can just start using fancy stuff you never want to use in bash and it can slowly grow into a library or application or something like that.

Btw. I have started a syntax-sugar library/crate that creates typing information for all kinds of programs via the builder-type-state-pattern, so that you don't always have to look up man etc. and that it should be more convenient to execute programs (not open sourced yet, and low priority for me as I'm working on various other exciting projects currently)

Yeah as weird as it sounds to use a "low"-level systems programming language such as Rust. Rust works surprisingly well as "script" language. (And you don't have to deal with the ugliness of bash, admittedly though, that bash is quite a bit more concise when using a lot of program executions and piping the results etc.)

Yeah but why do I have to use an IDE to generate getters and setters in the first place? It just adds up to more mental overhead, because my brain has to process this boilerplate somehow, even if my IDE can generate it (I know it's simple code, but it's even simpler to not have that boilerplate code at all).

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...

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

Is there really no native (SwiftUI) iOS app?

Yeah, this is the way how to interact with it. It makes sense as well, because it's only predicting the next word based on the previous words, so it had can in hindsight find a lot more stuff and in general be smarter about it.

I think at the time where this will be relevant, it will be implemented (I don't think it's that difficult), I don't think it will be that difficult. Apart from that a lot of the instances already have manual sign up, and it's working well so far AFAIK. (The beauty of decentralization is, that this work will be distributed among all the different instances, whereas the number of instances is ideally proportionally growing like the userbase). But yeah ideally it wouldn't be necessary and some kind of smart algorithm (AI? captcha?) will decide whether the user is allowed to register (as it is currently with captchas)... But we'll see...

Now combine it with Nix and you're on the happy path

Yeah I totally agree, I have mixed feelings about the competition part (which is obviously true especially when looking into the valley). Being passionate really counts (in the form of (not just) trying to achieve high quality open source software).

But if it's just about getting a good pay-check I think it's not too difficult to get a relatively well-paid job if it's not in the "hot" zone (i.e. boring jobs are ok).