ecnahc515

You might like shapez.io

Except Texas has had one of these winter storms roughly every 10 years, so it's not like it's unexpected.

Shell aliases aren't as useful in a CI pipeline, or when trying to provide instructions on how new to Julia installs a new package. Also, with Julia being so different from everything else does mean everyone has to learn a new way of doing things. This isn't a bad thing, I like that Julia has a programmatic API for most of these things, but the UX is definitely not amazing.

I don't use Julia regularly, it's just an example of making it clear how the REPL is core to using Julia.

I'm assuming you may not be familiar with Julia, but basically every "tool" you use in Julia is a library.

It requires importing it in the Julia REPL or activating a new contextual REPL within the Julia REPL. You can then start calling the functions from the imported module. You don't really get standalone Julia tools, it's all libraries and you're always starting the REPL, importing something, then doing stuff from inside the REPL.

For example, installing a package in Julia is the following steps:

    julia
    ] # keybinding which activates pkg mode
    add StaticArrays

You could do it also like this:

    julia -e 'use Pkg; Pkg.add("StaticArrays")'

There is no `julia-pkg add StaticArrays`, unfortunately.

This is awesome. Can you think of any major downsides to an approach like the German system takes?

How did I not know that? How "prod" ready is Dokku if we just ran it on top of k8s?

In case you weren't aware, Glue's metastore is an implementation of Apache Hive, so not too different from the person you're replying to.

As someone else said, what constitutes "Kubernetes" isn't well defined, and so the CNCF put limits on using the terminology in product names.

Ive been interested in the licenses that are restrictive with a time period (eg: 6 months-1 year) after which they become FOSS (Apache2/MIT), eg BSL. I think it's a reasonable approach, but I think the restrictive license still needs to be quite permissive for it to make me happy. I haven't quite found one yet that sat well with me.

I believe they have an option so you can peer your VPC to their hosted offering's VPC, so logs from within your VPC don't have the typical expensive AWS internet egress/ingress costs.

If you have an AWS env, and they have no comparable alternative, you may be forced to look outside AWS, eg: to Elatic's SaaS offering. But in many cases, if AWS has a comparable offering, you simply don't bother looking outside.

It's similar to bundling tactic of Microsoft, and other big vendors. By bundling MS Teams with other things, no one has to "buy" Teams, they already get it for "free" (well, it's no extra cost beyond what they would be paying for Office or whatever already), so why "buy" Slack when you have a similar chat tool for "free".

Reminds of the recent greatsuspender issue that's been going on recently (https://github.com/greatsuspender/thegreatsuspender/issues/1...)

What's the performance like? I think this would be really interesting if comparable to something like Go.

But they run ARM docker images, not x86.

This sounds like synology hybrid raid, which uses lvm and mdadm together for something similar if I recall.

If I was making 99% of the profit off of 1% the market, I’d be terrified someone could just undercut me and take either my 1% or a big portion of the remaining market, that I’m trying to also get.

Owning the profit is great, but owning the market means longevity.

Why would they do that when they could just fully control access with their app and not have to worry about ensuring other clients show ads?

That's (AOT transpilation) quite the interesting approach to the problem. No wonder it's so fast.

The unsafeness here was GDM, not accountservice.

For what it's worth, Jaeger, one of the most popular FOSS tracing servers uses ES/Cassandra for storing it's traces.

They can do both. Someone lying or their inference being wrong about their gender is yet another new data point.

There's way more to this than just the containers (the apps) themselves though. Orchestration is a very big piece of the puzzle, integrating into that layer is traditionally very cloud specific. Without a common orchestration layer you end up re-inventing the wheel a lot. Containers being a common interface is good, but having the orchestration have a common interface (k8s) is also important.

I generally agree. I'm using kustomize right now, but I'm also using helm charts via a kustomize plugin called chartInflator. It allows us to re-use existing upstream boilerplate while still using kustomize. Though I've not been entirely happy with kustomize either, and I'm thinking I might begin to investigate jsonnet for some things.

In addition to what others mentioned, even if Cockroach is written in Go, they could have used Rust, but the trade-off is that they would need to use cgo which introduces extra complexity for building, debugging, and has performance trade-offs that a pure-Go based solution doesn't necessarily have.

A similar story I saw a few months back on reddit is of Jacob Hendel, who also suffered from locked-in syndrome due to Acute Toxic Progressive Stage 4 Leukoencephalopathy.

He's got a website www.jhaendelrecovery.com and youtube https://www.youtube.com/c/JacobHaendelRecoveryChannel/.

It's super inspiring and he regularly provides updates on youtube on his recovery progress.

Not op, but I’d call what they’re referring to as a team lead. Usually a team lead manages 3-6 people, isn’t a manager, but is a senior engineer and has technical leadership abilities.

I refer to it as fargate compute or ec2 compute. It’s not a cluster level thing, you can have clusters with both fargate and ec2 for your compute.

Not really. They require a basic understanding of higher order functions and often heavily use closures. Those moderately advanced concepts. It’s also sometimes harder to write efficiently to avoid multiple iterations over the same collection. I think many many people are way more comfortable with loops than people are with map/filter.

It's subscription/billing management, and it doesn't really do payment processing itself, but rather you might configure Zuora with something like Stripe/PayPal/etc.

Gitlab had an outage today related to Zuora going down. My guess is the backends directly call to these APIs and they don't have any form of caching or storing the info from these APIs elsewhere.