thinkmassive

https://en.wikipedia.org/wiki/Layoff

I think the meaning has fully shifted to imply permanence, for at least a couple decades now. The word that comes to mind for a temporary situation is furlough, although I’ve mainly heard that used in a government context.

Maybe the difference is that most people now change jobs often enough, that the government is the only entity that would promise to re-employ those they temporarily couldn’t pay.

Service discovery adds some complexity, but if you’re operating with any amount of scale that involves dynamically scaling machines then it’s also the simplest model available so far.

What about it doesn’t work for you?

Edit: I didn’t touch on logging because the post is about metrics. Personally I’ve enjoyed using Loki better than ELK/EFK, but it does have tradeoffs. I’d still be interested to hear why it doesn’t work, so I can keep that in mind when recommending solutions in the future.

I discovered it from Google’s Kubernetes podcast, so that might be worth a listen (although there’s more tangible information in the executive summary and key findings, 3 easy pages):

https://kubernetespodcast.com/episode/205-state-of-cost-opti...

If you don’t want to submit the form, a quick search should provide a direct link to the PDF.

You might find their forum (intended for end users, not much about development) or some of their repos useful:

https://github.com/endlessm

https://community.endlessos.com/

Silverblue/Sircea gets all the attention these days, but Endless is the oldest OSTree-based user distro by a long shot, and it’s still actively developed by the Endless Foundation.

It’s also the one most suitable for non-technical users. Definitely worth considering for that use case, particularly for very young users since it now includes plenty of tutorial content intended for that audience.

I know multiple people still using an iPhone X (2018), for whom cost is not an issue.

The main reason for the majority of the general population to upgrade is because the phone literally breaks (screen, stops charging, radio malfunctions, etc)

nit: Every competent developer I know uses PGP on a daily basis, for signing and validating commits. The responsible ones also use it to validate security-critical software is coming from the expected source. I do agree though, that the original use case of encrypted email is largely dead.

Many places that accrue PTO will pay out for unused days at your departure.

How often would you estimate that security concerns are a valid reason to isolate functionality into a microservice? Separation of concerns, reduced attack surface and blast radius, etc

Obviously the performance of tor is reduced when traffic increases, but performance isn’t the goal, privacy is. Increasing the traffic of "normal" use cases (as opposed to those targeted by state-level opposition) improves privacy for the entire network.

I agree that using tor for all your video conferencing and streaming needs is probably irresponsible, possibly unethical, but the performance is likely to be so poor that it’s not a good use case anyway.

Using tor for everyday text chat (by real humans) is unlikely to have a negative performance impact, and it does provide more noise for attackers to sift through, so it could arguably improve privacy for those who need it most.

I wish there were better options for listening 20-25 hours/mo. Like Amazon in general, the selection + convenience is tough to beat.

Audible Premium Plus - 1 Credit Every Other Month for $17 ($8.50/mo)

You can buy 3 more credits for $37.99 (12.66/ea). It’s also worth checking individual titles because quite a few cost less than the credits.

Correction: I guess I actually buy slightly fewer than 2/mo because there’s a plan for that ($22.95/mo) that’s cheaper than the 27.50/mo from my numbers above. I had that one for a while but ended up feeling pressured to use them before they expire.

    A catalogue of DeFi platforms that facilitate permissionless trading

Permissionless: https://coinmarketcap.com/alexandria/glossary/permissionless

Your question is broad, so you may get a more helpful answer if you ask something more specific.

Of course you can have all that without k8s. I’ve been operating cloud infra for over a decade, and I used to roll my own solutions to implement that functionality, so I’m quite familiar with that approach. Embracing kubernetes has made life much easier. I do read a lot, but my opinion is based on operating production systems. Whether you like it or not, k8s has become the defacto standard interface for distributed systems.

High level programming languages and libraries provide useful layers of abstraction in their own domains. Do you also reject those, and use assembly language for everything?

The recent post “Finding an Edge” inspired me to share here. It’s probably no surprise that making a basic knife is relatively easy, considering it’s one of the first tools created by man. What did surprise me is how fun it can be, and with such low overhead to get started.

The author also has an entertaining YouTube channel called Knife Steel Nerds, which may be more interesting for anyone not yet into the hobby.

Some drawbacks of plain YAML, and of tools that use string templating to render YAML:

    - difficult to extend features not exposed by upstream
    - composition is often messy, resulting in duplication
    - validation is often impractical (at least identifying the exact source of the error… I’m looking at you Helm!)

https://tanka.dev/

https://cuelang.org/

Persistent storage has been a solved problem, especially when using a managed Kubernetes service. What's the problem with running stateful workloads on a cluster?

Pods are not intended to bundle those 3 services. Typically one would use higher level abstractions (Deployment for the API, StatefulSet for the database), each composed of multiple Pods that should be scheduled on different physical machines.

It’s no wonder you’ve had a bad experience trying to use it the way you describe. Following the intended patterns provides a standard way to achieve rolling updates, horizontal autoscaling, and a ton of other functionality that used to be bespoke code at each organization. The old way was often buggy, and onboarding new engineers took much longer.

It’s possible to deploy a smart contract with no way to modify it, meaning it’s literally impossible to shutdown (without shutting down the entire network). This is rare, most dev teams retain admin keys and compose the smart contact components from additional layers of abstraction to allow for updates. But those admin keys typically also allow the possessor to abscond with all funds locked in the contracts (a rugpull).

My understanding is Tornado Cash eventually added a limited form of KYC to the frontend web UI. That’s simply a convenient interface to use the smart contract though, and it’s possible to interact with the smart contact directly (where there’s no KYC).

https://opentf.org/#output

The post was written by the CTO (former founder and CTO of Chef). It mentions at the highest level how DevOps has succeeded since 2009, then it complains about how our tooling is practically unchanged since then. This results in “death by a thousand papercuts,” which System Initiative aims to solve!

Visiting the website[1] provides a better overview of the purpose/goal. It seems like an opinionated configuration of a stack of existing tooling that can be extended in typescript.

Edit: seems like there’s something novel going on with building a graph of the infra, and having a GUI to collaboratively manipulate the infra through.

[1] https://www.systeminit.com/

That’s pure Free Software, and it would require Amazon to publish their changes or not offer the service. In reality they would probably choose the latter.

You can run each of those roles on the same machine, achieving high availability from 3 total. For learning purposes you can run this all in VMs on a single machine.

There are plenty of good reasons not to try kubernetes when it doesn’t fit your use case, but the overhead it imposes is mostly in time and expertise. Claiming it’s more costly in compute resources, and especially contributing climate crisis, is reaching.

    Change Date:2023-06-29          2027-01-01
    
    Change License:       Apache License, Version 2.0


    Effective on the Change Date, or the fourth anniversary of the first publicly available distribution of a specific version of the Licensed Work under this License, whichever comes first, the Licensor hereby grants you rights under the terms of the Change License, and the rights granted in the paragraph above terminate.