Banks and other instutitions have flagrantlyignoredfederal and state laws, and in many cases it appears that they screwed up so badly that no one actually has legal standing to forclose!
Planes HAVE to be inspected and maintained constantly unlike cars where nobody really cares as long as your not a direct and imminent threat to other people on the road.
Depending on where you live your car might require annual inspections for emission testing. Extending this to mandatory steering system inspections isn't that far of a leap.
The simple example is that someone with a lot of money to throw around goes into a poor area and offers to pay individuals for every receipt they bring him proving they voted for Candidate A. People go out, vote for Candidate A, bring the receipt back to prove it, and get paid off. It's not hard at all to imagine something like that happening in a place like Afghanistan. And just because it's hard to imagine in the West, doesn't mean it couldn't happen here too.
What do you mean it couldn't happen here?
The only difference is that the politicians here don't need to collect receipts - they just redraw the district lines.
And they don't use their own money - they use yours.
Personally I will withhold judgement until I know who exactly will be releasing the information. It just might become something that you do want to see.
I wanted to use Linux, but aside from maybe Slack, Arch, and LFS, none of the major distributions are usable without giving me endless problems. It's either package management, or hardware drivers, or the DE is fused with everything else and can't be removed, etc...it's hell.
Init/Upstart both need to be scrapped, and replaced with FreeBSD's init system. It is simple, clear, sane, and WORKS.
I solved most of the problems you mention by switching to Gentoo (from LFS) and by compiling the kernel myself using the sources direct from kernel.org
Desktop environments need to ensure they integrate nicely with PulseAudio. GNOME is obviously doing this, but KDE is lagging behind. I do hope to rectify the latter situation personally, and have a pretty clear roadmap to making this happen – it’s just a matter of finding the time to do it!
Do you publish patches or a git tree so that interested users can try out your changes?
Blocking all radio signals is a problem because passengers will still want to use their phones and laptops even if the driver is not.
Stating that someone else will always be available to dial 911 is false because sometimes people get into accidents where there are no passengers or witnesses.
If they're critically injured, they can't use a cell phone and there will be plenty of folks around them to call for emergency services. And most likely, they're in that situation for having been using a cell phone in the first place. Therefore, if they can't use a cell phone, they won't get into an accident and then they won't be critically injured. Problem solved.
Have you ever noticed all that extra space beside and behind you when you are driving? Believe it or not, other people can ride in the car too! Some of these people (let's call them "passengers") might want to use their cell phones during the trip.
Not all car accidents happens when the driver is talking on the phone nor do they all involve more than one car. Sometimes a person hits a deer, or skids on ice and ends up in a ditch without any witnesses at all. Too bad if they can't get a 911 call to go through.
I have 2 personally, but I do not know anyone else who does. So I think it is fairly important point for many people. I might be wrong, of course.
I'm going to come out and say that having a webcam is mainstream, since my grandmother has one (she's not on Linux).
One of those and/or some type of USB or Bluetooth headset for VOIP and you now need some method to connect applications to the correct inputs and outputs.
I'd like to understand the whole situation better, and see what Pulse can do for me.
I installed PulseAudio for the first time this weekend to answer that very question.
My main desktop is used by my wife and I for regular internet browsing/email as well as webcam chats with inlaws and running Rosetta Stone under Wine.
PulseAudio lets me route the webcam microphone to the IM programs and the USB headset microphone to Rosetta Stone*. If one of us is listening to music or watching a movie on the speakers and the other one gets a phone call we can easily route the sound to the headset without needing to stop playback.
It's not exactly groundbreaking but it does make life easier.
*Wine support for PulseAudio is somewhat problematic, but solutions exist.
If you try to force them into doing it in a "properly organized" way, to save yourself a little bit of effort,
The exact magnitude of that "little bit" is the key. I'm not a developer but I can see that if the number of users numbers in the thousands (millions) and the number of developers numbers in the dozens that a large bottleneck exists. For a scaling perspective it makes sense for as much of the task that can be distributed and parallized (assiging a bug report to the correct component) to be done by the users.
Personally when I ask for free support I try to be as little of a burden on the developer as possible. Of course if I am paying for a certain level of support then a different set of expectations apply.
Then why are so many people having so many problems with getting the most basic of these (the sound card itself) to work?
I've only been using it since yesterday and I can only speak for myself but I don't have any major problems. On the other hand I use Gentoo so my threshold between "minor annoyance" and "major problem" might be skewed a little bit. One minor annoyance I've run into is that in order to make Wine play nicely with PulseAudio on a 64 bit system I need to build a 32 bit PulseAudio libraries in a chroot so that the third-party winepulse patch will compile.
PulseAudio isn't written for the hardware of 10 years ago. It is written for 2009 where a typical user has multiple independent pieces of hardware each capable of sound input and/or output that may or may not be present all the time (webcams, headsets, bluetooth, etc.)
who gives a flying F about the red tape, if a developer wont see an actual problem and fix it, hes too stupid.
See a problem? then fix it, regardless of a bug list, report # id.
The other side of that argument is that bug reporters outnumber developers. Not to mention the developers are frequently not getting paid by the bug reporters.
Developers should spend as much of their time as possible fixing bugs and adding features, not fixing poorly written bug reports. If the users want their bugs fixed they should either pay someone to fix them or help out the developers by writing good bug reports.
Besides your regular set of speakers you also have a webcam with a microphone and a USB or Bluetooth headset and you want the inputs and outputs to get routed to the correct applications.
Slashdot Mirror
Thanks.
Banks and other instutitions have flagrantly ignoredfederal and state laws, and in many cases it appears that they screwed up so badly that no one actually has legal standing to forclose!
I think The Pirate Bay operates in a different legal jurisdiction...
Depending on where you live your car might require annual inspections for emission testing. Extending this to mandatory steering system inspections isn't that far of a leap.
What do you mean it couldn't happen here?
The only difference is that the politicians here don't need to collect receipts - they just redraw the district lines.
And they don't use their own money - they use yours.
What I found more notable than the 0.5% number was the amount of new features that will not be appearing within the next twelve months.
Personally I will withhold judgement until I know who exactly will be releasing the information. It just might become something that you do want to see.
He admits that in the article.
Are you suggesting that people read the articles? You must be new here.
I solved most of the problems you mention by switching to Gentoo (from LFS) and by compiling the kernel myself using the sources direct from kernel.org
The logic is that this is a dumb law that inconveniences millions of people at great expense for a dubious benefit and causes some potential harm.
Do you publish patches or a git tree so that interested users can try out your changes?
You're just being deliberately obtuse.
Blocking all radio signals is a problem because passengers will still want to use their phones and laptops even if the driver is not.
Stating that someone else will always be available to dial 911 is false because sometimes people get into accidents where there are no passengers or witnesses.
Not exactly true. The temperature difference between the passanger cabin and the evaporaror will affect the load on the compressor.
Yep. Facebook too...
I'm going to come out and say that having a webcam is mainstream, since my grandmother has one (she's not on Linux).
One of those and/or some type of USB or Bluetooth headset for VOIP and you now need some method to connect applications to the correct inputs and outputs.
I installed PulseAudio for the first time this weekend to answer that very question.
My main desktop is used by my wife and I for regular internet browsing/email as well as webcam chats with inlaws and running Rosetta Stone under Wine.
PulseAudio lets me route the webcam microphone to the IM programs and the USB headset microphone to Rosetta Stone*. If one of us is listening to music or watching a movie on the speakers and the other one gets a phone call we can easily route the sound to the headset without needing to stop playback.
It's not exactly groundbreaking but it does make life easier.
*Wine support for PulseAudio is somewhat problematic, but solutions exist.
True
The exact magnitude of that "little bit" is the key. I'm not a developer but I can see that if the number of users numbers in the thousands (millions) and the number of developers numbers in the dozens that a large bottleneck exists. For a scaling perspective it makes sense for as much of the task that can be distributed and parallized (assiging a bug report to the correct component) to be done by the users.
Personally when I ask for free support I try to be as little of a burden on the developer as possible. Of course if I am paying for a certain level of support then a different set of expectations apply.
This is a shrinking use case. Plenty of people already have hardware devices (besides sound cards) that handle audio data.
I've only been using it since yesterday and I can only speak for myself but I don't have any major problems. On the other hand I use Gentoo so my threshold between "minor annoyance" and "major problem" might be skewed a little bit. One minor annoyance I've run into is that in order to make Wine play nicely with PulseAudio on a 64 bit system I need to build a 32 bit PulseAudio libraries in a chroot so that the third-party winepulse patch will compile.
But other than that everything's good...
PulseAudio isn't written for the hardware of 10 years ago. It is written for 2009 where a typical user has multiple independent pieces of hardware each capable of sound input and/or output that may or may not be present all the time (webcams, headsets, bluetooth, etc.)
The other side of that argument is that bug reporters outnumber developers. Not to mention the developers are frequently not getting paid by the bug reporters.
Developers should spend as much of their time as possible fixing bugs and adding features, not fixing poorly written bug reports. If the users want their bugs fixed they should either pay someone to fix them or help out the developers by writing good bug reports.
Besides your regular set of speakers you also have a webcam with a microphone and a USB or Bluetooth headset and you want the inputs and outputs to get routed to the correct applications.
Fortunately half the population is already naturally equipped with this interface.