Firmware.

There’s a surprisingly more expansive demographic that pro tip applies to.

I feel like you should really have seen that one coming.

Whiskey-ware

Half-chubware

I had a physics teacher who measured something against his hand in front of class and started to say, "You should try to..." then stopped before telling us he almost said "you should try to use your body to measure whenever possible" but stopped because he remembered he was talking to a room full of high schoolers.

Well, it's usually closer to the hardware though. Your average x86/64 software dev doesn't have to struggle with pins, addresses, buses and timings that much, if at all.

I''d like to know that where spyware is located?

Firmware is just software that runs in a different place.

Like in the kitchen?

Jk

Pants? Shat.

Hotel? Trivago

This was my assumption too, but I like this description better.

Okay, but now explain Hard and Soft

But third party firmware isn't official

I thought exactly the same thing...

What was more acceptable? "Control stick"?

what ? why ?

I actually never tried to find any meaning to it. I thought it was just software for the BIOS (which it is), and that's it.

But this half wat between soft and hard? Whoa.

Same

200+ Shareware games on a CD, played the shit outta those. And they came in magazines or were given out completely free.

I believe demos for games should still be the norm.

I sharewared my firmware and got malware.

Oh man, Doom. Getting 1/3 of the whole game was incredible. Also Deus Ex years later. Some people hated the Ellis Island level, but I spent so much time exploring everywhere.

The kinkiest of the wares

Of course there's people, the ID-10-T module needs to be installed somewhere!

With the advent of lab grown animal neurons interfacing with parts, we need to expand the definition of "wetware".

It's meat. Doesn't even need to be people meat. Just meat that can be trained to react to stimuli, which opens up some options depending on complexity.

My favorite is smoked firmware.

Super firm trust on first use.

Is this just fantasy?

Hardware is the physical part of computer.

Software is the code that runs on the computer to do the thing you want to do.

Firmware is the code that is installed on the hardware itself, usually in some sort of permanent or semi-permanent memory to make the hardware work.

It's software that lives in the hardware. It provides low-level control and functionality specific to that device. It runs on the hardware itself, not the CPU of the computer.

For example, a hard drive. We don't want the OS to have to know how to interact with every type of hard drive. Seagate does things differently than Western Digital, an SSD works very different than a hard drive, etc.. The OS sends the same commands to all types of hard drives, but each hard drive needs to know how to actually comply with the commands. If the OS is asking for a dozen different files all over the drive, it would be dumb to try and read them all at the same time. The OS doesn't really know where they are on the spinning disk, but the drive does. Firmware written specifically for the device can do a much better job planing how to fetch the data so the read head doesn't need to go back and forth a bunch of times, but instead make one good pass fetching all the data as it comes to it.

Hope that helps.

FIRMware is SOFTware (code) that contains the instructions to run HARDware. In most cases you would experience it, hardware is running an OS (Operating System) which manages all of the firmware ‘packages’. Many electronics, particularly more sophisticated, have firmware that is directly loaded onto the device which has a proprietary OS with limited to no graphical interface.

I am a layperson so if an expert can weigh in on my take I’d appreciate it!

Nibbles are still a thing in embedded programming and in ultra low bandwidth comms like LoRa. For example you can pack 2 BCD digits into a byte, one for the high nibble and one for the low nibble. This results in the hex representation of the byte actually being directly readable as the two digits, which is convenient.

Datasheet for sensors will sometimes reference nibbles as well, often for status bits on protocols like Onewire where every bit counts. i.e low nibble contains a state value 0-15 and high nibble contains individual alarm flags.

I always think of it as software that's saved on the hardware. But I guess technically all software is saved on hardware, but firmware is saved on hardware that's different from the hardware you normally save it on.

But maybe your definition is better.

So in the 90s I had different computer based classes in high school.

There was a "computers" class, which is probably the closest to what you're talking about, in which we mostly learned how to use Microsoft Works.

I also was fortunate enough to have some programming classes. We started out with QBasic and then the more advanced level was visual basic.

None of these discussed firmware. If it came up at all it was probably a casual side conversation because someone bricked something trying to update it.

Care to elaborate?

I've always thought of it more as the software of hardware.

When we getting quickware

Firmsand.

possibly because a "firm" is also a word for a business / company, so "firmware" as the chipset software coming from the firm that manufactures said chipset makes perfect sense. at least that's why I never sought an alternate explanation - and I am not fully convinced OP is right, actually.

I disagree. Firmware originally referred to things in ROM or EEPROM. Basically software that is firmly in place and doesn't change, providing an abstraction layer between the hardware and software.

It's closer to the hardware. Generally harder to update. It's less frequently updated. And it's less fault tolerant.

Idk, sure, it's technically software. But it's pretty clearly at least a distinct subsection that deserves it's own moniker.

The only common thing between software and firmware is the coding part. Everything else is different. Fault tolerance, memory management, MCU optimization, etc.

Half-chub-ware.

This is also true.

38 and I thought firm meant company. Like the firm that created the software for the hardware.

You can know the name of a thing without realizing where the name comes from.

I think he does know what a firmware. Just didnt't realize the origin of the term.

A firmware is neither soft nor hard... it's firm.

(Or maybe I completely misunderstood the tweet 🙄