Apparently it’s hard to get hired in software. Meanwhile, some of the worst software ever made is being written today. Have you tried using literally any software recently? We’re in this “barely good enough to function while being heavily supplemented by tech support” phase. I guess capitalism breeds incompetence as long as it’s still profitable?

But quiche is tasty!

def path_is_valid(path: Path) -> bool:
    if not path.exists():
        return False
    return True

There’s no reason for this function to exist. Can you see why?

Gleam is cool. I wrote some services with it to see if I wanted to use it for more projects. It seemed like a good option because it would be easy to teach.

Things I like:

• fast build times (I only tested small apps though, under 2000 LOC)
• strong static types
• runs on the BEAM
• easy to learn
• pattern matching
• immutable + structural sharing
• currying (with parameter holes)

Things I don’t like:

• no re-exports
• it’s possible to have name collisions between packages; authors have a gentleman’s agreement to always create a top-level module with the same name as the package
• some standard library APIs seem missing or immature (it’s still pre-1.0)
• it can be hard to get good performance out of idiomatic code for specific tasks (see immutability)
• no format strings; best you can do is "Hello, " <> name. It starts to get cumbersome
• parsing/serialization is all quite manual boilerplate; there’s nothing quite like serde
• no field/argument punning
• no method syntax; you just have to scan the docs to figure out what functions can be used with a given type
• you can’t define the same variant name twice in the same module; I believe this is a limitation in how the types are translated to Erlang records
• you can’t call functions in pattern matching if guards
• you can’t have dependency cycles between modules in the same package
• hard to write FFI correctly; you lose all the comfort of types

I think it would help narrow things down if you described what kind of website you want to build.

They explicitly said they want to build a website. Not that you can’t go far with a Java server + HTML(X) but JS is the de facto standard for interactive websites.

Javascript

WASM

It’s almost like these languages were designed to solve different problems.

AWS CLI is trash compared to gcloud in general.

Ah that explains it.

Are you kidding me? Clap has some of the best documentation of any crate.

Say what you want about DI frameworks, but if I have to remove another fucking global variable so I can write a test, I’m going to cut a bitch.

I know it’s not for everyone, but creating your own nix derivation for software that doesn’t exist yet on nixpikgs is not terribly difficult (for most things).

Damn, the author sure knows how to ramble. No wonder they can’t make a game with Rust, they’re too busy talking about making a game.

If you’re going to actually give a useful critique, organize your thoughts into a succinct narrative instead of making a giant list of rambling bullet points.

Are you responding to my comment or just speaking stream of consciousness?

So… dev blames skill issues on language? Classic.

EDIT: For the record, I’m not saying the author is bad at Rust. I’m saying they’re bad at making games and balancing tradeoffs. They keep saying that they don’t like rust because they just want to worry about making a game, not fighting the language. And yet, they seem to continually make decisions that favor performance over ergonomics. Then they whine about how the Rust community is supposedly pressuring them to make bad decisions.

πfs: The Data-Free Filesystem!

I don’t understand how Agile became synonymous with “useless meetings.” I thought the whole point of Agile was to minimize wasted work.

I don’t think my company uses batch scripts anywhere, but if they did, it would probably be in the app installer for Windows or something.

Oh wow. I hate this lol