I agree. I have written server software my entire career, and the need for performance is a corner case in my experience. The never crash in runtime aspect of rust should get much more attention (I know it can panic, but that really never happens in practice unless you use unwrap or smilar).

I also think the defaults are fine, so I was quite surprised to see 14% modify the settings. That is much higher than I expected.

It is always nice to see things progress in the IDE space, even though I must say that since rust analyzer have progressed a lot and JetBrains switched to Rust Rover, I use Rust Rover less now and NeoVim / VSCode more.

No, I think you missunderstand.... A joke is supposed to be funny.

Are they really? Didn't you press a button that said "Buy"? Just because they want things to be something else, doesn't mean that the meaning of the words changed.

My company actually used a whiteboard instead of a DNS for our internal network. We used it as a temp solution during setup, then 5 years later it was still in use. It worked quite well.

It might be interesting to watch the Jackie Chan episode of Every Frame is a Painting, for an analysis of the difference between Hollywood and Hong Kong. This will explain why Jackie Chan is so much better in his Hong Kong movies.

https://m.youtube.com/watch?v=Z1PCtIaM_GQ

I think this is was a great read, since it shows a few important things

• Coming to rust from C is not trivial, you are required to learn a few new concepts (or not really new, but implicit in most languages, formalized in rust).
• When coming from C and you understand the basic concepts, it is easier to learn rust than from many other languages, since you understand what is going on under the hood. Dangling pointers, and use after free aso, are known concepts. C/C++ programmers don't have to fear rust.
• The rust book is a great source of information.

Short about the garage myth https://money.cnn.com/galleries/2011/smallbusiness/1103/gallery.business_creation_myths/4.html

Yes, but all programmers have a love/hate relationship to their languages and toolchains. When I started off back in the 90:s, my prefereed language was Perl, it was amazing, but it was also a nightmare in some aspects... and unfortunately the larger the project the larger the nightmares. I assume Python is probably pretty much the same, even though I have avoided to work with dynamic languages in very large scale projects due to the support nightmares that comes with them. So I assume the Rust cult, is based on the fact that the rust frustration comes a lot from the strictness of the language, but that becomes less of a problem the more you use it (since your skills improve) and at that point the strictness instead gives the reward of reliability and efficiency.

So, while dynamic languages may frustrate you the more you use it (since the projects grows and it is a nightmare to maintain), rust will instead reward you over time.

In short, running an instance requires quite a bit of work, so having a really small instance might be quiet a challenge. Programming.dev is still niche, but large enough to not be a one man show.

Also, if you try it out, then you cannot delete your threads account without deleting your Instagram account and loosing all your photos. So, Welcome to the Hotel California.