WatTyler

I’m learning Rust at the moment and I too think I have some reservations with its syntax. Most of these reservations come from my strong preference for functional programming over OOP.

I am unsure if I like method-syntax period, even if it isn’t inherently OO. Chaining just makes me feel uncomfortable in a way piping doesn’t.

Also it seems idiomatic for values of enumerated types to be written Type::Enum, which seems ugly and unnecessary.

What’d you make of this article?: https://matklad.github.io/2023/01/26/rusts-ugly-syntax.html

{-# LANGUAGE OverloadedStrings #-}

import qualified Data.Text as T (Text)

correctAnswer :: T.Text
correctAnswer = "Haskell"

Reflecting on my first year running solely Linux (as opposed to dual-booting), I think that this culture comes from the fact that, on Linux, problems can more often than not be solved. If not solved, then at least understood. When you want to change something on Windows, or something breaks, you have far less room to maneuver.

When I was a Windows user, I’d barely ever submitted a bug report for anything, in spite of being very tech-literate. It felt hopeless, as my entire experience with the OS was that if a fix would come, it’d have to be done by someone else.

Linux treating its users like adults, produces users who are more confident and more willing to contribute.

Doom Emacs with lsp and rust-analyzer

I recommend Pocket Casts.

Fellow NixOS traveller. I used Nix for work and never saw the appeal of a whole OA built around it but when I saw a tutorial with the declarative config I was instantly sold.