Notices by Mike 🐧 :fedora: :centos: (omenos@fosstodon.org)

@monsieurborni @LWN Which comes to the point of project vs product confusion. openSUSE shares a package pool base with SUSE, but the actual deliverables are not 1:1 with SUSE's offerings. As someone who had to explain the value of RHEL versus related projects like CentOS, I would not want the headache that would come from explaining the minute details of the SUSE ecosystem.

It may seem straightforward to us, but many businesses don't make decisions based on our way of thinking.

@monsieurborni @LWN I would say associated is a bit of a broad term. I would go with "confused" instead. For example, let's look at the Red Hat ecosystem:

RHEL, CentOS, Fedora. None of these legally related projects can be confused with each other. The numerous derived projects of Fedora (Nobara, Universal Blue, etc) aren't confused with Fedora proper.

But SUSE and openSUSE? Before even getting to Leap or Tumbleweed one just sounds like a free version of the other.

Currently upgrading to @fedora 40 ahead of GA with updates-testing and RPM Fusion enabled... I'll set the flag myself by saying I expect everything to go fine! So much so I'm not even near my system for the next hour; I'm looking forward to going back upstairs and being greeted by a dormant login screen. And yes, an #NVIDIA device is involved...

I did this going from F38 to F39 as well... But I still take a BTRFS snapshot ahead of time *just to be safe*.

@xarvos @drewdevault Considering the Redis community exists on GitHub and relies on its development paradigm, it's likely to ease the contribution path to the fork. Migrating to SourceHut would require an up-front cost to contribute when you would want folks to onboard as quickly as possible.

@lanodan @drewdevault @synlogic glibc does tend to provide... larger binaries considering how much is going on in the libraries. I'm going to run a quick test comparing GNU libstdc++ to LLVM libc++.

@drewdevault @synlogic Haha, yeah. I figured there are clever ways of getting "as close to the metal" as possible, I was only looking at general usage.

C: printf("Hello, World!\n")

C++: std::cout << "Hello, World!" << std::endl

Go: fmt.Println("Hello, World!")

Hare: fmt::println("Hello, World!")

Rust: println!("Hello, World!")

Something to note is that Golang and Hare are the only two actually static binaries of the bunch. C, C++, and Rust are all dynamically linked to some degree (libc, libstdc++, libgcc_s, libm).

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:

strip -s -o ${lang}_strip
du *_strip

C: 16
C++: 16
Go: 1204
Hare: 220
Rust: 352

#programming #compile #c #cpp #go #golang #hare #harelang #rust #rustlang

@synlogic @drewdevault You both replied while I was in the middle of writing the followup 😅

I wanted to test default compiling behavior, which means for at least C and C++ results in dynamically linked binaries.

Just updated, this is phenomenal! The first and last feature have been on my wishlist for so long, I love that they're finally here 🤩 And they Just Work™️

Thank you @dimillian and all the contributors to the project, you make one amazing application!

From: @IceCubesApp
https://mastodon.online/@IceCubesApp/111582695073908110

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).

#harelang #fedora

From: @omenos
https://fosstodon.org/@omenos/111404268866017469

Alright, my #harelang update for #fedora is posted! Either run a #DNF upgrade or install #hare, hare-bin, and/or hare-src.

The dependency chain has been fixed as follows:

- qbe: (none)
- harec: qbe
- hare: hare-bin
- hare-bin: hare, harec, ~hare-src
- hare-src: (none)

The thought behind this is to allow folks who want to work in a stdlib-less environment can opt out of installing the stdlib in the first place (--setopt install_weak_deps=False).

Getting a little tired of seeing the phrase "freeloader" thrown around online so casually regarding the RHEL situation. Mike McGrath has a post on LinkedIn that details that word out a bit more:

https://www.linkedin.com/posts/mrmikemcgrath_just-some-further-thoughts-on-this-week-activity-7080644263968997376-vrGA

"Finally, I wanted to say something about the term "freeloaders" as I've seen many use it. This is a mostly internal term we have at Red Hat, it looks like at some point it slipped out in the public. So what does it mean?"

1/x