well, if I have an object on the heap and I want a lot of things to use it at the same time, a shared_ptr is the first thing I reach for. If I have an object on the heap and I want to enforce that no one else but the current scope can use it, I always reach for a unique_ptr. Of course, I know you know all of this, you have used it almost daily for 7 years.

In my vision, I could use a raw pointer, but I would have to worry about the lifetime of every object that uses it and make sure that it is safe. I would rather be safe that those bugs probably won’t happen, and focus my thinking time on fixing other bugs. Not to mention that when using raw pointers the code might get more confusing, when I rather explicitly specify what I want the object lifetime to be just by using a smart pointer.

Of course, I don’t really care how you code your stuff, if you are comfortable in it. Though I am interested in your point of view in this. I don’t think I’ve come across many people that actually prefer using raw pointer on modern C++.

wow! I love the technical part of GUI programming, and that, for me, was a great article! props to alex.

weird. for me, the “hard engine and framework stuff” is the fun part, while the content creation is not boring, but just very hard for me :P

codeberg is great! the community there seems to be interested in growing the platform and developing tools as useful as those on GitLab/GitHub.

I too just turned into a Marxist after finding out about Linux and software freedom in 2020 lol

I think there might be more than a handful of us. Welcome, comrade.

oops, something went wrong while I was typing it. fixed, thanks

there’s also a multiplatform implementation in Go

“bro, just trust me, 2020 2021 2022 2023 will be the year of the Linux desktop!”

you should check out Alba: A Wildlife Adventure, it’s awesome and fits perfectly in your description

cool client! that filesystem interface looks easy to implement for other APIs, neat!

Cool project! That readme gives me a “I like your funny words, magic man” reaction, but I know it’s just because I am not that much into networking and concurrent stuff lol

Those benchmarks already speaks for themselves, and the fact that you are using it in your workplace already shows the awesomeness of your project :)

I would like to point out my project as well:

simpleutils, a small alternative coreutils package. It’s the only actual Go project I have right now and it’s nothing impressive, but I really am enjoying making it. It’s been a blast seeing it being useful in my day-to-day life as well.

It’s supposed to have simple and easy to read code, so that you can easily hack and modify for your own needs :)

quote stolen directly from the repo:

“Science isn’t about WHY. It’s about WHY NOT. Why is so much of our science dangerous? Why not marry safe science if you love it so much. In fact, why not invent a special safety door that won’t hit you on the butt on the way out, because you are fired.” — Cave Johnson (Portal 2)

no, monkeys and apes are cool, cute and badass :)