OSM is such a badass project
Otaku, gamer, self-taught programming student and professional procrastinator from Brazil. In fact, I am procrastinating at this very moment. I love boomer shooters too.
OSM is such a badass project
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
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.
well, I just came across the article on Mastodon and wanted to share it. I mean jeez, imagine sharing and wanting to discuss interesting topics just for fun?
and I posted the article on !technology@beehaw.org and then cross-posted it here, because I thought it was also an interesting community to discuss it. I saw a bunch of people cross-posting it elsewhere, so if you’re seeing it a bunch of times then it’s probably because those communities probably also have something in common with the article. I personally think every community have different people and different discussions to have, so I don’t see it as particularly bad.
oh sorry! forgot about it adding a description. will do next time.
“I SWEAR BRO JUST ONE MORE LANE, ONE MORE LANE WILL BE ENOUGH!!!”
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)
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++.