> PS: In practice if your project funded by publisher it means that you as developer will make less money from a game than Valve.

So that essentially means a publisher takes even more than valve, while doing almost nothing.

Publisher gives you development budget because most games arent made by one person and you need money. At least $50,000 - $150,000 for a small PC games.

Then publisher takes 70-90% before recoup and 50% afte of what remain after VAT, refunds and Valve's 30%.

Problem is when you spent $100,000 and sold lets say for $400,000:

* Valve gets $133,000

* Publisher gets $100,000 + $90,000

And you get $90,000 and real number would be much worse because VAT, refunds, etc.

Oh, dont forget to pay your taxes on $90,000. Good luck!

No it's not. There is a even a wikipedia page for it: https://en.wikipedia.org/wiki/Economic_moat

A moat is protection so you can keep your ARR up or increase it over years. Arguably only google have a moat with their TPUs. NVidia has a moat. But the others who just train some models on NVidia hardware have no moat.

I have used in my life many different Linux distributions: Slackware, Red Hat, Ubuntu, Debian (professionally or privately). My private choice is the only one not driven by marketing: Debian.

You have three main Debian releases:

  SID (if you need to be as close as possible to upstream versions)

  Testing (the same as above but a few days after SID)

  Stable (you sacrifice the latest software versions for insane stability)

Which one did you use ?

And please don't mix Debian and Ubuntu.

Canonical is commercial company driven by profit (and CEO's bonus).

Debian is driven by community and (mostly) engineers.

I used Stable and SID. The reason I mixed Debian and Ubuntu is because I perceive the root of shittiness to be apt and how it can, and often does, poison your system.

What do you mean by "poison" ? Be specific. Very specific.

running apt install can brick your system in both large ways, it just stops booting. Or small ways, breaking existing packages or a myriad of other ways. On the one hand this is the fault of apt itself. It allows package scripts to do way too much. And on the other hand package maintainers write honestly brain damaged scripts a lot of the time.

Sounds similar to my experience with other systems (like Red Hat). Amazing - you've just realised that IT systems don't always work. Welcome to IT world !

"welcome to IT world" is just dismissive and needlessly aggravating. Just because systems can break doesn’t mean we should throw up our hands and accept the terrible state Debian package management is in. Debian-style package management has specific architectural issues, combined with maintainers writing poor package scripts, that make breakage seem far more common than it should be.

I asked you to be very specific. And you refused. You are criticizing "apt" for "specific architectural issues" but it is still very, very vague. Once again - be specific please. Can you? What exactly are the "specific architectural issues" ?

If you worked for a politician, you would look like hired by PR agency to throw a sh..t on someone else. I believe (and hope) you are not ?

I didn't refuse, I gave a very specific answer, namely that debians package manager can brick your system at any time because there are literally no safety mechanisms. That is the "specific architectural issues" I'm talking about. What more do you want? The code to prove it? Here it is: https://gist.github.com/rowanG077/27cd0a9417dd48593e63018783...

You are right: you didn't refuse, you are cheating (especially people who don't understand nuances)

You provided a content of a deb package that is intentionally malicious. It is like a saying that car from specific car manufacturer is dangerous for people. When asked "why" your answer is: "Because you can suddenly turn the car and hit people waiting at a bus station".

BTW, I hope you already know that in i.e. Red Hat you don't need rpm package to brick your system. It's much, much easier.

You are a troll.

I've lived on Debian since day dot, never really had an issue. Biggest gripe with Debian is that it's /too/ stable!

Back in the 1990's I was fond of it for the community spirit, the attention to detail, the way things "just worked" even it had a particular take on some things. Over time it felt like it became burderned with design-by-committee decisions, maintainers leaving and abandoning packages faster than they could replace them, and just a bit too political.

For me this is all about team size. It works if you have small teams, maybe max 6 people. But anything above 8-10 this is a total no go. Because management tasks just are not able to be done well at that point.

You right, but there is a very real coordination problem above the team when you're doing bigger things. I've recently experienced an organization with approx. 25 teams of 5-8, and because of their organization they had way too many concurrent initiatives. It was very hard to effectively swarm multiple teams on fewer (bigger) projects.

How do you suppose people in those times would even meet some love interest in a far away place, aka the next town over?

Sure it can be zero. It can even be negative. As larger player numbers, including piracy, are a natural form of marketing. That means it's not hard to see this additional marketing could lead to larger sales figures compared to if piracy was not possible.

Yeah that's mostly a US problem. Not a Healthcare problem in general.

Good luck to you if the prompt is written by health insurance.

Emotional support. Some human doctors absolutely radiate confidence and a kind of "you're gonna be okay" attitude. For me, this helps a lot. I'm not sure a machine can do this.

But I hate if the human doctor "radiates confidence" when I know he is not doing the proper scan, because I have to get back with worse symptoms first for him to take it serious. I don't need emotional support from a human doctor. I need the adequate scans and a proper analysis. I am pretty sure that a competent human will be still way better than AI, but AI even now will likely be better than a doctor not really paying attention.

You can hopefully get emotional support from your loved ones. If not a coach seems much more appropriate.

In Germany I learned module arithmetic at something like 13 years old in high school. I also find unsigned much more intuitive and in my code only use sized signed when I absolutely have to. Which is not often. Only in languages that offer automatic big Ints I just use ints, like Python and Haskell.

Rust is evolving too fast? Rust is evolving EXTREMELY slowly. I dare say even slower than C++ or Python.