• 12 Posts
  • 179 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2023

help-circle
  • I feel like the cool features I think of are generally Linux features

    • You can periodically have scripts run by setting up from jobs(e.g. make a temp folder that deleted it’s contents every 24hours or update the programs on your computer at midnight everyday)
    • Ricing your desktop, I’ve never done it but there’s an insane amount of customization you can put into how your computer looks. Just look at unixporn(it’s just nerds showing off their desktops) to get an idea
    • Getting used to using your package manager, it’s extremely nice to not have to open up a browser to download software but to have one place to look every time you want to find software (try using the apt search command)

    Picking Ubuntu was a really good choice for testing out how it’d feel to use a Linux distro. That isnt to say there aren’t things that the average user wouldn’t like when using it. If you need to use office software, there is Libre office suite, but it’s just not as widely used or feature full as the Microsoft suite. Or if you’re trying to sync files across devices, I swear every linux user has a different means of doing so (one place to start would be Syncthing).

    I hope you have a great experience and that you learn a lot from it.










  • Reading the rust book is a great use of your time. Rawdogging is a good method if you’re just concerned with things you’re working on. You can also read documentation on different things that you may not be working on, but know is a gap in knowledge. For me that was the async and tokio books as async rust is a bitch.

    A lot of rust libraries use the same approach by having some type of “book” for documentation. I treat them like normal reading, so I’ll be out and about or just sitting and I’ll pull one out and read it leisurely. It’s another way I’ve found to learn by osmosis. Doesn’t even have to be something I’m working on, just something interesting. It sounds like you’re doing what interests you, and that’s what’s important.












  • I think one thing to mention is that Rust is highly specific in what it does. In most of the examples you mentioned, string types, tokio::main, you can essentially just say that rust is more explicit. When initializing an integer variable in C using int, it’s not specified what use the integer is or whether it’s signed or not. i32, uint16_t you can see how it’s specified. Using tokio::main before your main function just specifies that you’re using the tokio asynchronous executor for your async code. In the case of string types, they all have different implementations which just help with being specific.

    The reason I like Rust is because I know what’s happening when I read it. Did I have to read the whole async book to understand how the tokio::main stuff works? Yes. But now I understand exactly how it works. The problem I have with using Javascript is that it doesn’t have that high amount of explicitness(is that a word?). At the end of the day, if you’re using it for a personal project or you’re arguing for language supremacy, it really just comes down to personal preference.