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.
Personally, I also like the :hare_lang: #harelang. Its performance is comparable to C, but its syntax and elegance are more modern.
That exactly why I like #nimhttps://nim-lang.org/ --- it's IMHO much more mature than Hare and offers more targets (e.g. compile to C, C++, JavaScript, WASM or various embedded devices).
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:
Back to work on packaging @hare for @fedora, let's see how much I can bang out in a few hours. The resulting artifacts are going to be fairly simple, but not particularly packager friendly. That's a day-2 project.
New cross-compile meta packages for #GNU and #LLVM dependencies.
I've created a convenience script, harex, to switch to non-GNU toolsets. Just set HARE_XCOMPILE_TOOLCHAIN to "llvm". User specified env vars will still be respected.
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 🥪
I'm really bad at both Hare and regex, but I assume the stdlib should not be crashing when I put in something that is perfectly valid in Python and regex101, right?
Abort: regex/regex.ha:516:41: slice or array access out of bounds
Aborted (core dumped) #Hare#HareLang#AdventOfCode