SparrowRanjitScaur

Because it tastes good.

It's just a tool like any other. An experienced developer knows that you can't apply every tool to every situation. Just like you should know the difference between threads and coroutines and know when to apply them. Or know which design pattern is relevant to a given situation. It's a tool, and a useful one if you know how to use it.

Extremely misleading title. He didn't say programmers would be a thing of the past, he said they'll be doing higher level design and not writing code.

Maybe as a social signal for other humans.

That's funny, but I love content created by individuals and small teams, especially the maker/engineering channels. I'll take that over corporate produced media any day, even if it means paying a corporation to serve that content to me.

They also have one of the best business models for creators, meaning people producing content can do it full time and make a good living off of it, instead of doing it as a charity and producing mediocre quality videos.

I agree with all your points, not using the service is absolutely an option. I suggested paying for premium because that was the option that made the most sense to me. I hate ads and love YouTube. For me, the value I get from a subscription is much higher than other services I pay for. I'm subscribed to probably 500 YouTube channels and probably watch between 50-100 hours of content per month.

Like many other business they offer an ad funded service and a paid service. I understand this is Lemmy, and people love getting things for free. But if you don't like ads, have you thought about paying for the service?

Maybe now's the best time to mix things up. This could be the last election before the fall of the democracy, why not go all out? I'm actually really excited for this move, and despite a little uncertainty at first I'm fully onboard.

I'll reiterate, if it was a null pointer exception (I honestly don't know that it was, but every comment I've made is based on that assumption, so let's go with it for now) then I absolutely can blame C++, and the code author, and the code reviewer, and QA. Many links in the chain failed here.

C++ is not a memory safe language, and while it's had massive improvements in that area in the last two decades, there are languages that make better guarantees about memory safety.