bloat

(redirected from bloat line)
Also found in: Dictionary, Thesaurus, Medical.
Related to bloat line: frothy bloat

bloat,

excessive accumulation of gases in the rumen, the first stomach of a cud-chewing animal. Bloat is probably formed to a large extent by bacterial action. It occurs in all ruminants, but is most common in cattle; it appears typically in animals that graze on newly developed, highly productive, lush green pastures, especially during a wet summer on clover-dominant pastures. Bloat can result from excess frothiness of the ruminal ingesta or loss of tone and motility of the rumen. Both of these conditions will prevent the normal eructation process. Treatment consists of passing a tube to the stomach or of reducing the foam formation by oral administration of mineral or vegetable oils. Prevention is attempted by carefully controlled management practices, administration of antibiotics, and the use of nontoxic oils.

bloat

[blōt]
(veterinary medicine)
Distension of the rumen in cattle and other ruminants due to excessive gas formation following heavy fermentation of legumes eaten wet.

bloat

Vet science an abnormal distention of the abdomen in cattle, sheep, etc., caused by accumulation of gas in the stomach

bloat

bloatware

(1) Applications that are overloaded with features. See software bloat and wares.

(2) Extra applications pre-installed on a Windows computer. Quite often in the past, PC manufacturers have been paid by software vendors to pre-install lite versions of their products on the machines they sell. In addition, some of these applications load at startup, wasting RAM and providing a potential for conflict with other programs. For a fee, some retailers have offered to rid the new PC of bloatware for customers.

Android Mobiles Too
Like Windows, Android devices also suffer from bloatware, especially from the carriers. In some cases, as many as four different music players have been pre-installed on a device. See wares.


MAINGEAR PCs are "Clean"
Prominently displayed on MAINGEAR's website, this high-performance PC vendor builds PCs with only the software the user asked for. For more information, visit www.maingear.com.

software bloat

(1) See bloatware.

(2) The ever-increasing complexity of software. Modern operating systems and applications are huge in size compared to software in personal computers in the late 1970s and early 1980s. They are gigantic next to software of the 1950s and 1960s.

There Are Several Reasons
Today's object-oriented programming languages generate much more machine language than earlier non-object languages. See object-oriented programming.

The increasing capacities of the computer's RAM and storage allow programmers to be much less concerned with conservation.

The marketing department demands more functions in the app to sell another version, even if 98% of people never need them.

In order to make it easier to write a program, software is often written in higher levels of abstraction. This eliminates the coding tedium but increases the number of instructions the computer must execute (see abstraction layer).

There are often too many cooks in the kitchen. The more software code is patched by different people, the more obtuse it can become. See Wirth's law and Freedman's law.

A Note from the Author


From 1963 to 1966, I programmed an IBM 1401 for the Pennsylvania Drivers License Division. The first widely used transistor-based computer, the 1401 processed all six million drivers in the state.

The machine had 12K characters of RAM (equivalent to 12,000 bytes). The driver master file was some 40 reels of magnetic tape.

The point of this story is that we never added the extra 4K memory module, upgrading the machine to its 16K maximum. It would have cost several thousand dollars, and we never found it necessary. Our programs, written in IBM assembly language, first on paper and then transcribed to punch cards, were extremely compact. We condensed program steps wherever we could.

There was no graphical interface, because there was no screen. We debugged our programs with memory dump printouts, and we didn't even have an operating system. What for? We just wrote our own input/output routines.

But, we processed an entire state!

Know anyone processing a state on a desktop computer with easily a million times as much RAM as we had in 1963? Software bloat. Better believe it. See IBM 1401.


Looking Rather Nerdy in 1963
I'm the guy on the left clowning around with our IBM systems engineer. Love that tie!







In a Span of Twenty Five Years
The processing power in the 2016 MacBook (right) is nearly seven million times greater than Apple's PowerBook in 1991. Needless to say, we are not producing seven million times as much work on our personal computers today as we did 25 years ago. (Image courtesy of Apple Inc.)