SDXC is shoving exFat down everyones throats. exFat is heavily patent encumbered (yes.. they really did patent the idea if going from fat32 to essentially fat64).
Getting exfat support in kernel will likely be akin to getting patent encumbered codecs is on linux now. A small inconvenience but it won't work out of the box.
Going back to the days where you can't just read anything anyone gives you is a pain in the ass. I blame software patents.
Also I envy your free weapon, where I am at present you couldn't even own an m4 due to the firearms laws. Hell even all semi-autos are banned for civilian use.
yes, Rockloon, Zeroconf networking is in fact a nice thing to have if you want to write applications which discover other apps/devices/services across a LAN without the need for the user to configure anything
Not if the computers on your lan are on multiple subnets.
Take your logic to it's extreme, and you would be saying who needs any application except for a browser?
In modern times I've seen people write emulators in javascript that make quad core machines reel where a native program emulator runs fine on a 486.
Javascript and it's kin have uses, but when all you have is a hammer everything looks like a nail... and some things should really not be written 'for the web'.
This is a perfect example of why having drivers in the mainline kernel tree are a good idea.
If it was it would get automatic updates as the other parts of the kernel are changed. What tends to happen though when there is an open source driver not in kernel, people study the source and within 3-6 months create an in kernel driver that supports it.
So typical worst case is you are stuck using an old kernel version for maybe a year until the new proper drivers are ready for prime time.
Had this happen to me with my eeepc that has an rt2860 chip in it for wifi. At first dependent on their module, it broke, kept old kernel for six months now in kernel driver works a charm.
Really? You're using an analog tuner to receive what?
Actually I'm using it to capture the composite output of various consoles. But you missed the point, this is one example of many I can give.
The fact that you think this way shows that you have no concept of how proper software development works. Its not even unique to software development, standardized interfaces are considered one of the major innovations that brought us to where we are today as far as production is concerned.
Standardised interfaces are a great thing for enabling functionality between discrete projects. Remember that this is the kernels INTERNAL functions we are talking about.. You would essentially be mandating the codebase to freeze.
I think it has been well and truly established that having a release every few years as opposed to consistent incremental improvements is a bad idea. But you are free to argue for this if you wish.
The interface doesn't have to stay the same forever, and indeed can't, but consistency and stability are a good thing, even if you don't understand why.
If you want the same interfaces why not just keep using a single kernel version then? after all any improvements the newer kernels bring are changes which detracts from the codebase staying the same.
And to ignore what every major developer complains about and uses as their reason for not developing for Linux is just utterly ignorant. If you want people to develop for Linux you have to address their reason for not doing it, not sit around and tell them they are wrong.
We can't be blamed for thinking long-term, after all why should we care for binary only drivers when they will eventually be broken anyway (not to mention technically break the gpl anyway). And if they are open source they should be encouraged to go into mainline so they get updated to fit with the rest of the kernel automatically.
Do you think an assembly line would work if every engine, tire, bolt, or whatever had 'improvements to its interface' every day? Oh, today we get new bolts, gotta update the engines... oh, the engines have a change that requires transmission modifications.
Within a single project, when dependent parts communicate to eachother about the changes and improvements, incremental improvements are far better than complete overhalls (do you really want a linux 3.0 that comes in five years time that has problems an order of magnitude worse than vista did? while having a stable abi that whole time just from lack of updates?).
Yes it can come across as nasty to simply ignore those that propose retardedly stupid ideas such as a stable in kernel ABI, but unless you make release cycles longer and suppress technical improvements to single big releases, you can't do it.
And more to the point if you are doing things 'the right way' the lack of a stable ABI does not effect you in the slightest.
The bottom line, IMHO, is this: KDE shouldn't release anything (going back to 4.x) until it has feature-parity with previous versions, and until it is as tested and reliable as possible--in other words, "when it's ready." Anything else merely frustrates users and hurts its reputation--and sometimes risks data loss, as well.
Been using kde 4 since 4.0 and I have never experienced data loss etc, some apps had stability issues circa 4.0 and 4.1, but I'm using it for my primary machine and cannot actually think of the last time I had a segfault.
I know this is a 'works for me' kind of post, however I have installed systems running kde for quite a few people (although none of which with kubuntu) and none have ran into any issues thus far.
KDE 4.x is pure crap and so is gnome. And there is only ONE single reason they are pure crap... they both rely on pulseaudio for sound.
There is absolutely no way to install KDE 4 or Gnome without installing pulseaudio and have your audio to work properly.
This is completely false, I run pulseaudio-free workstations with kde that use jack as the audio backend.
With this out of the way the rest of your post is meaningless.
You do know that the WoW beta included a linux client as well as the windows one yes?
Apparently the official reasons it was dropped for release were 'legal reasons'. Nobody knows if the port is kept up to date, however it is known that one point some of the developers were using the linux build on their own machines.
For starters, unlike windows land, in linux drivers tend to have common things that many drivers need put into modules and re-used. For example the mac80211 stack. In this example all the actual card drivers have to do is basically tell the kernel where the registers are and what they do and bam, working wifi.
Bug fixes in used modules fix bugs in all things that use it. Code re-use to the extreme.
It also helps with portability, can you run your nvidia binary driver on mips? Hell no, could you run neauvou which exposes the hardware through gallium and uses GEM etc.
As long as the drivers need to be rewritten every few months because the kernel was changed (often for no other reason than to break compatibility), linux will have crummy drivers.
Linux by far has the most in-built driver support of any operating system that has ever existed. To call it crappy is a bit of a farce.
All hardware vendors need to do is give a kernel dev specs and a driver which will be indefinitely supported is created. I can still use a tv tuner card from 2001 on my machine now, could you do the same with windows 7?
Having a stable ABI limits improvements to the kernel, and loses a great deal of flexibility and usefulness. So really, screw that. If you 'want' a stable ABI, it is a good sign you are doing it wrong anyway.
but the "traditional" gaming segment is more or less left out.
Depends how you define traditional. I have a wii and xbox 360, and the xbox only ever occasionally sees use as a dvd player, that's it. On the wii however I have about two dozen games or so.
That being said metroid prime 3 by far interested me more than halo 3 which I tend to find a bore, same with most other games of that sort, even gta 4 I find to be a serious let down.
You may call them 'kiddy' games, but really what is so mature about wanting to fake shoot up a neighbourhood? Hell even stuff like mercury meltdown beats that kind of tripe.
The only people I find not liking the wii tend to be the ones who grew up with the xbox and ps2 demanding sex/drugs and violence. Those who are content with puzzles/platforming/uniqueness tend to not mind the wii.
Yes there is lots of shovelware, but there always is for the most popular platform, case in point ps2.
I for one fail to see how the american revolution was really such a change. You rebel against a government and eventually they send people with guns to stop you. Same as the current american government. Can guarantee if you don't pay your taxes and take arms against the US government for it they will not be very amused or forgiving.
Anything above about 70% volume caused a lot of clipping and sounded horrible. No idea why, but even a cheap ad-on card was an improvement.
Go alsamixer -c 0 to see your sound card settings, it will give the volume in db for each channel. Have a look at the master channel and you will notice for most cards it hits 0db at about 74 percent or so. 100% is +12db, anything with a positive value results in nasty clipping. I imagine it is the same situation on windows but a bit harder to tell.
[1] If you're doing effects on the card, it definitely does make a difference. The cheaper on-board cards did everything in 16-bit, so you got audible clipping from the artefacts. The better ones used 24- or 32-bit values for intermediate results.
Even if you are doing actual audio work the only real reason to get a sound card is lower noise levels. In so far as the quality of the samples decent sound servers like jack do all their processing as 32-bit floats.
Main use of this is errors don't become so cumulative. At the end when it is rendered at 16-bit for cd use it will sound better than if you'd used 16-bit for the whole process.
In modern times relying on the sound card for mixing/effects/midi is just stupid, we have quad/oct core machines that have far lower latency doing it in software and more flexibility. We only need the sound card to essentially act as a dac now.
If your domain is CLI server apps, mono tends to work just fine. I am well aware of some of the shortcomings of the GUI libraries of c#. And yes they would make us use c# even if mono did not exist.
Disappointing I was marked troll. If it weren't for mono I would have actually had to use windows at some point in the last ten years. It does have some utility.
So you never use wine ever? what about samba for interacting with windows shares?
It's all for compatibility. When employers force you to use c# and related things it is nice to be able to use linux to develop on and run it. Not all of us get to choose what languages we must work with.
unix you may have a point, but it's market share is being absorbed by linux and has been for over a decade.
Redhat/IBM etc will certainly be around for quite some time to support linux. Redhat has bet the farm on linux and without it they are nothing. Their market cap/share price is rather nice too.
Attachmate sell terminal services like xservers and an ssh server/client... they can only really sell these things because windows lacks them by default.
By encouraging their users to go to linux would that not kill a fair majority of their market just because people can get linux to do that from anywhere?
For one thing She would get a real kick out some human using their limited human intelligence and perspective trying to solve an unsolvable problem -- "prove that something 'outside' yourself exists!
Fan of solopsism (or a derivative) hey? I'll pay that, good luck making any kind of productive thought with that. I mean hey if everything is merely inside yourself are you really that egotistical to create illusions of other minds simply to satiate your own ego?
Hell go and cause armageddon by killing yourself, if you're right and we're all just a part of you we'll all cease to exist with you right?
You are confusing BLIND faith with FAITH.
Faith is _action_ _because_ of beliefs. If you do nothing with your beliefs, it is just that, beliefs.
Look up the definition of faith. I dare you... actually hell I'll post it
"A belief not resting on logical proof or material evidence."
As a Gnostic & mystic
Ah so we have one of those 'I have experienced the wonder of the goddess' types. Very well
As for the rest of your post, I leave you to your delusions, you are entitled to them, the further on peoples errors are in a chain of logic the longer it takes to explain the sources of error and to be frank I cannot be bothered to explain the concepts you are using with incorrect definitions.
Slashdot Mirror
SDXC is shoving exFat down everyones throats. exFat is heavily patent encumbered (yes.. they really did patent the idea if going from fat32 to essentially fat64).
Getting exfat support in kernel will likely be akin to getting patent encumbered codecs is on linux now. A small inconvenience but it won't work out of the box.
Going back to the days where you can't just read anything anyone gives you is a pain in the ass. I blame software patents.
it's a weapon... who cares about looks?
Function over form and all that.
Also I envy your free weapon, where I am at present you couldn't even own an m4 due to the firearms laws. Hell even all semi-autos are banned for civilian use.
You get what you pay for.
yes, Rockloon, Zeroconf networking is in fact a nice thing to have if you want to write applications which discover other apps/devices/services across a LAN without the need for the user to configure anything
Not if the computers on your lan are on multiple subnets.
Interestingly the steyr aug fits all of the design requirements listed on that page (since the 90's the a3 revision comes with picatinny rails)
They have spent so much on this weapon and yet their standard issue rifle is horrible compared to more modern (hell even three decades ago) weapons.
While not a video card, the N64 memory expansion pack doubled the amount of ram in the system.
Take your logic to it's extreme, and you would be saying who needs any application except for a browser?
In modern times I've seen people write emulators in javascript that make quad core machines reel where a native program emulator runs fine on a 486.
Javascript and it's kin have uses, but when all you have is a hammer everything looks like a nail... and some things should really not be written 'for the web'.
All the music I listen to is binary files. How else would I keep them on digital storage?
Ternary?
This is a perfect example of why having drivers in the mainline kernel tree are a good idea.
If it was it would get automatic updates as the other parts of the kernel are changed. What tends to happen though when there is an open source driver not in kernel, people study the source and within 3-6 months create an in kernel driver that supports it.
So typical worst case is you are stuck using an old kernel version for maybe a year until the new proper drivers are ready for prime time.
Had this happen to me with my eeepc that has an rt2860 chip in it for wifi. At first dependent on their module, it broke, kept old kernel for six months now in kernel driver works a charm.
Really? You're using an analog tuner to receive what?
Actually I'm using it to capture the composite output of various consoles. But you missed the point, this is one example of many I can give.
The fact that you think this way shows that you have no concept of how proper software development works. Its not even unique to software development, standardized interfaces are considered one of the major innovations that brought us to where we are today as far as production is concerned.
Standardised interfaces are a great thing for enabling functionality between discrete projects. Remember that this is the kernels INTERNAL functions we are talking about.. You would essentially be mandating the codebase to freeze.
I think it has been well and truly established that having a release every few years as opposed to consistent incremental improvements is a bad idea. But you are free to argue for this if you wish.
The interface doesn't have to stay the same forever, and indeed can't, but consistency and stability are a good thing, even if you don't understand why.
If you want the same interfaces why not just keep using a single kernel version then? after all any improvements the newer kernels bring are changes which detracts from the codebase staying the same.
And to ignore what every major developer complains about and uses as their reason for not developing for Linux is just utterly ignorant. If you want people to develop for Linux you have to address their reason for not doing it, not sit around and tell them they are wrong.
We can't be blamed for thinking long-term, after all why should we care for binary only drivers when they will eventually be broken anyway (not to mention technically break the gpl anyway). And if they are open source they should be encouraged to go into mainline so they get updated to fit with the rest of the kernel automatically.
Do you think an assembly line would work if every engine, tire, bolt, or whatever had 'improvements to its interface' every day? Oh, today we get new bolts, gotta update the engines ... oh, the engines have a change that requires transmission modifications.
Within a single project, when dependent parts communicate to eachother about the changes and improvements, incremental improvements are far better than complete overhalls (do you really want a linux 3.0 that comes in five years time that has problems an order of magnitude worse than vista did? while having a stable abi that whole time just from lack of updates?).
Yes it can come across as nasty to simply ignore those that propose retardedly stupid ideas such as a stable in kernel ABI, but unless you make release cycles longer and suppress technical improvements to single big releases, you can't do it.
And more to the point if you are doing things 'the right way' the lack of a stable ABI does not effect you in the slightest.
highly recommend MPD, there are many interfaces for it I tend to use ncmpcpp but I believe there are some graphical ones and even web ones.
The bottom line, IMHO, is this: KDE shouldn't release anything (going back to 4.x) until it has feature-parity with previous versions, and until it is as tested and reliable as possible--in other words, "when it's ready." Anything else merely frustrates users and hurts its reputation--and sometimes risks data loss, as well.
Been using kde 4 since 4.0 and I have never experienced data loss etc, some apps had stability issues circa 4.0 and 4.1, but I'm using it for my primary machine and cannot actually think of the last time I had a segfault.
I know this is a 'works for me' kind of post, however I have installed systems running kde for quite a few people (although none of which with kubuntu) and none have ran into any issues thus far.
KDE 4.x is pure crap and so is gnome. And there is only ONE single reason they are pure crap... they both rely on pulseaudio for sound. There is absolutely no way to install KDE 4 or Gnome without installing pulseaudio and have your audio to work properly.
This is completely false, I run pulseaudio-free workstations with kde that use jack as the audio backend.
With this out of the way the rest of your post is meaningless.
You do know that the WoW beta included a linux client as well as the windows one yes?
Apparently the official reasons it was dropped for release were 'legal reasons'. Nobody knows if the port is kept up to date, however it is known that one point some of the developers were using the linux build on their own machines.
have you even checked out a modern version of cube2?
It may not be up to par with the latest, but to call it 90's is a bit of a stretch.
Provide a stable binary interface,
This is wrong on so many levels in linux land.
For starters, unlike windows land, in linux drivers tend to have common things that many drivers need put into modules and re-used. For example the mac80211 stack. In this example all the actual card drivers have to do is basically tell the kernel where the registers are and what they do and bam, working wifi.
Bug fixes in used modules fix bugs in all things that use it. Code re-use to the extreme.
It also helps with portability, can you run your nvidia binary driver on mips? Hell no, could you run neauvou which exposes the hardware through gallium and uses GEM etc.
As long as the drivers need to be rewritten every few months because the kernel was changed (often for no other reason than to break compatibility), linux will have crummy drivers.
Linux by far has the most in-built driver support of any operating system that has ever existed. To call it crappy is a bit of a farce.
All hardware vendors need to do is give a kernel dev specs and a driver which will be indefinitely supported is created. I can still use a tv tuner card from 2001 on my machine now, could you do the same with windows 7?
Having a stable ABI limits improvements to the kernel, and loses a great deal of flexibility and usefulness. So really, screw that. If you 'want' a stable ABI, it is a good sign you are doing it wrong anyway.
but the "traditional" gaming segment is more or less left out.
Depends how you define traditional. I have a wii and xbox 360, and the xbox only ever occasionally sees use as a dvd player, that's it. On the wii however I have about two dozen games or so.
That being said metroid prime 3 by far interested me more than halo 3 which I tend to find a bore, same with most other games of that sort, even gta 4 I find to be a serious let down.
You may call them 'kiddy' games, but really what is so mature about wanting to fake shoot up a neighbourhood? Hell even stuff like mercury meltdown beats that kind of tripe.
The only people I find not liking the wii tend to be the ones who grew up with the xbox and ps2 demanding sex/drugs and violence. Those who are content with puzzles/platforming/uniqueness tend to not mind the wii.
Yes there is lots of shovelware, but there always is for the most popular platform, case in point ps2.
I for one fail to see how the american revolution was really such a change. You rebel against a government and eventually they send people with guns to stop you. Same as the current american government. Can guarantee if you don't pay your taxes and take arms against the US government for it they will not be very amused or forgiving.
Anything above about 70% volume caused a lot of clipping and sounded horrible. No idea why, but even a cheap ad-on card was an improvement.
Go alsamixer -c 0 to see your sound card settings, it will give the volume in db for each channel. Have a look at the master channel and you will notice for most cards it hits 0db at about 74 percent or so. 100% is +12db, anything with a positive value results in nasty clipping. I imagine it is the same situation on windows but a bit harder to tell.
[1] If you're doing effects on the card, it definitely does make a difference. The cheaper on-board cards did everything in 16-bit, so you got audible clipping from the artefacts. The better ones used 24- or 32-bit values for intermediate results.
Even if you are doing actual audio work the only real reason to get a sound card is lower noise levels. In so far as the quality of the samples decent sound servers like jack do all their processing as 32-bit floats.
Main use of this is errors don't become so cumulative. At the end when it is rendered at 16-bit for cd use it will sound better than if you'd used 16-bit for the whole process.
In modern times relying on the sound card for mixing/effects/midi is just stupid, we have quad/oct core machines that have far lower latency doing it in software and more flexibility. We only need the sound card to essentially act as a dac now.
If your domain is CLI server apps, mono tends to work just fine. I am well aware of some of the shortcomings of the GUI libraries of c#. And yes they would make us use c# even if mono did not exist.
Disappointing I was marked troll. If it weren't for mono I would have actually had to use windows at some point in the last ten years. It does have some utility.
nobody remotely sane has or would ever use Mono.
So you never use wine ever? what about samba for interacting with windows shares?
It's all for compatibility. When employers force you to use c# and related things it is nice to be able to use linux to develop on and run it. Not all of us get to choose what languages we must work with.
unix you may have a point, but it's market share is being absorbed by linux and has been for over a decade.
Redhat/IBM etc will certainly be around for quite some time to support linux. Redhat has bet the farm on linux and without it they are nothing. Their market cap/share price is rather nice too.
Attachmate sell terminal services like xservers and an ssh server/client... they can only really sell these things because windows lacks them by default.
By encouraging their users to go to linux would that not kill a fair majority of their market just because people can get linux to do that from anywhere?
For one thing She would get a real kick out some human using their limited human intelligence and perspective trying to solve an unsolvable problem -- "prove that something 'outside' yourself exists!
Fan of solopsism (or a derivative) hey? I'll pay that, good luck making any kind of productive thought with that. I mean hey if everything is merely inside yourself are you really that egotistical to create illusions of other minds simply to satiate your own ego?
Hell go and cause armageddon by killing yourself, if you're right and we're all just a part of you we'll all cease to exist with you right?
You are confusing BLIND faith with FAITH.
Faith is _action_ _because_ of beliefs. If you do nothing with your beliefs, it is just that, beliefs.
Look up the definition of faith. I dare you... actually hell I'll post it
"A belief not resting on logical proof or material evidence."
As a Gnostic & mystic
Ah so we have one of those 'I have experienced the wonder of the goddess' types. Very well
As for the rest of your post, I leave you to your delusions, you are entitled to them, the further on peoples errors are in a chain of logic the longer it takes to explain the sources of error and to be frank I cannot be bothered to explain the concepts you are using with incorrect definitions.
Good day sir