Hello,
This is my first post to this Rust community and I am happy to introduce myself and discuss what I love about this language, but first a little about myself.
I’m Alice, Fluffy to most, and she/her are my pronouns. I’m from the UK. I got a little boy who love like crazy. I’m Autistic, suffer from cPTSD and I also 🩷 Rust!!
Rust I feel appeals to Autistic people because of it’s focus on accuracy and correctness. It’s a common feeling people have about the language. But as the type of person I am I love it.
I began learning it in 2023, before this I was using C++. Rust showed me the importance of error’s as values and helped improve the quality of my code.
Currently I’m writing a game-engine as a hobby. The game-engine is a work in progress (WIP) and I have only just begun it’s development. Since the game-engine will natively support various platforms. To ensure consistency I’m writing all the platform specific code manually and building my own custom standard library for my engine, loosely based on the actual Rust standard library.
Right now I have the code in place to create/remove directories and to create, delete, write, read and set file pointer location. Convert UTF8 to UTF16 and output to the console in Unicode (Windows C API uses UTF16) and heap functions to get the process heap and create and delete memory dynamically.
Next will be the ‘config.json’ for which Serde will be used. Then the logger, and so on.
So it is a WIP but it’s fun and given my conditions allows me to do what I love, writing Rust code.
Thanks for reading!!
Alice 🏳️⚧️
Personally, I’ve found excessive nesting to be problematic, because each level of nesting is an invariant, which might not fit your application anymore as it evolves.
For example, let’s say you’ve got “application.logging.enabled” as one flag.
Then you decide to introduce more extensive telemetry in the next release. So, if you go with ‘proper’ nesting, you’d have to call the flags for that:
Theoretically, you’d have to move the logging config also under that nesting level, but that would break existing configs.
Obviously, this example is relatively easy to avoid by not introducing the nesting in that case.
But you can find other examples where you might have called that level one way and then later ended up introducing a bunch of configs under a different name, where it could’ve also been under. That will confuse end users who try to configure your application and also might make it just more difficult to remember or guess config names in general, when you also have to guess the intermediate levels.