wow! I love the technical part of GUI programming, and that, for me, was a great article! props to alex.
oh yeah, I heard about the already forked projects before, certainly awesome that people already have that option. I do use Aniyomi, and it's pretty damn good.
For some reason I've never felt like I needed extra features that the main project didn't have, so I've never looked out for forks. But looking at some of the forks right now they seem pretty good as well and do have features that would be super useful to me. Certainly will try it out.
FOSS is so amazing.
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
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:
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.
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
you should check out Alba: A Wildlife Adventure, it's awesome and fits perfectly in your description
how is reading the communist manifesto being a tankie?
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++.