An uneducated thought on the subject. Game development doesn’t cost much more today than years ago. Game companies are just spending more on game development. It’s a choice, not a requirement

I’m just a little skeptical when “snake oil” is barely a euphemism

It’s true. I’m tempted to turn this into some wall art

Honestly, k8s is super easy and very lightweight to run locally if you know the rights tools. There are a few good options but I prefer k3d. I can install Docker/k3d and also build a local cluster running in maybe 2 minutes. It’s excellent for local dev. Even good for production in some niche scenarios

Wow. I 100% agree with you here.

There’s an element of trust when you buy a product. You trust that the product itself isn’t malicious and is intended to help you in some way. E.g. “This food is safely prepared and won’t poison me.” Harvesting user data and advertising really violate that trust.

Though it is worth noting that we don’t buy web browsers. We simply use them for “free“.

This was my only meaningful personal interaction with lemmy.ml that stands out. It was not a good experience. It became very clear, very fast that I would simply have no meaningful discussion with these people. So I left some downvotes on the awful comments promoting violence and stopped engaging.

I haven’t blocked the instance or any users. But i am considering it.

Here’s my random collection of thoughts on the subject.

I have no idea how common it is in general. Seems like some devs build tests while others don’t. This varies plenty on a team level as well as organization wide. I’ve observed this at small to very large companies, though not FAANG where I generally hope and expect that tests are a stronger standard.

I will say that test are consistently and heavily used in every large, open source project that I’ve reviewed. At some point, I think quality test cases become a requirement.

Here’s the big thing. Building automated tests is almost always a wise investment, regardless of the size of the org. Manual testing is dramatically more expensive and less effective than running unit and integration tests. I’ve never written unit tests and not found issues.

More importantly, writing unit tests forces you to write code that can be tested. This is important. IMO, code that can be tested is 1) structured differently and 2) almost always better.

Unit tests protect you from your own mistakes. Frequently. Integration tests protect you from other people. E.g when your code depends on an api and that api unexpectedly introduces a breaking change.

Everybody likes having quality tests. Nobody likes writing tests.

Quality tests are basically a strict requirement for fully automating ci/cd to production. Sure, you can skip tests and automate prior deploys, but I certainly don’t recommend it. I would expect people to be fired for doing this.

Chasing 100% test coverage is a fools game. Think about your code, what matters, and what doesn’t. Test the parts that add value and skip the rest. This is highly related to how writing unit tests change your code.

Building front end tests is inherently hard. It’s practically impossible to fully test front end code. Not even close.

Personally, I like the idea of skipping tests when you’re building a POC. Before the POC is done, you may not know if your solution is viable or what needs to be tested. The POC helps you understand. Builds tests for MVP and further iterations.

Quality ci/cd tests are complimented by quality observability, which is a large and independent topic.

/ ramblings of a tired mind

An interesting discussion! You’re probably right about most Lemmy instances. But it’s entirely possible that some instances are running a modified version of Lemmy that collects more data. And only those admins will understand why. They could sell it as easily as any company.

You need to trust your service providers or accept what they’re doing.

Disclaimer: I don’t yet understand why this is valuable.

I looked through the yaml example a bit. It looks pretty rough. This really makes familiar and readable yaml into much longer configuration. It’s much harder to read. First impression is a pass.

Here’s a random article on the topic to get you started.

Basically Google is destroying anonymous web browsing by embedding finger printing in chromium. Certain trusted servers will track your identity and report whether or not it trusts you.

It’s actually very similar to how Single Sign On and identity providers work. Except you aren’t choosing to use it with a “login with Facebook” or similar button. It’s forced on you by the browser

Hmm I may be confused. Do you believe that software companies shouldn’t be allowed to build and sell libraries? I.e. They should only be allowed to sell full products, ready for an end user?

While you are definitely right, I and many others use yyyy-mm-dd outside of software. And that's when the T becomes super lame.