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 🏳️‍⚧️

  • sugar_in_your_tea
    2·
    8 hours ago

    At my company, we picked an awful middle-ground: write Python like it’s Java, but don’t use correct type hints.

    In our project:

    • everything is a static class - from a.b.c import C; C.thing() instead of from a.b.c import thing; thing() or import a.b.c; c.thing()
    • use declarative dependency injection frameworks instead of duck typing
    • force rigid class structures, but don’t do typing properly, and don’t necessarily keep the calling signature of the base class methods (i.e. break SOLID all over the place)
    • use decorators to hide magic (i.e. implicit is better than implicit and other Zen of Python violations)

    We get the worst of OOP and functional styles with none of the benefits by abusing Python’s flexibility.

    But hey, I guess it works…

    • mholiv@lemmy.world
      3·
      8 hours ago

      That’s terrible. I noticed that there is a certain type of programmer. Normally they went to Uni in the late 90s or early 2000s and their entire education was focused around Java.

      They went out to get a job writing “Enterprise” Java for 10 years.

      This programmer then tries to learn another language, but because all they know is Java everything ends up looking like and structured as Java.

      I’ve seen this developer over and over again. It’s possible for them to overcome Java Brain but it’s rare.

      I bet one of these types of programmers is or was the technical lead of that project.

      I noticed something similar when I worked on a Scala project in the past. Yes I know we’re on the JVM, but we don’t need a data deconstructor factory when flatmap is right there.

      • sugar_in_your_tea
        3·
        6 hours ago

        Nailed it.

        We outsourced the project at the start. My company picked the tech stack (Python + Postgres, pretty sensible) and the consultancy company separately, so the consultant re-skilled to deliver the project. They were Java devs, so the whole project looks like Java.

        The code was massive when I joined, and now it’s infeasible for me to fix, even if I can get buy-in.

        The worst part is that we decided to go async on new microservices, so they pulled in different Java BS in the name of “quality.”