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!! 🇧🇷
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
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).
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)
you should check out Alba: A Wildlife Adventure, it’s awesome and fits perfectly in your description
okay, okay, I’ll declare it
Friend[] myFriends() {
return {};
}
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++.