HNHacker News
TopNewBestAskShowJobs

lkjaldfwltjohw

11 karma · joined November 7, 2023

submissionscomments
lkjaldfwltjohw··on Gleam: a type safe language on the Erlang VM
At a glance the type system is quite barebones and nominative.

I'd like to see Gleam add support for structural types and maybe set theoretic [1]

[1] https://arxiv.org/abs/2302.12783

lkjaldfwltjohw··on Why Golang instead of Rust to develop the Krater desktop app
ORMs manifest when the language doesn't have native query constructs.

C# (LINQ) or F# (Query Expressions) come to mind. Sadly not much else.

lkjaldfwltjohw··on Why Golang instead of Rust to develop the Krater desktop app
Meh, even the traditionally non-gc languages ones have used reference counting (gobject, Objective-C MRC) or even GC (gcnew C++/CLI)

I admit that STW GC pauses sicken me, so I avoid them on principle.

lkjaldfwltjohw··on Why Golang instead of Rust to develop the Krater desktop app
No, they are obviously ignorant to type theory
lkjaldfwltjohw··on Why Golang instead of Rust to develop the Krater desktop app
> Understanding ownership transfer and management can be one of the most confusing and complex aspects of Rust. It is crucial to consider the program's execution flow and manage mutable and immutable variables in memory to avoid getting lost in the code. Mastering this, along with working with threads, was one of the most time-consuming tasks for the team.

I want to add that "ownership" isn't new. When working with systems languages without a GC, ownership was always there, you just kept track of it mentally, rust may be the first to make you aware of it by enforcing it at the compiler level, essentially making you aware that you are doing something stupid.

Adopting rust's ownership model was truly "zero cost" coming from a C/C++ background as we were already doing it.