this post was submitted on 16 Feb 2024
37 points (97.4% liked)

Programming

17406 readers
89 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

Hare is a systems programming language designed to be simple, stable, and robust. Hare uses a static type system, manual memory management, and a minimal runtime. It is well-suited to writing operating systems, system tools, compilers, networking software, and other low-level, high performance tasks.

you are viewing a single comment's thread
view the rest of the comments
[–] rockSlayer@lemmy.world 6 points 9 months ago (4 children)

The language itself seems pretty heavily inspired by rust. On that note, why in the hell wouldn't they use ownership for memory management?

[–] AriosThePhoenix@feddit.de 20 points 9 months ago* (last edited 9 months ago) (2 children)

Funny you mention Rust - one of Hares lead devs (and I believe the original creator), Drew DeVault, has been pretty vocal about his dislike for Rust, especially in the low-level and Linux kernel world. Here's an article by him about the subject:

https://drewdevault.com/2022/10/03/Does-Rust-belong-in-Linux.html

IIRC, Hare has more of a "trust the programmer" approach to things such as memory management. As a programmer who who trusts no one and especially not myself, I don't think Hare is for me (and i disagree wit a lot of Drews points.) But that's just my two cents. The language itself seems pretty neat still, but I think it's got very different design goals

If there's one thing the history of computers has shown us beyond the shadow of doubt, it is that programmers cannot under any circumstance be trusted to manage memory.

[–] rockSlayer@lemmy.world 8 points 9 months ago (1 children)

I suppose I can respect that opinion on memory management, but also disagree that we should always trust the programmer. I was mostly commenting on the syntax, if it weren't for the fact that I was on the website for Hare I would have thought it was Rust.

It's got a lot of good ideas from what I saw in the quick guide, but I feel like lifetimes are the next step for memory management in general. If they really want manual memory management to be default, they could continue to flip Rust and make a safe attribute for functions

[–] Lmaydev@programming.dev 8 points 9 months ago

I think the exact opposite to them. Humans are almost always the weakest link. The more you can automate the better.

load more comments (1 replies)