So you equate your rather limited usecase and expectations with everyone elses needs, call them whiners, and then top it off with a nice appeal to antiquity fallacy.
Are you talking about an alsalib wrapper that acts as a pulse client? It's not honest to compare that to the real deal. If this is the case then your problem is still pulse, not alsa itself. Remove pulse from your system and link mpg123 against the real alsa-lib and your problems should go away.
If alsa was truly having a problem on your system then pulse wrapped applications would still have issues too.
alsa-lib is userland and abstracts device differences, though I believe it is possible to write directly to/dev/snd/pcm* if you wanted. I believe any application supporting alsa directly calls this library.
The primary visible feature to most users is per-application volume control.. Essentially, pulse is a userland mixer. It supports effects plugins, multiplexing, network IO, etc. It also adds noticeable latency and has bugs of its own. Alsa also has a software mixer, dmix, but IIRC it was not enabled by default at the time pulse was first released. Without dmix, only one application could open the sound device at a time (unless the device had hardware mixing eg:sblive/audigy). This issue helped drive adoption of pulse. These days, 99% of sound devices are little more than simple DACs so dmix is enabled by default eliminating the need for pulse in typical desktop configurations.
Firefox users who are already using pulse won't notice anything. Those of us who like low latency response and problem free sound from their pulse-free systems (and who don't care about per app volume controls) will miss the direct alsa support.
'not useful' by whom? Allowing authority to dictate arbitrary limits on expression is far riskier to free society than some one/group taking offense. Frankly, if your leaders are willing to cause some calamity because they were called names, then they lack the discipline required for leadership and don't deserve to hold office.
No thanks. That would just make would-be programmers stay away, and the rest of the industry so risk-adverse that it would create a market for DE-automating business.
I never said it wasn't moderated. Usenet and the other early systems were only 'cesspools' to thin skinned idiots with bad arguments.
I don't see that as a problem.
I bet you would if the banned topics included your viewpoints. Therein lies the hypocrisy of modern social justice. You would not be defending that advertiser excuse either. You'd attack it as evidence of 'systemic bigotry.'
The people upset about this generally just want to bypass the obscurity phase and broadcast their messages to a wide audience that doesn't want to listen.
Like MLK? The suffragettes? Had they existed during the internet era, should they have been censored for speaking their minds to that 'wide audience that doesn't want to listen'? Should they have been sued or jailed? I think you need to reevaluate your politics.
You mean the one where discriminators like race, sex, country, etc didn't matter? Where free speech reigned and all that mattered was the argument made? The one that routed around censorious assholes and their insecurities?
Gawker? Nick Denton? Oh. So not 'that' internet after all.
Web Assembly doesn't introduce that problem, it is already there for decades.
No, but it does attempt to remove some of the performance barriers that cause people to continue writing local applications, encouraging more development of less-secure-by-design browser 'apps' to replace them.
What's better: using a JavaScript or WebAssembly app in a web browser and having it fuck up your workflow when it magically changes/disappears one day, or having to run a specific OS to run a native, local application that's there forever until you choose to abandon it?
1. disable with physical switch on side of machine if possible. 2. disable in bios if possible 3. go to device manager and remove the device. remove driver from driver store. go to \windows\system32\drivers and delete any remaining relevant.sys files. 4. go to device manager/network manager. Right click wireless adapter, hit disable. 5. remove all entries in windows firewall, set it to block in/out by default, and whitelist required applications. This is the least secure but most convenient of the options besides default.
If your client's truly that paranoid (justifiably or not), just operate on the data from a hardwired/airgapped machine and charge him for the inconvenience.
Slashdot Mirror
So you equate your rather limited usecase and expectations with everyone elses needs, call them whiners, and then top it off with a nice appeal to antiquity fallacy.
Great.
Yeah because switching from c++ to some hipster interpreted/bytecode garbage is going to fix everything.
Your time estimate ignores the redevelopment of the workflow he created around firefox over the years..
Are you talking about an alsalib wrapper that acts as a pulse client? It's not honest to compare that to the real deal. If this is the case then your problem is still pulse, not alsa itself. Remove pulse from your system and link mpg123 against the real alsa-lib and your problems should go away.
If alsa was truly having a problem on your system then pulse wrapped applications would still have issues too.
It wasn't before... Now it is. For a tiny bit of code that takes 0 effort to keep. It's not like alsa-lib has changed much in years.
What bugs were those? In the years I've used firefox with pulse-free systems, I've never encountered any issues.
Endless abstraction has its own costs too.
For now.. Supposedly, this is to be removed in the future.
alsa-lib is userland and abstracts device differences, though I believe it is possible to write directly to /dev/snd/pcm* if you wanted. I believe any application supporting alsa directly calls this library.
The primary visible feature to most users is per-application volume control.. Essentially, pulse is a userland mixer. It supports effects plugins, multiplexing, network IO, etc. It also adds noticeable latency and has bugs of its own. Alsa also has a software mixer, dmix, but IIRC it was not enabled by default at the time pulse was first released. Without dmix, only one application could open the sound device at a time (unless the device had hardware mixing eg:sblive/audigy). This issue helped drive adoption of pulse. These days, 99% of sound devices are little more than simple DACs so dmix is enabled by default eliminating the need for pulse in typical desktop configurations.
Firefox users who are already using pulse won't notice anything. Those of us who like low latency response and problem free sound from their pulse-free systems (and who don't care about per app volume controls) will miss the direct alsa support.
Pulse is just an alsa client. Alsa isn't unmaintained. It is the defacto sound system for linux.
Individual choice derived from conscious, unconscious, and environmental factors? Are you kidding? That's fascism!
'not useful' by whom? Allowing authority to dictate arbitrary limits on expression is far riskier to free society than some one/group taking offense. Frankly, if your leaders are willing to cause some calamity because they were called names, then they lack the discipline required for leadership and don't deserve to hold office.
Unless you lived in a major city, reception was spotty at best.. cable provided a far more reliable experience.
This 'ban' will not stand up to an NSL..
No thanks. That would just make would-be programmers stay away, and the rest of the industry so risk-adverse that it would create a market for DE-automating business.
I never said it wasn't moderated. Usenet and the other early systems were only 'cesspools' to thin skinned idiots with bad arguments.
I don't see that as a problem.
I bet you would if the banned topics included your viewpoints. Therein lies the hypocrisy of modern social justice. You would not be defending that advertiser excuse either. You'd attack it as evidence of 'systemic bigotry.'
The people upset about this generally just want to bypass the obscurity phase and broadcast their messages to a wide audience that doesn't want to listen.
Like MLK? The suffragettes? Had they existed during the internet era, should they have been censored for speaking their minds to that 'wide audience that doesn't want to listen'? Should they have been sued or jailed? I think you need to reevaluate your politics.
You mean the one where discriminators like race, sex, country, etc didn't matter? Where free speech reigned and all that mattered was the argument made? The one that routed around censorious assholes and their insecurities?
Gawker? Nick Denton? Oh. So not 'that' internet after all.
No. They're constantly changing, spying, cpu hogging, oversized, clunky, bloated, unnavigable abominations meant for fisherpriced mobile junk.
Web Assembly doesn't introduce that problem, it is already there for decades.
No, but it does attempt to remove some of the performance barriers that cause people to continue writing local applications, encouraging more development of less-secure-by-design browser 'apps' to replace them.
What's better: using a JavaScript or WebAssembly app in a web browser and having it fuck up your workflow when it magically changes/disappears one day, or having to run a specific OS to run a native, local application that's there forever until you choose to abandon it?
vista supports dx11.
1. disable with physical switch on side of machine if possible. .sys files.
2. disable in bios if possible
3. go to device manager and remove the device. remove driver from driver store. go to \windows\system32\drivers and delete any remaining relevant
4. go to device manager/network manager. Right click wireless adapter, hit disable.
5. remove all entries in windows firewall, set it to block in/out by default, and whitelist required applications. This is the least secure but most convenient of the options besides default.
If your client's truly that paranoid (justifiably or not), just operate on the data from a hardwired/airgapped machine and charge him for the inconvenience.
This is a technology site, not buzzfeed. The summary should be mostly change logs.
define 'polite society'