Seeker, you learned your people’s language and then learned the way of the world.

I set this up for seamless commits:

function gao() {
     git add .
     git commit -a -m "$*"
     git push origin `git rev-parse --abbrev-ref HEAD`
 }

Usage: gao fixing a typo

You are stuck on 100% accuracy and trying to actually stuff to death. The user asked if it’s possible to write an application in bash and the answer is an overwhelming duh. Most assembly languages are emulators and they all predate C. You are confidant, wrong and loud. Guess I struck a nerve when I called you out for needing a specific language.

2 parts:

• All languages are middleware. Unless you write in assembly, whatever you write isn’t directly being executed, they are being run through a compiler and being translated from your “middle language” or into 0s and 1s the computer can understand. Middleware is code used in between libraries to duplicate their functionality.
  https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-middleware/
• Most original code was written in shell. Most scripting is done in the cli or shell language and stored as a script.shfile, containing instructions to execute tasks. Before python was invented you used the basic shell because nothing else existed yet

Pretty much all languages are middleware, and most of the original code was shell/bash. All new employees in platform/devops want to immediately push their preferred language, they want java and rust environments. It’s a pretty safe bet if they insist on using a specific language; then they don’t know how awk or sed. Bash has all the tools you need, but good developers understand you write libraries for functionality that’s missing. Modern languages like Python have been widely adopted and has a friendlier onboarding and will save you time though.

Saw this guy’s post in another thread, he’s strawmanning because of lack of knowledge.

Or available via docker for anyone claiming to be an os elitest. Looks great, not meta data that I’m interested in, but thanks for sharing/cataloguing your passion

4 bay nas 22tb drives = 88tb as a single volume. Backed up to offline single storage drives that are timestamped. Anything newer than that timestamp gets rsynced/robocopied to a new drive until it’s full., update timestamp, swap drive and rinse repeat. If a drive fails, just replace it and copy the contents of the backup drives to master and restored. Alternatively you can set a single disk tolerance raid.

I debated signing in multiple times myself, finally got it validated for a feature that was never enabled. Fuck off Google

This thread is a dumpster fire, routing infrastructure, solar panel addresses, we are adding this to EVERYTHING WE ALREADY HAVE that is growing exponentially. I work on an L7 support team, regular users are clueless on how this stuff is setup and apparently have strong stupid opinions. Anyone still reading disable ipv4 in your home network and try to roll forward. You will fail, and finite numbers are finite.

So, yes a few pieces of land mass tech such as smart road or solar paneling and we hit the theoretical limit of IPv6. And we currently dont need the addresses. So glad that you agree

I’m sorry but how? We have appliances with dockerfiles, micro containers for remote controls, extensive botnets of virtual machines, centuries in the future when we have expanded into the solar system and trillions of humans all having millions of unique applications with addresses, it’s inevitable to hit a finite number. When every square meter of smart road has an routable address; we will likely be rewriting networking anyways. The only players pushing IPv6 transition are networking companies because a new standard requires new hardware.

Cisco as a client tried to force ipv6 for their managed service and after an entire quarter of attempting to resolve it, we actually disabled it for their virtual address per their request. IPv4 has issues and IPv6 promises solutions, but it’s not a stable platform yet. This appears ignorant but is based on truth. IPv6 is also eventually going to hit exhaustion with the frequency we spin up virtual machines, it’s okay to skip a bad generation.

It’s released but it’s insane feature light, has massive injestion problems, requires massive collection overhead and doesn’t have a fraction of splunks indexing. And it’s using the standard dd UI and I personally dont like. Logs aren’t metrics, they need a different interface.

Datadog logs are basically in beta. You can send them synthetics apm and rum but I would be interested in spinning up my own private greylog instance to get away from DD logs

#4 #3 pollutants list every year (p6) separate because the materials have different density and when damaged separate (p10). Feel free to do your own research Lemmy downvotes effort that they disagree with. https://www.bottlebill.org/images/PDF/Dutch study on caps_Doppenrapport_EN_2017_DEF_small.pdf

The advertised benefit is that if you throw away the cap and bottle separately, you have 2 pieces of trash to clean up instead of 1. The actual benefit is that bottling companies can charge more for a more complex mold, but the same amount of materials. Lobbyiest lobbied and tada! In reality both pieces end up in the same landfill or in the same water current to garbage island. Now we have an antiquated law and an annoying policy to follow.

Network engineering is kind of in the middle where you take the skill set of help desk and office management. This often leads to help desk and software development both falling under the organization in information technology. Application support also often falls under this category.

I use this in my bash profile in case anyone else finds it helpful. Usage is:

gao fixing a typo

function gao() {
    git add .
    git commit -a -m "$*"
    git push origin `git rev-parse --abbrev-ref HEAD`
}

I’m going to be late to the next meeting, I can’t quit vim ☺️