Welp... got distracted with learning #harelang last night and started porting my password/otp manager "fulla" to hare from go. So far I only implemented parsing an .fsv file.
Looks like I get to be impatient waiting for 32-bit arm support in hare as well now.
Personally, I have nothing against the emergence of new #programming languages. This is cool:
the industry does not stand still;
competition allows existing languages to develop and borrow features from new ones;
developers have the opportunity to learn new things while avoiding #burnout;
there is a choice for beginners;
there is a choice for specific tasks.
But why do most people dislike the :clang: #clang so much? But it remains the fastest among high-level languages. Who benefits from C being suppressed and attempts being made to replace him? I think there is only one answer - companies. Not developers. Developers are already reproducing the opinion imposed on them by the market. Under the #influence of hype and the opinions of others, they form the idea that C is a useless language. And most importantly, oh my god, he's unsafe. Memory usage. But you as a #programmer are (and must be) responsible for the #code you write, not a language. And the one way not to do bugs - not doing them.
Personally, I also like the :hare_lang: #harelang. Its performance is comparable to C, but its syntax and elegance are more modern.
And in general, I’m not against new languages, it’s a matter of taste. But when you learn a language, write in it for a while, and then realize that you are burning out 10 times faster than before, you realize the cost of memory safety.
Decided to try and compare the general base program size of several languages. I wrote a handful of Hello World programs, and stripped them of everything. Here's the final results in KiB:
Writing my first #Zig code, and I can already tell this is going to be a struggle. So much syntactic sugar. Makes #Rust look easy to write in comparison.
All I want is a better C. So far #HareLang seems like the winner there.
#Perl still takes the cake as the worst language I had to write today. Though shoutout to the Perl fediverse community for being helpful people!
This week we’re joined by @drewdevault, talking about the Hare programming language 🐇
We discuss Hare (of course), why he’s so passionate about all things open source, the state of the language, fostering a culture that values stability, and oddly enough — what it takes to make a peanut butter and jelly sandwich 🥪
For the #hare crew who have given this a try, thank you! I'll have an update published soon. I'm trying a newer commit so updating is seamless, but probably not the very latest commit (looks like it's got some problems).
@drewdevault Does #harelang need any kind of build loop structure? I'm getting it prepped for packaging in #Fedora but I'm not 100% sure if I should be doing a manual loop (bootstrap then rebuild with self).
When setting HAREC to "hare" it kind of explodes 😅 If no loop is necessary then this is pretty much good to go. I wasn't sure if the "harec2" task was just for validation purposes, and if the "harec" package users can install should always be the C-based bootstrap compiler.
I wrote an SDF ray-marching engine in #harelang. This is the first time I've got so far in writing a rendering engine, reminds me of when I was 15 or so experimenting with #PovRay. That's what got me into programming in the very beginning. Hare is a fun little language. Thanks @drewdevault.