fesc

no profile record

comments

2 वर्ष पहलेdiscuss

> for a few thousands users

It makes absolutely no sense to base this decision on the number of users. We have some applications that don't even have 10 users but still use k8s.

Try to understand the point that was made in the original comment: Kubernetes is a way to actually make infrastructure simpler to understand for a team which maintains lots of different applications, as it can scale from a deployment with just one pod to hundreds of nodes and a silly microservices architecture.

The point is not that every application might need this scalability, no the point is that for a team needing to maintain lots of different applications, some internal, some for customers, some in private datacenters, some in the cloud, Kubernetes can be the single common denominator.

Hell, I'm a hardcode NixOS fan but for most services, I still prefer to run them in k8s just as it is more portable. Today I might be okay having some service sitting on some box, running via systemd. But tomorrow I might want to run this service highly available on some cluster. Using k8s that is simple, so why not do it from the start by just treating k8s as a slighly more powerful docker-compose.

2 वर्ष पहलेdiscuss

I disagree, seems like a pretty standard structure of one directorz per app and inside that subfolders for configuration, secrets, opaque various data. Not complicated at all really.

2 वर्ष पहलेdiscuss

Why is it obviously wrong?

During a duration of time it is okay so say an amount of energy (MWh) was produced, right?

2 वर्ष पहलेdiscuss

> We sometimes call merges "commits" in Git, and, again, leaky abstraction and overloaded term.

You abuse the term leaky abstraction here. That isn’t a leaky abstraction as a merge commit is literally a commit, isn’t it?

2 वर्ष पहलेdiscuss

Some YouTuber talked about this and I think they were pretty on point: Of course for consumers this could all happen in some app on the phone.

But a 3rd party app will always be less integrated, have less permissions than functionality included by the manufacturer.

And for all this AI integration wide access is pretty much required as you'd want it to access your photos, notes, all kind of apps, etc.

This way manufacturers would have too much leverage over companies developing that kind of AI, as they could always develop better features than them with their own AI agent.

I think Apple Watch is a pretty good example of that already. Third party watches will never be as good as Apple Watch just because Apple won't let them.

2 वर्ष पहलेdiscuss

  Testcontainers is awesome and all the hate it gets here is undeserved.

  Custom shell scripts definitely can't compete.

  For example one feature those don't have is "Ryuk": A container that testcontainers starts which monitors the lifetime of the parent application and stops all containers when the parent process exits.

  It allows the application to define dependencies for development, testing, CI itself without needing to run some command to bring up docker compose beforehand manually.
  
  One cool usecase for us is also having a ephemeral database container that is started in a Gradle build to generate jOOQ code from tables defined in a Liquibase schema.

2 वर्ष पहलेdiscuss

Yeah but once per page, which is why it is okay to disable cache as the author wanted to simulate a cold load of each of those pages.

2 वर्ष पहलेdiscuss

Honestly I don’t understand why not more people use a GUI for git.

What you describe would be 1 Minute of work and maybe 10 clicks with a very low probability of shooting yourself in the foot in Tower.

3 वर्ष पहलेdiscuss

What would "integration tests" (that you don't write) look then in your opinion?

I ask because in my team we also a long time made the destinction between unit/integration based on a stupid technicality in the framework we are using.

We stopped doing that and now we mostly write integration tests (which in reality we did for a long time).

Of course this all arguing over definitions and kind of stupid but I do agree with the definition of the parent commenter.

3 वर्ष पहलेdiscuss

The same reason why most people stopped manually editing some random files via FTP to do deployments: to get a proper reproducible, automated and monitored production environment.

3 वर्ष पहलेdiscuss

But on the other hand it seems that produce is of higher quality in NL on average than in DE.

3 वर्ष पहलेdiscuss

I stopped reading when the solution for DNS was AWS and the solution for stateful sets was AWS EC2.

This is just a very weird comparison. Seems like the author doesn’t understand why people run K8s.

Of course they also “managed” several k8s clusters using… wait for it… AWS.

I’d say, when you are all in AWS, then fine don’t use k8s. But you also don’t need Nomad then in most cases.

And if you do need nomad on AWS then that’s fine as well, but it’s not comparable to k8s in general.

3 वर्ष पहलेdiscuss

I am a little bit disappointed.

This is just plain old static site generation?

By "docs as code" I expected something like programmatically verifying that the code examples compile, maybe even spinning up VMs and testing that the example commands lead to the expected output.

3 वर्ष पहलेdiscuss

What the hell is an OS without a kernel?

Is this less an OS and more like a toolchain to build container images?

3 वर्ष पहलेdiscuss

Except it isn't, so e.g. running containers still need a VM.

I wish macOS had something like WSL built-in.

3 वर्ष पहलेdiscuss

Great article! I think I knew most of it already but I’ve never seen all of it covered so succinctly and easy to understand!

I think in the case of Nix it is especially important to have a good grasp of the fundamentals so that you can verify your (possibly wrong) assumptions when troubleshooting a build failure, evaluation failure or when using the higher level constructs of nixpkgs.

3 वर्ष पहलेdiscuss

I am using a small German email provider and I can't remember the last time I got spam.

What's even crazier is that they are so confident in their spam filter that they simply reject mails classified as spam. But that hasn't been a problem since the few years I have been using them as well.