ossm1db

Kubernetes official documentation states, "A Pod is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers."

Running more than one container in a pod is a fundamental concept of Kubernetes. Init containers and sidecars allow for a separation of concerns, which is essential for non-cloud-native workloads. Logging and telemetry are just a couple of features which may be designed and built into cloud-native applications, but legacy applications need this flexibility without modifying the application itself.

The fact you ran K8S for four years without it demonstrates only that it is not required by your workload -- not that it is "unnecessary complexity" or an "anti-pattern."

int relationship(double effort) { return -1; }

Lies, damn lies, and statistics.

The Blue-Ridge Mountains vs a concrete jungle? That's a no-brainer.

Thank you. As an ACM member myself, this is indeed welcome news.

I used a free redis instance. There are all sorts of free database and storage services out there. Cloudflare has some really cool free stuff.

I like the idea. It has promise but needs some work: no explanation of what reputation does; dice always reduce reputation, not sure why that is desirable; buying first campus sets money to negative cost of campus (-$10000 for first one); state not saved; images spin instead of a more meaningful animation. I think clickers like this are great projects for someone wanting to learn javascript frameworks.

If you aren't familiar with the Actor Model, it's worth investigating. It avoids a lot of problems you will experience with other paradigms. https://www.brianstorti.com/the-actor-model/

In my opinion, TF is for cloud infrastructure up to and including the creation of the kubernetes cluster. Use the Kubernetes API with kubectl, kustomize, helm, skaffold, k14s, etc. to deploy applications and resources on the kubernetes cluster. It is my experience that using TF to deploy k8s applications and resources is putting a square peg in a round hole. It works with toy examples and simple applications, but fails in more complicated scenarios (like dev/test/prod templates and overlays) where existing k8s tools are more appropriate.

once AMD releases their 'c' cores, one might argue that SMT is no longer worth the additional complexity.

The movie "Phase IV" is the perfect movie to accompany this research.

I developed a rule of thumb for my kids (boy/girl): one individual sport/activity, one team sport, and (boy/girl) scouting. Some parents do even more, but we feared either they or we would get overwhelmed. The individual activity included ballet, bowling, gymnastics, swimming, or whatever they wanted to try out.

Even no-code requires that you be able to break a problem down to solve it, and that involves knowledge, skills and experience. Programmers will adapt, not disappear.

"Never gonna give, never gonna give (Give you up)"

I'm not just buying a six-piece, I'm getting six lottery tickets.

It's on the journal's web site: https://www.nature.com/articles/s41467-021-22592-4

How did they deal with all of those typewriters in the 50s with an open floor plan? They didn't.

Or blocking a turn lane. My thoughts exactly.

and every time it is posted, the "TCP over TCP is a bad idea" link is brought up (once by myself). Each time, the poster/supporters downplay TCP Meltdown. Solutions for VPN over TCP 80/443 already exist. It makes a great pet project, don't get me wrong, but it's not going to get any interest from industry professionals.

I understand, but you are still susceptible to TCP meltdown. You need to alert users to the risks.

Why TCP Over TCP Is A Bad Idea http://sites.inka.de/bigred/devel/tcp-tcp.html

What about the other 11 months?

This looks like a wheel sieve: https://programmingpraxis.com/2012/01/06/pritchards-wheel-si...

Run the websocket proxy yourself and get much better performance: https://github.com/benjamincburns/websockproxy

From the FAQ: "net_url sets the URL of the websocket VPN." I did this and it works great.

I guess I should consider myself very fortunate. It works out very well for me. I've worked under an unlimited PTO policy for several years now (at two different companies).

It does not "depend on management approval." Approval for time off is automatic; it is only necessary to coordinate with your supervisor and/or team to make sure tasks can be handled by coworkers in your absence. Vacations were typically one to three weeks, sometimes longer for international travel or special situations.

There is no "pressure to keep the PTO profile low" or limit the amount of time. It isn't even tracked.

It's not a "loss of a benefit." I've been able to use more time off than before, even with the most generous PTO benefits at prior organizations.

SOA is _not_ ESB

If Gitlab could deploy to a play-with-k8s temporary cluster with four hours to test and evaluate, that would be pretty cool.

I learned first-hand that migrations are difficult. Do not go to production with Swarm if you are thinking of migrating to k8s. Use it for experimentation and learning.

I also recommend starting with Swarm (not necessarily going to production) and then learning k8s next. This is the path I am taking. Kubernetes is different in surprising ways, but it helps to already have the basic concepts down by learning Swarm.