> Just replied to another comment recommending C. Can you help me understand which core principles C would help to refine i.e. what am I leaving on the table if I go with a Rust or C++?
In the other thread you mention features. I suggest C because of its "simplicity", that is, its lack of features. It really is a thin abstraction on top of assembly. C's closeness to the hardware is edifying.
Moreover, since the goal is learning, History is quite relevant. Languages evolve in the context of their predecessors. You probably already know this for typescript since it is so close to JavaScript. But how do C++ and rust relate to C? And how does Go relate to C++ and C?
Languages always involve tradeoffs. For example, a language that checks memory bounds at runtime (Go) uses more CPU cycles than one that doesn't (C). A compiler that does checks is more complex than one that doesn't. Language features can help with safety (rust), but then the language takes more time to learn. Complexity can be hidden (Go garbage collection) to make up front learning easier, but this can make the language less flexible or more difficult to debug. Complexity can be exposed later but then the language learning curve is lengthened.
I'm not suggesting you go become a C pro, but learn enough to shoot yourself in the foot. It will help contextualize the features of these other languages and give your more mental tools for decision making in your own code.
And 18650 powered flashlight, such as one made by Fenix. (Also note they make a keychain flashlight which could stand in for the device in another toplevel comment.) The 18650 is more your standard flashlight though. I used to have a flashlight, who doesn't? But now I consistently take one when hiking, looking for stuff, etc. The brightness and even cast of the beam, plus the long battery life, mean it has a lot of utility for working at night or in a poorly lit space. You can use it as a lantern, too, just stand it up or hang it. Bonus points for USBC charging.
An insulated mug. I didn't think it would change the way I drink tea. Now I can bring it to my desk and take small sips. This helps me get back to work and stay focused, and probably reduces my overall consumption because I don't feel like I have to chug while warm and then go brew more.
I find IRC bots useful although they certainly qualify as dumb. They meet the user where the user is. They are generally just a dressed up command-line interface. I've written some chat bots pre and post NLP explosion — In this era I've had luck with mild NLP mappings to commands, GPT3 not required. Just get you some verbs and objects.
In the other thread you mention features. I suggest C because of its "simplicity", that is, its lack of features. It really is a thin abstraction on top of assembly. C's closeness to the hardware is edifying.
Moreover, since the goal is learning, History is quite relevant. Languages evolve in the context of their predecessors. You probably already know this for typescript since it is so close to JavaScript. But how do C++ and rust relate to C? And how does Go relate to C++ and C?
Languages always involve tradeoffs. For example, a language that checks memory bounds at runtime (Go) uses more CPU cycles than one that doesn't (C). A compiler that does checks is more complex than one that doesn't. Language features can help with safety (rust), but then the language takes more time to learn. Complexity can be hidden (Go garbage collection) to make up front learning easier, but this can make the language less flexible or more difficult to debug. Complexity can be exposed later but then the language learning curve is lengthened.
I'm not suggesting you go become a C pro, but learn enough to shoot yourself in the foot. It will help contextualize the features of these other languages and give your more mental tools for decision making in your own code.