chrisv <chrisv@nospam.invalid> wrote:
>Chris Ahlstrom wrote:
>> some dumb fsck wrote:
>>>
>>> I used to fuck with my hard-of-hearing, grumpy old grandfather by
>>> looking at him and mouthing words. Later on I did it to my Dad, too. heh!
>>> RIP to grandpa HTS and father JFS.
>
>Once an asshole, always an asshole, eh?

It's a little concerning, yeah, behaviorally.

>> Too bad they didn't take a switch to yo ass.
>
>Too bad he wasn't aborted.

Oh, I like DFS, for all his faults. He's not a Trump fan. That
weighs heavily with me. His software ignorance facade just seems like
a troll tactic, he can't really claim that Winblows is so amazing.
He's run our shit, too, he knows the "crapps" aren't so crappy, but
are great alternatives.

--
Joel W. Crump

Amendment XIV
Section 1.

[...] No state shall make or enforce any law which shall
abridge the privileges or immunities of citizens of the
United States; nor shall any state deprive any person of
life, liberty, or property, without due process of law;
nor deny to any person within its jurisdiction the equal
protection of the laws.

Dobbs rewrites this, it is invalid precedent. States are
liable for denying needed abortions, e.g. TX.

On 4/11/2024 5:13 PM, shitv wrote:
> Chris Ahlstrom wrote:
>
>> some dumb fsck wrote:
>>>
>>> I used to fuck with my hard-of-hearing, grumpy old grandfather by
>>> looking at him and mouthing words. Later on I did it to my Dad, too. heh!
>>> RIP to grandpa HTS and father JFS.
>
> Once an asshole, always an asshole, eh?

Hypocritesayswhat?

>> Too bad they didn't take a switch to yo ass.
>
> Too bad he wasn't aborted.

Things My Parents Said About Me
©2024 shitv

On Thu, 11 Apr 2024 11:54:35 -0400, DFS wrote:

> "By obtaining and reproducing these signals in a controlled way over
> headphones, you can reproduce an auditory event in space and experience
> it in an extremely lifelike way."

Maybe you could find some of those original stereo records from the '50s
where a train drove though your living room. Don't forget the matching
panther TV light.

On Thu, 11 Apr 2024 12:12:25 -0400, DFS wrote:

> Yep. I went to a pro car race once at the Atlanta Motor Speedway (in
> the 70s). I was shocked how loud the cars were when they passed in
> front of you.

This was a half mile oval so the sound level was fairly constant. I've
only been to one Grand Prix at Watkins Glen. It was underwhelming. The
SCCA races at Limerock were better except for the Mazdas.

There aren't many tracks around here but the one I go to sometimes is a
1/3 mile tri-oval. It's okay but not like the good old days when the
groundhogs ran for their lives when the ground started to shake.

On Thu, 11 Apr 2024 16:06:46 -0400, Chris Ahlstrom wrote:

> I would skip such an event. (And generally loud concerts as well.)

If it's too loud you're too old.

rbowman wrote this copyrighted missive and expects royalties:

> On Thu, 11 Apr 2024 11:54:35 -0400, DFS wrote:
>
>> "By obtaining and reproducing these signals in a controlled way over
>> headphones, you can reproduce an auditory event in space and experience
>> it in an extremely lifelike way."
>
> Maybe you could find some of those original stereo records from the '50s
> where a train drove though your living room. Don't forget the matching
> panther TV light.

My uncle was big into Quadrophonic for awhile.

--
You will feel hungry again in another hour.

chrisv wrote:

> -hh wrote:
>>
>>Where it gets tricky is that the dB loss curve is stronger at higher
>>frequencies, plus as one ages it gets steeper.
>>
>>For example, at 2kHz, going from age 20 to 40 has roughly a -10dB loss,
>>but at 8kHz for the same age increase, its a -20dB loss. Call this the
>>"stronger" element part.
>>
>>When going onto the next 20 year increment (from age 40 to 60), 2kHz now
>>has an additional -10dB loss (same "strength" as before), but 8kHz jumps
>>to -40dB (thus, much "steeper").
>>
>>Similarly, for 4kHz, the total loss at age 20 is -9dB, but by age 40 its
>>-22dB (notionally, if it was a linear loss it should have been -18dB),
>>and age 60 is -55dB ('linear' would have been -27dB)
>
>Those numbers are absolute nonsense.

I'd like to withdraw the above, and say that I'm extremely skeptical
that the losses in the 1 - 10 kHz range are that bad, that soon. No,
I still haven't Google researched, but I will if no evidence is
forthcoming.

--
"Google has one single cash-cow... and that's search. Everything else
is a snoozer. Android phones... they can give away the Android OS to
all the OEMs in the world... a billion times $0.00 is still zero." -
trolling fsckwit "Ezekiel", putting his ignorance on display.

chrisv wrote this copyrighted missive and expects royalties:

> Chris Ahlstrom wrote:
>
>> some dumb fsck wrote:
>>>
>>> I used to fuck with my hard-of-hearing, grumpy old grandfather by
>>> looking at him and mouthing words. Later on I did it to my Dad, too. heh!
>>> RIP to grandpa HTS and father JFS.
>
> Once an asshole, always an asshole, eh?
>
>> Too bad they didn't take a switch to yo ass.
>
> Too bad he wasn't aborted.

And when I implied he should have been beaten with a switch,
I meant a Cisco switch :-D

--
You may worry about your hair-do today, but tomorrow much peanut butter will
be sold.

rbowman wrote this copyrighted missive and expects royalties:

> On Thu, 11 Apr 2024 16:06:46 -0400, Chris Ahlstrom wrote:
>
>> I would skip such an event. (And generally loud concerts as well.)
>
> If it's too loud you're too old.

I studied hearing science (got a Ph.D in it).

--
Q: How many surrealists does it take to change a light bulb?
A: Two, one to hold the giraffe, and the other to fill the bathtub
with brightly colored machine tools.
[Surrealist jokes just aren't my cup of fur. Ed.]

On Fri, 12 Apr 2024 08:00:23 -0400, Chris Ahlstrom <OFeem1987@teleworm.us>
wrote in <uvb7on$2bjoi$2@dont-email.me>:

> chrisv wrote this copyrighted missive and expects royalties:
>
>> Chris Ahlstrom wrote:
>>
>>> some dumb fsck wrote:
>>>>
>>>> I used to fuck with my hard-of-hearing, grumpy old grandfather by
>>>> looking at him and mouthing words. Later on I did it to my Dad, too.
>>>> heh!
>>>> RIP to grandpa HTS and father JFS.
>>
>> Once an asshole, always an asshole, eh?
>>
>>> Too bad they didn't take a switch to yo ass.
>>
>> Too bad he wasn't aborted.
>
> And when I implied he should have been beaten with a switch,
> I meant a Cisco switch :-D

Speaking of technology...

I mentioned two technological advantages of Linux over Windows,
expecting a discussion from the guy: early fork(2) behavior,
and TCP/IP.

Instead of discussing it, he just went on the attack.

I've also seen him ask a question in comp.lang.c that he
could have answered himself by typing on his Linux shell:

$ man size_t

I really, really, wanted to give him sh*t for that, but held
off because he was already receiving his just due of "WTF?".

He may be a competent Excel and Access programmer
-- and maybe even Python -- but given his old-fashioned
ideas, I suspect he may sell buggy whips on the side.

Finally, I once confronted him as being racist. His response?
"Everybody's racist! You're racist too!"

So he's ignorant. Cunning, though -- don't turn your back on him.

--
-v

On 4/12/2024 9:17 AM, vallor wrote:
> On Fri, 12 Apr 2024 08:00:23 -0400, Chris Ahlstrom <OFeem1987@teleworm.us>
> wrote in <uvb7on$2bjoi$2@dont-email.me>:
>
>> chrisv wrote this copyrighted missive and expects royalties:
>>
>>> Chris Ahlstrom wrote:
>>>
>>>> some dumb fsck wrote:
>>>>>
>>>>> I used to fuck with my hard-of-hearing, grumpy old grandfather by
>>>>> looking at him and mouthing words. Later on I did it to my Dad, too.
>>>>> heh!
>>>>> RIP to grandpa HTS and father JFS.
>>>
>>> Once an asshole, always an asshole, eh?
>>>
>>>> Too bad they didn't take a switch to yo ass.
>>>
>>> Too bad he wasn't aborted.
>>
>> And when I implied he should have been beaten with a switch,
>> I meant a Cisco switch :-D
>
> Speaking of technology...
>
> I mentioned two technological advantages of Linux over Windows,
> expecting a discussion from the guy: early fork(2) behavior,
> and TCP/IP.
>
> Instead of discussing it, he just went on the attack.

I didn't know you wanted some repartee over those issues.

1) fork(2) behavior?

https://man7.org/linux/man-pages/man2/fork.2.html

fork you

2) "Where did Windows get TCP/IP from?"

It's common knowledge MS used the BSD FOSS TCP/IP code, but they wrote
their own brand new implementation 16 frickin' years ago. That's sixteen.

I'm sensing an ignorant and stuck-in-the-past mindset on your part.

> I've also seen him ask a question in comp.lang.c that he
> could have answered himself by typing on his Linux shell:
>
> $ man size_t
>
> I really, really, wanted to give him sh*t for that, but held
> off because he was already receiving his just due of "WTF?".

When you don't know if you should bite your tongue or not, don't. You'll
feel better.

I figured I would catch some hell for that question, but I was curious
why memset accepted ints when the function prototype specifies size_t.

For a language as 'strict' as C, it seems to be handled with a little
leeway. gcc warns or errors using printf(%d) with a long int.

> He may be a competent Excel and Access programmer

More than competent (at least in the past).

> -- and maybe even Python -- but given his old-fashioned
> ideas, I suspect he may sell buggy whips on the side.

I sense a mild insult in there.

And I don't understand: which of my ideas is old-fashioned?

> Finally, I once confronted him as being racist. His response?
> "Everybody's racist! You're racist too!"

Sounds like me. But I'll have to look that one up in my all-knowing,
all-seeing database.

In the meantime, tell me about all your non-White friends, accountants,
lawyers, doctors, etc. Don't slink away now.

I found this, from 9 years ago
============================================================================
I've asked you 4 or 5 times why you refuse to run your business on Linux
desktops, and all you do is slink away.

I show how ALL the founders and top managers and executives at Sonic are
White, and you claim you're not a racist organization.

I ask how many black friends you've had over to your house the last 6
months, and you run away.
============================================================================

You NEVER did answer any of those issues.

> So he's ignorant.

Not in the least. Your problem is you didn't grow up in Apelanta.

> Cunning, though -- don't turn your back on him.

A cunning linguist in my day, for sure. They all said so.

On Fri, 12 Apr 2024 12:23:37 -0400, DFS wrote:

> It's common knowledge MS used the BSD FOSS TCP/IP code, but they wrote
> their own brand new implementation 16 frickin' years ago. That's
> sixteen.

And winsock.h still is a little strange.

rbowman wrote this copyrighted missive and expects royalties:

> On Fri, 12 Apr 2024 12:23:37 -0400, DFS wrote:
>
>> It's common knowledge MS used the BSD FOSS TCP/IP code, but they wrote
>> their own brand new implementation 16 frickin' years ago. That's
>> sixteen.
>
> And winsock.h still is a little strange.

All windows headers are bloated monstrosities. Ya better just include the
massive universe of <windows.h> :-D

On the other hand, GNU code is full of IFs ANDs BUTs and MAYBEs.

Jesus the gettext headers and code are ... obtuse.

--
Do something unusual today. Pay a bill.

On Fri, 12 Apr 2024 13:17:36 -0000 (UTC), vallor wrote:

>
> I've also seen him ask a question in comp.lang.c that he
> could have answered himself ...
>

Ha, ha, ha, ha, ha, ha, ha, ha, ha!

His, the DooFuS, postings to comp.lang.c are unimaginably
asinine messages. They reveal his total lack of not only
C programming but of computer science in general.

Only the civilized etiquette of that group prevented him
from being laughed out in complete shame.

The guy is a total digital loser.

>
> He may be a competent Excel and Access programmer
> -- and maybe even Python ...
>

Ha, ha, ha, ha, ha, ha, ha, ha! You must be joking!
His "knowledge" of such programming is purely superficial
but enough to get by his former ignorant corporate
bosses.

Get real.

>
> So he's ignorant. Cunning, though -- don't turn your back on him.
>

Ha, ha, ha, ha, ha, ha, ha, ha, ha!

He, the DooFuS, is a little man with a big mouth.
That is all.

Le 09-04-2024, Joel <joelcrump@gmail.com> a écrit :
> Farley Flud <ff@linux.rocks> wrote:
>
>>I play my FLAC files thusly:
>>
>>flac -d -c file.flac | aplay
>>
>>What could be simpler?
>
> Having an actual GUI, you retard.

Why would it be simpler? His command line is far from complex and if not
the simplest, it could easily been scripted if often launched. It could
be done available within a few keystrokes, which would be as fast as
launching your GUI. And the first thing you would do with your GUI is to
hide it because it becomes useless when the music plays.

--
Si vous avez du temps à perdre :
https://scarpet42.gitlab.io

On Fri, 12 Apr 2024 15:16:26 -0400, Chris Ahlstrom <OFeem1987@teleworm.us>
wrote in <uvc1aa$2h40t$1@dont-email.me>:

> rbowman wrote this copyrighted missive and expects royalties:
>
>> On Fri, 12 Apr 2024 12:23:37 -0400, DFS wrote:
>>
>>> It's common knowledge MS used the BSD FOSS TCP/IP code, but they wrote
>>> their own brand new implementation 16 frickin' years ago. That's
>>> sixteen.
>>
>> And winsock.h still is a little strange.
>
> All windows headers are bloated monstrosities. Ya better just include
> the massive universe of <windows.h> :-D

That doesn't sound very POSIX, but I might be biased (see domain name).

> On the other hand, GNU code is full of IFs ANDs BUTs and MAYBEs.
>
> Jesus the gettext headers and code are ... obtuse.

But how often do you have to go into those? Don't you just enable
a feature macro and Bob's your uncle?

--
-v

vallor wrote this copyrighted missive and expects royalties:

> On Fri, 12 Apr 2024 15:16:26 -0400, Chris Ahlstrom <OFeem1987@teleworm.us>
> wrote in <uvc1aa$2h40t$1@dont-email.me>:
>
>> rbowman wrote this copyrighted missive and expects royalties:
>>
>>> On Fri, 12 Apr 2024 12:23:37 -0400, DFS wrote:
>>>
>>>> It's common knowledge MS used the BSD FOSS TCP/IP code, but they wrote
>>>> their own brand new implementation 16 frickin' years ago. That's
>>>> sixteen.
>>>
>>> And winsock.h still is a little strange.
>>
>> All windows headers are bloated monstrosities. Ya better just include
>> the massive universe of <windows.h> :-D
>
> That doesn't sound very POSIX, but I might be biased (see domain name).
>
>> On the other hand, GNU code is full of IFs ANDs BUTs and MAYBEs.
>>
>> Jesus the gettext headers and code are ... obtuse.
>
> But how often do you have to go into those? Don't you just enable
> a feature macro and Bob's your uncle?

I want to parse .mo files without using the GNU API for that.
First you have to figure out what the code does. There's the rub.

Let's say you want to figure out how a function like ngettext() works.
You find two files: intl/ngettext.c and src/ngettext.c.

In the first one, #ifdef _LIBC then NGETTEXT is defiend as __ngettext,
otherwise it is defined as libintl_ngettext. Then

GETTEXT (const char *msgid1, const char *msgid2, unsigned long int n)
{ return DCNGETTEXT (NULL, msgid1, msgid2, n, LC_MESSAGES);
}

where DCNGETTEXT is defined as __dcngettext or libintl_dcngettext.

Also __ngettext is a "weak_alias" for ngettext, or maybe vice versa.

Now we look in intl/dcngettext.c and find macros similar to the above.
And then

DCNGETTEXT (const char *domainname,
const char *msgid1, const char *msgid2, unsigned long int n,
int category)
{ return DCIGETTEXT (domainname, msgid1, msgid2, 1, n, category);
}

At this point I want to kick Ulrich Drepper's ass!

In dcigettext.c we find more macros and finally the dcigettext() function.
It's chock full of conditional macros, uses some lock/unlock code and
indirection galore. About 460 lines of crappily-indented code. Supported
by a number of other functions loaded with pointer arguments, including another
400+ liner.

You bet your roots toots it's tons of fun!

--
Avoid reality at all costs.

On 4/12/2024 4:24 PM, Cackling Larry Piet wrote:

> On Fri, 12 Apr 2024 13:17:36 -0000 (UTC), vallor wrote:
>
>>
>> I've also seen him ask a question in comp.lang.c that he
>> could have answered himself ...
>>
>
> The guy is a total digital loser.
>
> Ha, ha, ha, ha, ha, ha, ha, ha, ha!
> Ha, ha, ha, ha, ha, ha, ha, ha!
> Ha, ha, ha, ha, ha, ha, ha, ha, ha!

If your programs are the output of a "digital winner" and a "C
Programmer Extraordinaire", I refuse to step on that podium.

--------------------------------------------------------------
Let us shown him the way a REAL MAN and REAL GNU/Linux user
does things.

Here is the wonderfully perfect and highly efficient code:

/* free all strarray elements */
for(i = 0; i < rec_count; i++) {
free(data[i]->field1);
free(data[i]->field2);
free(data[i]->field3);
free(data[i]);
i++;
} --------------------------------------------------------------

Now THAT shit-code is worthy of ha*26.

> He, the DooFuS, is a little man with a big mouth.

The irony meter is WAY off the charts.

A few choice Feeb quotes:

* Intellectully, I am superior to 99.9999999% of the human
population.

* if a number is prime could it be even? The answer is "no"

* I am heavily involved in virtually ALL AREAS of contemporary computing

The sustained self-nuke this delusional braggart delivers is unmatched
in cola's history, even by shitv and John GodHesDumb.

On 4/12/2024 8:02 AM, Chris Ahlstrom wrote:
> rbowman wrote this copyrighted missive and expects royalties:
>
>> On Thu, 11 Apr 2024 16:06:46 -0400, Chris Ahlstrom wrote:
>>
>>> I would skip such an event. (And generally loud concerts as well.)
>>
>> If it's too loud you're too old.
>
> I studied hearing science (got a Ph.D in it).

When I was doing a little research about 'surround sound' recently, I
was curious how your brain knows sound is coming from directly behind you.

Can you shed some light?

Related: how much sound normally passes through your ear (and I mean
through the skin and cartilage of your ear tissue) from behind? Does
that help you localize the sound?

Farley Flud <ff@linux.rocks> wrote at 19:23 this Thursday (GMT):
> On Thu, 11 Apr 2024 14:40:11 -0000 (UTC), candycanearter07 wrote:
>
>
>>
>> That's why those libraries exist. Most users couldn't write a program to
>> access them.
>>
>
> They don't need to.
>
> To play an OGG file just use ogg123.
>
> For opus audio do:
>
> opusdec file.opus --force-wav - | aplay
>
> Very simple.

Yes, but having one program decide which to use, then play it with a
consistent UI, is convenient.
--
user <candycane> is generated from /dev/urandom