mootzville

This shit is amazing! Thanks.

True, thought I didn't include the lookup first, it is how it happens in practice. Also, we use the mysql client, so semicolon is a must, and I would avoid anything that let you submit the statement without it...that's your safety net.

I was taught to:

1. Write your WHERE clause first 2. Return to the beginning of the line to finish writing the statement 3. Check your statement 4. If it looks good, then -- and only then -- add your closing semicolon

Having said that, once during my second week at a new company, I plugged in an ethernet cable to an APC UPS, so I could set up networking on it. It shut down production. Why? APC makes (for that model at least) proprietary ethernet cables for networking, and if you plug in a regular cable it does an autoshutdown...an engineers attempt at marketing perhaps!? I did RTFM before, and after out of confusion, and there was no mention of this.

Oh, if anyone does care about this, the browser console is throwing this out now: The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.

But...I'm not sure if it was throwing that before as well. But it would seem that it gets triggered at the moment when you'd normally see the conversation get thrown into your conversations list...instead, get that in the console, and no conversations ever make it to the converation list.

Also, as a side note, another interesting find is the idea of recursive prompting. I had it spitting out some interesting code in Javascript based on dental x-ray analysis, and once it did something I really liked I just kept sending, "Awesome! Continue." and it did really interesting things.

Having said that, I write a lot of JS / Node. When you npm (a package manager for NodeJS) install something there could very well be some curl commands piping to bash or sh.

Makes me think of an idea -- and maybe it exists -- create a npm package whose only purpose is to run checks on the code of the other packages being installed to ensure they are "safe".

Seems like the best solution is to not use this technique. Been touching linux servers for 10+ years, and have never had to use it. I definitely used it when learning linux though.

I curl to files for review when I need / want to run a remote script. A bonus is you still have to `chmod u+x some_remote.sh` before it can be run, so it would be extremely difficult to accidentally run.

Look up the actual definition of "proprietary". If a company owns it, it's proprietary...even open source software.

Open source software can cost money, and still be open source...it currently exists.

CentOS still exists, and is now owned by Red Hat. Originally, CentOS was meant to be the community ("free") version of RHEL, yet after Red Hat took it over it has since become a mid-point in the stream.

Before it was Fedora -> Red Hat

Now it is Fedora -> CentOS Stream -> Red Hat

RHEL is not free, but the word "free" is loosely defined in open source world. RHEL is open source, yet it is also proprietary. Yes, if you wanted to build from source you can, for free, but you get no access to the repos or service and you have to strip out all references to Red Hat (trademark / copyright infringement) if you want to use it commercially. So, ya if you want to use it at home or to learn, it's free.

If it ain't broke, don't fix it.

You are kind of combining two things though: legacy systems, and proprietary systems.

There are modern proprietary systems as well. RHEL is a good example.

I'd argue it's not a "small number of entities" though. You'd be shocked by what legacy systems are running in the most important places on the planet...maybe scared. Unfortunately/Fortunately, nuclear facilities aren't running Linux Kernel 6.X

The fact is, a lot (probably most) problems solved with a computer don't need further updates. As long as the hardware continues to function, all is well.

Something you may have not considered is that when the time does come, and the hardware does fail, I'd guess most organizations will opt -- and even go out of their way -- to source those same legacy components they had before to keep things running exactly the same instead of upgrading to a more modern solution.

I've had to do this a number of times for clients. Not long ago, I had to source an old mainboard for a system that was 20+ years old...in doing so I did realize there is some good money to be made if you can source parts for systems about 20 years in the past because the board was like $300 (this was 2017, and the board had a 33mhz processor and like 8MB RAM)

If you don't have to touch these systems, count yourself lucky.

If you do touch these systems, thank you for your service.\

In regards to the modern proprietary systems, there are many, but if you consider RHEL for instance, there is a lot of value for large organizations. They can reduce the number on on-hand personnel whom probably would be less efficient at solving an OS issue than a RHEL engineer. As an example, the Federal Reserve runs modern RHEL...but I'd guess if you dig deep, they have some really old stuff too...

I'd argue this is one of the last things people will be thinking about in this election. No one is changing their vote over this...the economy and abortion will drive this cycle.

You're probably thinking: If they can't transfer them, why did they show up the first time? That's a good question...