labor unions based as always!!! brasil!! 🇧🇷
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.
labor unions based as always!!! brasil!! 🇧🇷
Celeste screenshots, because every scenario in that game is beautiful. And it’s one of my favorite games of all time.
Here is my favorite one:
Yeah, a lot of lemmy users were already into free software as a whole and liked lemmy because it’s libre and federated. So it’s only natural you see the focus on software freedom everywhere.
I just think that we should strive to use libre alternatives, especially when they are as useful/better than closed source ones.
The philosophical side of free software is much more important to me than anything else. For me, it’s not just about using open source software for the sake of it. It’s about software freedom.
But I don’t go around telling everyone to use open source or die. If you just don’t like the libre alternative and prefer using closed source software, whatever. If there isn’t a general reason to use a closed source software, I’ll just point out the libre alternative (or try to convince that a somewhat inferior libre alternative may not be that bad) :)
not open source, unfortunately.
maybe you’re looking for something like LiveSplit?
Torch Browser is not open source, and it still is based on chromium. It’s the worst browser combination possible.
Falkon is pretty cool! I prefer using qutebrowser if it’s gonna use QtWebEngine anyway. It is slower and less featureful than the main browsers, though. If you don’t mind it, I’d say go for it!
I didn’t know about Dot Browser, but it looks… unfinished? It’s based on Firefox, so that’s cool. But it seems someone would be better off just using something like LibreWolf (or Tor if you actually want some privacy).
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 [email protected] 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.
test my own PWA of websites I’m developing
changing browsers or keeping both open breaks the workflow and sucks. and it’s pretty damn slow for me too
BookWyrm has a barcode scanner on its UI, which redirects you into the scanned book title (if it’s registered in the “databases” BookWyrm pulls from)
Parlera is an amazing and fun party game
straight to the point cooking recipes
actual skirts and dresses being a common piece of clothing for men. I love how they look and feel
poverty is prohibited.
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++.