Gleam v1.12 • Hacker News Board

Re: Gleam v1.12

#41

Post by samdoesnothing » Wed, Aug 06, 2025, 9:27 PM UTC

ForceBru wrote: post #34

ASalazarMX wrote: post #9

The official website has an interesting footer > As a community, we want to be friendly too. People from around the world, of all backgrounds, genders, and experience levels are welcome and respected equally. See our community code of conduct for more. Black lives matter. Trans rights are human rights. No nazi bullsh*t. On one hand I applaud that their community standards are inclusive, but on the other hand, it shou…

> Shouldn't be that blatantly ideological, it's not a political platform Yeah! This always stands out like a sore thumb on the website. Like _yeah_, all of it should go without saying! You're a freely available programming language, of course everyone can use it! Of course everyone is welcome! Does a hammer care about your gender or race? No, anyone can use it! It's also very weird and a little childish to specifical…

[flagged]

Re: Gleam v1.12

#42

Post by buzzerbetrayed » Wed, Aug 06, 2025, 9:29 PM UTC

akkad33 wrote: post #32

ASalazarMX wrote: post #9

The official website has an interesting footer > As a community, we want to be friendly too. People from around the world, of all backgrounds, genders, and experience levels are welcome and respected equally. See our community code of conduct for more. Black lives matter. Trans rights are human rights. No nazi bullsh*t. On one hand I applaud that their community standards are inclusive, but on the other hand, it shou…

But this is not very relevant to the release announcement?

When you put distracting things on your homepage, don't be surprised when they're distracting

Re: Gleam v1.12

#43

Post by giraffe_lady » Wed, Aug 06, 2025, 9:35 PM UTC

samdoesnothing wrote: post #41

ForceBru wrote: post #34

Earlier quoted context omitted.

> Shouldn't be that blatantly ideological, it's not a political platform Yeah! This always stands out like a sore thumb on the website. Like _yeah_, all of it should go without saying! You're a freely available programming language, of course everyone can use it! Of course everyone is welcome! Does a hammer care about your gender or race? No, anyone can use it! It's also very weird and a little childish to specifical…

[flagged]

HN itself has quite a lot of "nazi bullshit." You don't usually, regularly see people being virulent about it but people frequently endorse policies that would absolutely have fit cleanly into the historical nazi party's platform. Things like race science and eliminationist policies against the homeless, anti-immigration stances, homo- and transphobia are particularly popular. People here are normally "polite" about it and we seem to all have decided that means it doesn't count. It does count.

Re: Gleam v1.12

#44

Post by smithcoin » Wed, Aug 06, 2025, 9:36 PM UTC

bmacho wrote: post #38

thijsvandien wrote: post #18

Earlier quoted context omitted.

Error(error) -> Error(error) has strong if err != nil { return err; } vibes, and I don't consider that a good thing.

No, it doesn't have strong if err != nil { return err; } vibes. Pattern matching on Ok/Error is one of the best known error handling, while go error handling is one of the worst. They are about as far from each other as possible.

Interesting, I find myself thinking the exact opposite.

Re: Gleam v1.12

#45

Post by no_wizard » Wed, Aug 06, 2025, 9:37 PM UTC

Alupis wrote: post #2

Some highlights from this release are listed here[1]. The best part of Gleam in my opinion is the language's design. It's just so elegant to read and write. Take this example code snippet from the release notes: pub fn find_book() -> Result(Book, LibraryError) { case ask_for_isbn() { Error(error) -> Error(error) Ok(isbn) -> load_book(isbn) } } It's a trivial code snippet, but I'm finding this kind of "first class" pa…

snake case convention is the only thing that always feels odd to me.

Perhaps its because I deal in TypeScript all day, every day, but it never stuck with me.

That said, small price to pay for a very nice runtime!

Re: Gleam v1.12

#46

Post by giraffe_lady » Wed, Aug 06, 2025, 9:37 PM UTC

lpil wrote: post #16

ASalazarMX wrote: post #9

The official website has an interesting footer > As a community, we want to be friendly too. People from around the world, of all backgrounds, genders, and experience levels are welcome and respected equally. See our community code of conduct for more. Black lives matter. Trans rights are human rights. No nazi bullsh*t. On one hand I applaud that their community standards are inclusive, but on the other hand, it shou…

> It shouldn't be that blatantly ideological from the get go. It's just another programming language, not a political platform. It's first and foremost a community, and it's important for communities to have clear a code of conduct and moderation of that code. There are lots of languages without community, Gleam is not one of those.

Gleam is an incredible technical achievement and the community an amazing social one. You should be proud of both, thank you for your clear vision and commitment on this issue despite so much consistent external pushback.

Re: Gleam v1.12

#47

Post by lpil » Wed, Aug 06, 2025, 9:42 PM UTC

Alupis wrote: post #21

lpil wrote: post #14

Earlier quoted context omitted.

> Gleam seems to have a lot of obvious influences from Rust, and the creator is a rust dev. Hi! That's me! Gleam the language doesn't have any Rust influence really. It's a happy accident that some of the syntax ended up looking the same, but that's likely due to both being inspired by similar languages such as OCaml and the C family. Most the syntax and the semantics predate Gleam's compiler being rewritten in Rust.…

> The build tool is a rip-off of Cargo for sure though. Hey, great artists steal, as the saying goes... It's all shaped up really nice. I'm a big fan of Gleam and your work in general.

Thank you, very kind.

Re: Gleam v1.12

#48

Post by lpil » Wed, Aug 06, 2025, 9:43 PM UTC

giraffe_lady wrote: post #46

lpil wrote: post #16

Earlier quoted context omitted.

> It shouldn't be that blatantly ideological from the get go. It's just another programming language, not a political platform. It's first and foremost a community, and it's important for communities to have clear a code of conduct and moderation of that code. There are lots of languages without community, Gleam is not one of those.

Gleam is an incredible technical achievement and the community an amazing social one. You should be proud of both, thank you for your clear vision and commitment on this issue despite so much consistent external pushback.

Thank you, you are very kind. I am extremely proud of the community, they are wonderful lot.

Re: Gleam v1.12

#49

Post by giraffe_lady » Wed, Aug 06, 2025, 9:46 PM UTC

steve_adams_86 wrote: post #10

Alupis wrote: post #4

Earlier quoted context omitted.

I have not used it at all, but Gleam does have a javascript target in it's compiler/build-tool. So in theory, you can write Gleam (strongly typed, etc) and produce js. I've exclusively used the BEAM/Erlang target so far - but the js community within Gleam seems quite interesting.

I've been considering trying this, but my team already struggles to properly adopt TypeScript so I'm fairly sure introducing Gleam would cause a few people to throw me out a window.

Gleam is so much smaller and easier than typescript and the type system works harder for what it is. TS gets you because it is similar to javascript in some ways that make it easier to start the transition. But a complete js -> ts transition is about as big a deal as it would be from js to any other language, except you can use the same external libraries.

Re: Gleam v1.12

#50

Post by Alupis » Wed, Aug 06, 2025, 9:49 PM UTC

no_wizard wrote: post #45

Alupis wrote: post #2

Some highlights from this release are listed here[1]. The best part of Gleam in my opinion is the language's design. It's just so elegant to read and write. Take this example code snippet from the release notes: pub fn find_book() -> Result(Book, LibraryError) { case ask_for_isbn() { Error(error) -> Error(error) Ok(isbn) -> load_book(isbn) } } It's a trivial code snippet, but I'm finding this kind of "first class" pa…

snake case convention is the only thing that always feels odd to me. Perhaps its because I deal in TypeScript all day, every day, but it never stuck with me. That said, small price to pay for a very nice runtime!

I come from a background where everything is camelCase. Naturally I wrote my JSON this way as well, among other things.

Switching to snake_case was challenging at first - I kept writing things in camelCase. Now, I've become pretty fond of snake_case and have a tough time going back into environments that require camelCase - funny thing, that is.

Thankfully Gleam's build tool/language server has a fairly strongly opinionated formatter built in, so it will let you know pretty quickly and help you fix it.