Earlier quoted context omitted.
Honestly memory unsafe languages shouldn't be used with exception of very few corner cases. It's the same reason why we no longer allow cars without seatbelts. You don't go around saying that seatbelts shouldn't be mandatory because you don't need them.
What's with this obsession about what other people do? You don't have to use a memory unsafe language, but others might.
Criticizing Hare language approach for generic data structures
151–160 of 272 posts
Re: Criticizing Hare language approach for generic data structures
#152Earlier quoted context omitted.
Honestly memory unsafe languages shouldn't be used with exception of very few corner cases. It's the same reason why we no longer allow cars without seatbelts. You don't go around saying that seatbelts shouldn't be mandatory because you don't need them.
What's with this obsession about what other people do? You don't have to use a memory unsafe language, but others might.
It has nothing to do with anything you do. It has everything to do with the impact it has on everyone but yourself.
Re: Criticizing Hare language approach for generic data structures
#153Earlier quoted context omitted.
> Why do people spend so much energy shooting down a language nobody uses? If you don’t like it you don’t have to use it. Because this language isn't made by a nobody. It's made by a popular person with a following, so the language _will_ get used by a non-insignificant number of people. And those people _will_ (re)implement all the things that you want a language to have (database connections, networking libraries,…
But why be the one to shoot it down? If the industry makes mistakes, that's not news.
Re: Criticizing Hare language approach for generic data structures
#154Why do people spend so much energy shooting down a language nobody uses? If you don’t like it you don’t have to use it. I would hate to be the creator of Hare and get so much crap for simply daring to exist. He is making a language he likes and wants to use. There are probably some people who like it and find it useful. Good for them! A lot of us have dreams of building our own language. He is following his passions…
> Why do people spend so much energy shooting down a language nobody uses? If you don’t like it you don’t have to use it. Because this language isn't made by a nobody. It's made by a popular person with a following, so the language _will_ get used by a non-insignificant number of people. And those people _will_ (re)implement all the things that you want a language to have (database connections, networking libraries,…
This language is only available on platforms where you are free to choose whatever software you want. If you think a Hare program is insecure, don't use it.
Re: Criticizing Hare language approach for generic data structures
#155Earlier quoted context omitted.
Correct me if I'm wrong, but Hare doesn't say "we need no package manager" but instead "we don't need a new package manager, use the one your OS provides", at least from how I understand it.
That strikes me as another C-ism that didn't deserve to be carried forward into a 21st century language. There's a reason we call it "dependency hell" and not "happy fun fussing with dependency version conflicts among projects that are completely unrelated except that you happen to be using the same computer to work on them time."
Re: Criticizing Hare language approach for generic data structures
#156Earlier quoted context omitted.
What's with this obsession about what other people do? You don't have to use a memory unsafe language, but others might.
All the while I have to use broken, unsafe software on a day to day basis I reserve the right to complain about things that make programs broken and unsafe
I'm not saying that memory unsafety isn't a problem, but if you really want to make software better, you should address the biggest problems first.
Re: Criticizing Hare language approach for generic data structures
#157Earlier quoted context omitted.
We don’t need more memory-unsafe languages with no generics and no functional programming. We just don’t. If it were a toy project for learning and pedagogical purposes that’s one thing but for code that’s supposed to be used in production it’s useless.
You sure speak surely about "us" like there is just one group of programmers out there. Some people love JavaScript, some people love C. Some people only use programming languages, some create new ones. Live and let live, don't tell others what they need.
> but for code that’s supposed to be used in production it’s useless
This isn't about doing what you love - it's about engineering a product, a product that needs to have certain safety, security, and stability guarantees. That's the context of this conversation, and for that purpose, Hare isn't suitable.
Re: Criticizing Hare language approach for generic data structures
#158Earlier quoted context omitted.
But why be the one to shoot it down? If the industry makes mistakes, that's not news.
Imagine if we’d had the opportunity to complain about PHP or JS back in their early days, and had the opportunity to fix some of their awful decisions _before_ they became practically set in stone?
If Drew and Co want to make Hare the way it is, awesome! If you don’t want to use share and prefer something else, great!
Re: Criticizing Hare language approach for generic data structures
#159Earlier quoted context omitted.
What's with this obsession about what other people do? You don't have to use a memory unsafe language, but others might.
I’m allowed to have opinions about what tools should be used for what. I think it’s fair to say you shouldn’t write a production HTTP service in assembly, for example.
Re: Criticizing Hare language approach for generic data structures
#160Earlier quoted context omitted.
What's with this obsession about what other people do? You don't have to use a memory unsafe language, but others might.
A person's actions sometimes have effects on other people. Such as not wearing a mask, for example. Or writing some piece of obscure but critical infrastructure with a memory vulnerability that causes all someone's precious apes to be stolen.
That's pretty rich